SMS2K3 - Client pushes to Win2K systems but not to XP w/SP2 2

[trock1004]

Hi. I am a total newbie to SMS and so-far I've been able to accomplish alot but I'm having some difficulties that I hope someone can help with.

Here's the breakdown of what I have:

1. My primary site (site code 001) is located on our SQL 2000 server (Server 2000) and is running the following roles: Client Access Point, Component Server, Management Point, Reporting Point, Server Locator Point, Site Server and SQL Server.

2. My secondary site (site code 002) is located on a server (Windows 2000) housing a drive cage array and is running the following roles: Client Access Point, Component Server, Distribution Server, Management Point and Site Server.

3. IIS5 and BITS on both servers.

4. Discovery has worked for the Primary and the collections show all of my workstations (5 Win2K w/SP4 and Rollup 1, and 57 WinXP Pro w/SP2) and servers (3 Win2K3 and 5 Win2K).

5. All servers and all Win2K systems have had the client pushed to them and show up as Client: Yes, Assigned: Yes, Site Code: 001 (Primary).

6. All XP systems show up as Client: No, Assigned: Yes, Site Code: {blank}

7. All workstations are running WMI

8. Anything that requires the use of account credentials has been setup to use a specific domain admin account with full abilities.

9. There are no warnings or errors in site status.

10. Both site boundaries are setup with our IP Subnet and Active Directory site for our domain.

If I left anything out that you would need to know to help, please advise and I'll respond with that info.

So why can't I get the client to push out to my XP systems?

Does the above scenario make sense? 002 is specifically intended for use as a distribution point. Should I have set this all up a different way?

Thanks!!

Tony

 

[tbrennans]

enable File and Print Sharing in the Windows Firewall configuration on the Windows XP client.

 

[trock1004]

Thanks for the reply. None of our XP clients have the firewall turned on.

Tony

 

[trock1004]

From the ccm.log, the following is pertaining to one of my XP systems:

