Re: Advanced Client install nightmare

Hi All,

Manyh thanks for all the help.

I can successfully install manually using the SMS account.

I have reset the password on this account again, deleted it from SMS and re
configured it, restarted SMS and i have now had some success with client
installs!

The only problem is,i am now seeing a different error with message ID 3019 :

MS Client Configuration Manager cannot install the Advanced Client to
machine "SCAT-001269". This platform is not supported by the Advanced Client.
The Advanced Client requires Windows 2000 or newer Operating System.

This is happening on a number of clients, all of which have Windows XP SP1
installed!

Getting there slowly....


--
IT Engineer



"Anthony Puca - MVP" wrote:

Can you install client manually successfully? If so, I would look at network
devices that are filtering packets between server and client. I have a
client who has a Packet Filter that handles traffic going in/out of Frame
Relay and it was stopping client push install because it matched traffic
pattern of "Zombie" attack. Appliance saw traffic as outbound from MAC x and
then client initiated communication on several different ports to different
devices, DC, SMS server ,etc...

If you can not install manually and get it to discover site and assign
itself, start looking at your desktop build.

--
Anthony Puca - MVP Management Infrastructure
EMC Sr. Solution Architect
Puca_Anthony@xxxxxxx



"Jonathan" <Jonathan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:577580B9-7F21-4C1C-8B24-7902AF05158B@xxxxxxxxxxxxxxxx
Hi,

Yes definately, there is nothing in the Policies that would prevent the
client being installed. We have no machine level policies configured
except
to disable the messenger service and there is no other policies that would
prevent installation.
I have previously successfully installed a client over the network, it has
just stopped working!

I have made no other changes to the AD etc. to cause this as far as i
know.
The only things i have done is to give the accounts full control over the
right OUs.
--
IT Engineer



"Santos Martinez" wrote:

how about your AD Policies, everything is good in that part too.


--
Santos Martinez,MCSE, MCDBA, MCTS
IT Community Staff of Puerto Rico
http://www.itcspr.org



"Jonathan" wrote:

Hi,

The user and computer account both have full control permissions over
both
System and Systems management. (I did this when installing)
In the Systems management OU i have :

SMS-MP-001-SCAT-SMS
SMS-SLP-001-SCAT-SMS
SMS-SITE-001

Inside the SMS-MP and SMS-SLP folders there is nothing. Should there be
some
data in here?

Cheers
--
IT Engineer



"Santos Martinez" wrote:

Can you verify your AD, for System and System Managment OU, if the
Machine$
and the SMS2003 have permissiones to it and if the MP was created
under the
OU of System Management, if not give permissions to this two accounts
on the
System or System Management OU since System Management Inherits from
the
system OU and then, verify is some erros comes to the Site Setting,
also how
your AD policy are you restricting remote registry installations or
something
like it.

regards,

--
Santos Martinez,MCSE, MCDBA, MCTS
IT Community Staff of Puerto Rico
http://www.itcspr.org



"Jonathan" wrote:

Hello again!

I can succesfully connect to the remote registry using the account.
I have
created an account called SMS2003 for this purpose and added it to
boht
Domain Admins and now Enterprise Admins. Domain Admins are also
local admins
on all of our machines so this should be ok.

When logged on as SMS2003 i can connect to everything without a
problem. Is
there anything else that could possibly be causing this? It is a
really
annoying problem! Is there any other log files i should be looking
in for
causes?

Thanks for all your help guys, really appreciated!
--
IT Engineer



"Kim Oppalfens <MVP>" wrote:

Try remotely connecting to the registry of one of these machines
using the
sms2003 account.

Trust me it is not.
The below error occurs if your computers are only member of a
single group,
usually domain computers.


--
Kim Oppalfens
Telindus Belgium
MVP Windows Server System - SMS
"Jonathan" <Jonathan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E36AD158-D8D7-40E9-9BBE-8B64B22BECFB@xxxxxxxxxxxxxxxx
Hi,

I can successfully connect to the Admin$ share of every machine
using the
account specified in the Client push installation properties.

I am also getting the following errors now, in the
SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT log, : (Message ID 5503)


MS Active Directory System Group Discovery Agent reported
errors for 603
objects. DDR's were generated for 603 objects that had errors
while
reading
non-critical properties. DDR's were not generated for 0 objects
that had
errors while reading critical properties.

