The push installation of the Systems Management Server 2003 Advanced Client fails on Windows XP Service Pack 2-based client computer

Article translations Article translations
Article ID: 920852 - View products that this article applies to.
Expand all | Collapse all

SYMPTOMS

When you try to push the Microsoft Systems Management Server (SMS) 2003 Advanced Client to a Microsoft Windows XP Service Pack 2 (SP2)-based client computer, the Advanced Client installation may fail. Error messages that resemble the following may be logged in the Ccm.log file:
ERROR: Unable to connect to remote registry for machine name "Client computer name", error 53. $$<SMS_CLIENT_CONFIG_MANAGER><Date Time><thread=1324 (0x52C)
ERROR: Unable to access target machine for request: "program name", machine name: "Client computer name", error code: 53 $$<SMS_CLIENT_CONFIG_MANAGER><Date Time><thread=1324 (0x52C)> STATMSG: ID=3015 SEV=W LEV=M SOURCE="SMS Server" COMP="SMS_CLIENT_CONFIG_MANAGER" SYS=Site server name SITE=Site code PID=1696 TID=1324 GMTDATE=Date Time ISTR0="Client computer name" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 $$<SMS_CLIENT_CONFIG_MANAGER><Date Time><thread=1324 (0x52C)> Retry request id for "program name" set to "Client computer name" $$<SMS_CLIENT_CONFIG_MANAGER><Date Time><thread=1324 (0x52C)> Stored request "Client computer name", machine name "Client computer name", in queue "Retry". $$<SMS_CLIENT_CONFIG_MANAGER><Date Time><thread=1324 (0x52C)> <======End request: "Client computer name", machine name: "Client computer name". $$<SMS_CLIENT_CONFIG_MANAGER><Date Time><thread=1324 (0x52C)>
WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account domain name\user name (000004b3) $$<SMS_CLIENT_CONFIG_MANAGER><Date Time><thread=764 (0x2FC)>
WNetAddConnection2 failed (LOGON32_LOGON_INTERACTIVE) using account domain name\user name (000004b3) $$<SMS_CLIENT_CONFIG_MANAGER><Date Time><thread=764 (0x2FC)> Waiting for change in directory "D:\SMS\inboxes\ccr.box" for queue "Incoming", (30 minute backup timeout). $$<SMS_CLIENT_CONFIG_MANAGER><Date Time><thread=2584 (0xA18)>

CAUSE

The SMS_CLIENT_CONFIG_MANAGER (CCM) cannot connect to the client computer share "Admin$". The client computer "Admin$" is not available because the Computer Browser service on the Windows XP SP2-based client computer is not started.

RESOLUTION

To resolve this issue, enable File and Printer Sharing on the Windows XP SP2-based client computer. To do this, follow these steps:
  1. On the Windows XP SP2 client computer, click Start, click Run, type Firewall.cpl, and then click OK.
  2. In the Windows Firewall properties page, click the Exceptions tab.
  3. Click to select the File and Printer Sharing check box, and then click OK.
  4. On the site server, initiate the Advanced Client push to install the Advanced Client.

MORE INFORMATION

For more information about ICF and the Computer Browser service in Windows XP SP2, click the following article number to view the article in the Microsoft Knowledge Base:
875362 The Computer Browser service does not start and event ID 7024 is logged when you restart your Windows XP Service Pack 2-based computer

Properties

Article ID: 920852 - Last Review: October 27, 2006 - Revision: 1.1
APPLIES TO
  • Microsoft Systems Management Server 2003
Keywords: 
kberrmsg kbtshoot kbfirewall kbnetwork kbprb kbfileprintservices kbsmsclients KB920852

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com