Getting a new request from queue "Incoming" after 100 millisecond delay. $$<SMS_CLIENT_CONFIG_MANAGER><Thu Oct 06 00:02:44.981 2005 Pacific Daylight Time><thread=2116 (0x844)>
Found CCR "soa1ntxb.CCR" in queue "Incoming". $$<SMS_CLIENT_CONFIG_MANAGER><Thu Oct 06 00:02:44.981 2005 Pacific Daylight Time><thread=2116 (0x844)>
Received request: "SOA1NTXB" for machine name: "AHPDX0167" on queue: "Incoming". $$<SMS_CLIENT_CONFIG_MANAGER><Thu Oct 06 00:02:45.106 2005 Pacific Daylight Time><thread=2116 (0x844)>
Stored request "SOA1NTXB", machine name "AHPDX0167", in queue "Processing". $$<SMS_CLIENT_CONFIG_MANAGER><Thu Oct 06 00:02:45.153 2005 Pacific Daylight Time><thread=2116 (0x844)>
----- Started a new CCR processing thread. Thread ID is 0x778. There are now 4 processing threads $$<SMS_CLIENT_CONFIG_MANAGER><Thu Oct 06 00:02:47.153 2005 Pacific Daylight Time><thread=2116 (0x844)>
Submitted request successfully $$<SMS_CLIENT_CONFIG_MANAGER><Thu Oct 06 00:02:47.153 2005 Pacific Daylight Time><thread=2116 (0x844)>
======>Begin Processing request: "SOA1NTXB", machine name: "AHPDX0167" $$<SMS_CLIENT_CONFIG_MANAGER><Thu Oct 06 00:02:47.153 2005 Pacific Daylight Time><thread=1912 (0x778)>
Getting a new request from queue "Incoming" after 100 millisecond delay. $$<SMS_CLIENT_CONFIG_MANAGER><Thu Oct 06 00:02:47.153 2005 Pacific Daylight Time><thread=2116 (0x844)>
---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0)~ $$<SMS_CLIENT_CONFIG_MANAGER><Thu Oct 06 00:02:47.169 2005 Pacific Daylight Time><thread=1912 (0x778)>
Found CCR "t19f5hnu.CCR" in queue "Incoming". $$<SMS_CLIENT_CONFIG_MANAGER><Thu Oct 06 00:02:47.169 2005 Pacific Daylight Time><thread=2116 (0x844)>
---> Attempting to connect to administrative share '\\AHPDX0167\admin$' using account 'AHPDX\Labare'~ $$<SMS_CLIENT_CONFIG_MANAGER><Thu Oct 06 00:02:47.169 2005 Pacific Daylight Time><thread=1912 (0x778)>
---> The 'best-shot' account has now succeeded 44 times and failed 0 times. $$<SMS_CLIENT_CONFIG_MANAGER><Thu Oct 06 00:02:47.262 2005 Pacific Daylight Time><thread=1912 (0x778)>
---> Connected to administrative share on machine AHPDX0167 using account 'AHPDX\Labare'~ $$<SMS_CLIENT_CONFIG_MANAGER><Thu Oct 06 00:02:47.262 2005 Pacific Daylight Time><thread=1912 (0x778)>
Received request: "T19F5HNU" for machine name: "AHPDX0116" on queue: "Incoming". $$<SMS_CLIENT_CONFIG_MANAGER><Thu Oct 06 00:02:47.294 2005 Pacific Daylight Time><thread=2116 (0x844)>
---> Attempting to make IPC connection to share <\\AHPDX0167\IPC$> ~ $$<SMS_CLIENT_CONFIG_MANAGER><Thu Oct 06 00:02:47.309 2005 Pacific Daylight Time><thread=1912 (0x778)>
Stored request "T19F5HNU", machine name "AHPDX0116", in queue "Processing". $$<SMS_CLIENT_CONFIG_MANAGER><Thu Oct 06 00:02:47.325 2005 Pacific Daylight Time><thread=2116 (0x844)>
---> System OS version string "5.1" converted to 5.10 $$<SMS_CLIENT_CONFIG_MANAGER><Thu Oct 06 00:02:47.340 2005 Pacific Daylight Time><thread=1912 (0x778)>
---> Could not retrieve the heartbeat time from the client (2)~ $$<SMS_CLIENT_CONFIG_MANAGER><Thu Oct 06 00:02:47.340 2005 Pacific Daylight Time><thread=1912 (0x778)>
---> Unable to retrieve a sites list from machine "AHPDX0167". $$<SMS_CLIENT_CONFIG_MANAGER><Thu Oct 06 00:02:47.356 2005 Pacific Daylight Time><thread=1912 (0x778)>
---> Unable to retrieve travel mode switch from machine "AHPDX0167". $$<SMS_CLIENT_CONFIG_MANAGER><Thu Oct 06 00:02:47.356 2005 Pacific Daylight Time><thread=1912 (0x778)>
---> Unable to retrieve pending command value for sms client base components from machine "AHPDX0167". $$<SMS_CLIENT_CONFIG_MANAGER><Thu Oct 06 00:02:47.356 2005 Pacific Daylight Time><thread=1912 (0x778)>
---> Could not retrieve the site config timestamp from the client (2)~ $$<SMS_CLIENT_CONFIG_MANAGER><Thu Oct 06 00:02:47.372 2005 Pacific Daylight Time><thread=1912 (0x778)>
---> Unable to retrieve the mobile client version from machine "AHPDX0167". $$<SMS_CLIENT_CONFIG_MANAGER><Thu Oct 06 00:02:47.372 2005 Pacific Daylight Time><thread=1912 (0x778)>
---> Client type to be installed on AHPDX0167: Advanced client $$<SMS_CLIENT_CONFIG_MANAGER><Thu Oct 06 00:02:47.372 2005 Pacific Daylight Time><thread=1912 (0x778)>
---> Copying client files to \\AHPDX0167\admin$\system32\ccmsetup.~ $$<SMS_CLIENT_CONFIG_MANAGER><Thu Oct 06 00:02:47.387 2005 Pacific Daylight Time><thread=1912 (0x778)>
---> Copying file "C:\SMS\bin\I386\MobileClient.tcf" to "\\AHPDX0167\admin$\system32\ccmsetup\MobileClient.tcf" $$<SMS_CLIENT_CONFIG_MANAGER><Thu Oct 06 00:02:47.403 2005 Pacific Daylight Time><thread=1912 (0x778)>
---> Copying file "C:\SMS\bin\I386\ccmsetup.exe" to "\\AHPDX0167\admin$\system32\ccmsetup\ccmsetup.exe" $$<SMS_CLIENT_CONFIG_MANAGER><Thu Oct 06 00:02:47.450 2005 Pacific Daylight Time><thread=1912 (0x778)>
---> Created service "ccmsetup" on machine "AHPDX0167". $$<SMS_CLIENT_CONFIG_MANAGER><Thu Oct 06 00:02:47.856 2005 Pacific Daylight Time><thread=1912 (0x778)>
---> Started service "ccmsetup" on machine "AHPDX0167". $$<SMS_CLIENT_CONFIG_MANAGER><Thu Oct 06 00:02:47.934 2005 Pacific Daylight Time><thread=1912 (0x778)>
---> Completed request "SOA1NTXB", machine name "AHPDX0167". $$<SMS_CLIENT_CONFIG_MANAGER><Thu Oct 06 00:02:47.950 2005 Pacific Daylight Time><thread=1912 (0x778)>
Deleted request "SOA1NTXB", machine name "AHPDX0167" $$<SMS_CLIENT_CONFIG_MANAGER><Thu Oct 06 00:02:47.965 2005 Pacific Daylight Time><thread=1912 (0x778)>
<======End request: "SOA1NTXB", machine name: "AHPDX0167". $$<SMS_CLIENT_CONFIG_MANAGER><Thu Oct 06 00:02:47.965 2005 Pacific Daylight Time><thread=1912 (0x778)>

