Unable to push client on SMS 2003 after upgrade. 1

[dgillings]

I am having an issue with our site. I have upgraded to SMS 2003 from SMS 2.0 with SP5. The upgrade ran flawlessly, and I extended the site into the AD schema. This was all done 4 days ago. I left the server to run, untouched, over the weekend in the hope that the system would work itself out, but alas no.
I have set the site up to use advanced clients as it's default but all clients are still running the legacy. I've also tried to manually push the clients out to all systems, this returned no positive results. Do any of you out there have any idea what could be causing this issue - it's starting to drive me crazy!

Any help or pointers would be appreciated, I'll try just about anything now.

Many thanks in advance for any assistance anyone can provide.

Daniel Gillings
Tech Leader IT Infrastructure

 

[mnt25]

Hey There,
A few things to check:

- Have you set the network access account (for software distribution of the client)
- Have you set the Client Push Installation Account (administrator rights on the machine) has been specified.
- Has the Management Point been specified and created with IIS BITS enabled running 2000 SP3 before pushing the advanced client
- Ensure SITE BOUNARIES have been properly set.
- Make sure machines that you want to push client to have been discovered
- server service is running on designated machines
- file sharing enabled and access to the admin share enabled on designated machines


Lastly, one you probably may already know, but
Do NOT Enable “client push installation to assigned resources”unless you want all discovered resources to get the client installed. when you upgrade from 2.0 client it should uninstall and then reinstall the advanced client.

Let me know if this helps!
-Matt

 

[dgillings]

Thanks for the assistance. After a few hours of looking through the documentation provided, and using your check list I managed to make some progress..

- Have you set the Network Access (for software distribution) - Yes, domain admin account
- Have you set the Client Push Account - Yes, domain admin account
- Has the management point been specified and created with IIS BITS enabled - yes, management point is the SMS server (BITS automatically enabled if you select for it to be used within site settings, am I correct?)
-Ensure Site Boundaries have been properly set - This was the one that took a while, I have now set the site up to use AD Boundaries, and got instant results with the SMS Admin console reporting objects assigned to sites.
- Make sure machines have been discovered - The machines are discovered, otherwise I wouldn't have the option to push the client to them, correct?
-File sharing enabled and access to the admin share enabled on designated machines - I have not changed any settings on this one. The accounts that I am using are all Domain Access, and in such (in our structure) should have access to all the shares.



So, to recap, I have made progress using the checklist you provided. BUT, I still am unable to push out an advanced client to any objects. I tried to push a client to MY PC, so I could check everything up. If you monitor the Event Viewer you can see a successful logon/logoff audit in the security events, allowing the client push account access, then nothing further happens... Any ideas why this could be? This is the only thing holding me up from using this as a tool...

Thanks for your great assistance so far!

Daniel Gillings

 

[dgillings]

A few more points, for information.

"The SMS_CLIENT_CONFIG_MANAGER component's status reports the following two messages on most clients (I think resulting in the issue I have of not being able to push out clients). Does anyone know how to clear these?

SMS Client Configuration Manager cannot connect to the machine "RDHR007". The operating system reported error 5: Access is denied.

Possible cause: The client is not accessible.
Solution: Verify that the client is connected to the network and that the SMS Service account or (if specified) the SMS Client Remote Installation account have the required privileges, as specified in the SMS documentation."


AND

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

Possible cause: The client is offline.
Solution: Verify that the client is connected to the network."

So error messages of "error 5" and "error 53"

Thanks

Daniel Gillings

 

[dgillings]

OK more information. I have been sifting through the log files and I have discovered this in the CCM.LOG:

======>Begin Processing request: "KMWXOJQU", machine name: "RDGSL022" SMS_CLIENT_CONFIG_MANAGER 11/12/2003 17:03:50 1928 (0x0788)
Waiting for change in directory "D:\SMS\inboxes\ccr.box" for queue "Incoming", (30 minute backup timeout). SMS_CLIENT_CONFIG_MANAGER 11/12/2003 17:03:50 2112 (0x0840)
---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0) SMS_CLIENT_CONFIG_MANAGER 11/12/2003 17:03:50 1928 (0x0788)
---> Attempting to connect to administrative share '\\RDGSL022\admin$' using account 'INGUKRDG\SMSServer_ING' SMS_CLIENT_CONFIG_MANAGER 11/12/2003 17:03:50 1928 (0x0788)
---> The 'best-shot' account has now succeeded 1 times and failed 0 times. SMS_CLIENT_CONFIG_MANAGER 11/12/2003 17:03:50 1928 (0x0788)
---> Connected to administrative share on machine RDGSL022 using account 'INGUKRDG\SMSServer_ING' SMS_CLIENT_CONFIG_MANAGER 11/12/2003 17:03:50 1928 (0x0788)
---> Attempting to make IPC connection to share <\\RDGSL022\IPC$> SMS_CLIENT_CONFIG_MANAGER 11/12/2003 17:03:50 1928 (0x0788)
---> Unable to obtain Access Token for machine name &quot;RDGSL022&quot;, error 5. SMS_CLIENT_CONFIG_MANAGER 11/12/2003 17:03:50 1928 (0x0788)
---> ERROR: Unable to access target machine for request: &quot;KMWXOJQU&quot;, machine name: &quot;RDGSL022&quot;, error code: 5 SMS_CLIENT_CONFIG_MANAGER 11/12/2003 17:03:50 1928 (0x0788)
STATMSG: ID=3014 SEV=W LEV=M SOURCE=&quot;SMS Server&quot; COMP=&quot;SMS_CLIENT_CONFIG_MANAGER&quot; SYS=RDGSSMS SITE=ING PID=1724 TID=1928 GMTDATE=Thu Dec 11 17:03:50.328 2003 ISTR0=&quot;RDGSL022&quot; ISTR1=&quot;&quot; ISTR2=&quot;&quot; ISTR3=&quot;&quot; ISTR4=&quot;&quot; ISTR5=&quot;&quot; ISTR6=&quot;&quot; ISTR7=&quot;&quot; ISTR8=&quot;&quot; ISTR9=&quot;&quot; NUMATTRS=0 SMS_CLIENT_CONFIG_MANAGER 11/12/2003 17:03:50 1928 (0x0788)
Retry request id for &quot;KMWXOJQU&quot; set to &quot;RDGSL022&quot; SMS_CLIENT_CONFIG_MANAGER 11/12/2003 17:03:50 1928 (0x0788)
Stored request &quot;RDGSL022&quot;, machine name &quot;RDGSL022&quot;, in queue &quot;Retry&quot;. SMS_CLIENT_CONFIG_MANAGER 11/12/2003 17:03:50 1928 (0x0788)
<======End request: &quot;RDGSL022&quot;, machine name: &quot;RDGSL022&quot;. SMS_CLIENT_CONFIG_MANAGER 11/12/2003 17:03:50 1928 (0x0788)


Anyone have any idea why I have this message:

ERROR: Unable to access target machine for request: &quot;KMWXOJQU&quot;, machine name: &quot;RDGSL022&quot;, error code: 5

I have checked all permissions, and as far as I can see there is no issue with either the account accessing the computer, or the computer itself...?

IF only I could push advanced clients..

Another issue I have discovered - which may help someone brainy out there to help me - is that even if I go through a manual install of an advanced client on a system, and it succeeds, then I do a discover - once again success, it doesn't report in the SMS console as an object with a client at all?

Starting to lose my hair

 

[leajunsw]

Have you resolved this matter yet. I am having the same problem I was just wondering if you had a fix.

Jeff

 

[FreakinBS]

Dito on leajunsw. I am having the same issue.

 

[dgillings]

No I still haven't resolved this issue. I can now push to all systems in my company, but still not to most Windows XP machines, which give the &quot;Unable to obtain access token for machine name 'blah'&quot; etc....

I have tried everything. I thought that it may be an issue with some Windows XP service pack 2 beta security patches (mouthful) so I removed all the security updates - NOTHING.

I'd be happier if this push process wouldn't work on any XP workstations, but it does work on some. And the problem with that is this. ALL our XP workstations are built from the same sysprepped ghost image, and are the same hardware, and are on the same Vlan.... WHY!!!!?? It makes no logical sense.

I'll start thinking illogically and let you know what I come up with!

Daniel Gillings

 

[FreakinBS]

I had to call MS Support to resolve my issues. #1 make sure the Schema was extended properly. You can check the ExtADSch.log on the System drive of the Domain controller where the Schema was extended. Also, and this will sound weird but you must remove the URL Scan ISAPI filter from IIS on your site server. It will conflict with SMS and you will never be able to deploy the Advanced client completely.

 

[Hankejp]

Where do I find that filter to remove it or see if its removed?

URL Scan ISAPI filter from IIS on your site server