Possible cause: The SMS Service might not have access to some
properties
of
this object. The container specified might not have the
properties
available.
Solution: Please verify the Active Directory schema for
properties that
are
not replicated or locked. Refer to the discovery logs for more
information.

It looks like it is relateed to me!



--
IT Engineer



"Kim Oppalfens <MVP>" wrote:

try manually connecting to the admin$ share using the sms2003
account
from
your sms server.

--
Kim Oppalfens
Telindus Belgium
MVP Windows Server System - SMS
"Jonathan" <Jonathan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:2D32F33C-8CD7-4017-A821-B670E45F53C8@xxxxxxxxxxxxxxxx
Hi again,

I have deleted and re-created the client install account and
the client
connection account but am still seeing the same errors!

I have reset the counters for the CLIENT_CONFIG_MANAGER log,
is this
the
same as clearing the status messages? Or is there a
different way.

I am still getting the same errors in the CCM.log


--
IT Engineer



"Diwan" wrote:

Hi

First of all clear your status messages from SMS server as
Santos
told.

other thing look bad is.
look like you have missed the remote client installtion
account.
recreate it and double check, it happens.

Warning: no remote client installation or SMS service
account found
$$<SMS_CLIENT_CONFIG_MANAGER><Fri Aug 11 07:49:52.895 2006
GMT
Daylight

Time><thread=3768 (0xEB8)>


thanks,

Diwan

Jonathan wrote:
Hi,

there are lots of errors in the site status under
SMS_CLIENT_CONFIG_MANAGER
stating that SMS either cannot find the clients

SMS Client Configuration Manager cannot find machine
"SCAT-000956"
on
the
network. The operating system reported error 53: The
network path
was
not
found.

Or a similar error which states that access is denied.

Here is more info from the ccm log :

Received request: "SCAT-003321.SCAT" for machine name:
"SCAT-003321"
on
queue: "Retry". $$<SMS_CLIENT_CONFIG_MANAGER><Fri Aug 11
07:49:43.176
2006
GMT Daylight Time><thread=2992 (0xBB0)>
Error event time has expired for Request
"SCAT-003321.SCAT" for
machine
"SCAT-003321". $$<SMS_CLIENT_CONFIG_MANAGER><Fri Aug 11
07:49:43.176
2006
GMT Daylight Time><thread=2992 (0xBB0)>
Stored request "SCAT-003321.SCAT", machine name
"SCAT-003321", in
queue
"Processing". $$<SMS_CLIENT_CONFIG_MANAGER><Fri Aug 11
07:49:43.176
2006 GMT
Daylight Time><thread=2992 (0xBB0)>
WARNING: High volume of CCRs. Slowing down the queue
processing
thread~
$$<SMS_CLIENT_CONFIG_MANAGER><Fri Aug 11 07:49:43.176
2006 GMT
Daylight
Time><thread=2992 (0xBB0)>
Received request: "ZBUFWQR1" for machine name:
"SCAT-002291" on
queue:
"Incoming". $$<SMS_CLIENT_CONFIG_MANAGER><Fri Aug 11
07:49:43.208
2006
GMT
Daylight Time><thread=2988 (0xBAC)>
.

Relevant Pages

  • Re: Client Push keeps failing
    ... verified all of the permissions seem correct. ... No network access account provided. ... I thought that at first too and yet the SMS console still shows this ... I am trying to get the client push to work and it keeps failing. ...
    (microsoft.public.sms.admin)
  • Re: SMS SP3 client problems
    ... I'm using a domain account that has access to just about everything on the ... While the clinet does now install on the ... client machine it never shows up in the SMS admin console as being installed. ...
    (microsoft.public.sms.admin)
  • Re: Advanced Client install nightmare
    ... I can succesfully connect to the remote registry using the account. ... MVP Windows Server System - SMS ... I have deleted and re-created the client install account and the client ... Slowing down the queue processing ...
    (microsoft.public.sms.admin)
  • Error Advanced Client setup
    ... I'm having a problem installing the SMS advanced client on certain servers. ... Action start 16:07:53: INSTALL. ...
    (microsoft.public.sms.setup)
  • Re: Client Push keeps failing
    ... I thought that at first too and yet the SMS console still shows this ... Above messages showed that the ccmsetup ran on the client machine ... I have already setup a "SMSPUSH" user account and it is added to the ... I am able to login to the SMS server using the SMSPUSH user account ...
    (microsoft.public.sms.admin)