Tony

 

[kelfuego]

Just curious but is your server Windows 2003? I had some of my issues go away by backing off 2003 Service Pack 1.

Kelly Johnson MCP
Central City Concern

 

[tbrennans]

Try file and print sharing in there anyway and see if it helps Take a look at this link, it doesnt say if the firewall is enabled or not...

http://www.microsoft.com/technet/pr...faq/tfaq03.mspx#XSLTfaqSection125124121120120

at the bottom under Windows XP SP2

 

[trock1004]

Thanks to both of you for your responses!!

Kelly, the server for both of my sites are server 2000. I do have the Rollup 1 package on each of them though.

tbrennans - I checked, file and print sharing are already selected in the exceptions list and is the standard setting for all of our XP systems. And, I already have SMS 2003 SP1 installed on both my primary and secondary sites.

Tony

 

[momdude]

It looks from the log that the connection to the admin$ share was succesfull. Check on the client if the SMS service is installed?, then check in the control panel under SMS if the agent is assigned to the correct sitecode.
Check in the application and system log on the clients for any installation errors.

 

[trock1004]

Thanks for the reply momdude.

The SMS service isn't installed. And, of course, there isn't an SMS agent listed in Control Panel.

I found some information stating the following:

"Some of the problems encountered in deploying SMS in the client network inlude improperly set security on the BITS and Windows Update services."

I'm investigating this now. I will post my findings here.

Tony

 

[trock1004]

I figured out why the client wouldn't install to my XP clients. I found that something along the way had been installed, I think it was a version of Microsoft Jet installed in about May, changed some paths in the registry for the location of the repository on all of my XP machines to C:\WINNT\System32\wbem. XP doesn't have a WINNT folder of course, but 2k, 2k server and 2k3 server do and so they all installed the client without issue.

The following registry key had four values (paths) which changed and caused the problem:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WBEM\CIMOM\

Autorecover MOFs
Logging Directory
Repository Directory
Working Directory

The fix is to stop the WMI service, change the paths in the string values above to what they are supposed to be (Windows instead of WINNT), restart the computer.

Thanks to everyone for providing your responses!


Tony