SMS 2.0 client not installing...XP SP2 systems

[PhilMarcum]

I'm having a hard time getting the SMS 2.0 client to install on XP SP2 systems with and without the firewall enabled. I'm thinking I need to add the rcsvcs.exe and Wuser32.exe services to the exception list but I don't see how that's possible when the \MS\SMS\clicomp\remctrl folder structure or path isn't created on the client. Can someone shoot me a link or provide some direction on getting this to work? I need to get this working ASAP before deploying SP2.
Any responses are appreciated.

 

[tbrennans]

http://www.microsoft.com/technet/prodtechnol/winxppro/deploy/xpsp2dep.mspx

There was a doc that explained your exact problem but I cant find it for the life of me :-(

I'll keep a look out

 

[Sugrat]

The only thing that SMS 2003 needs on the client side with sp2 is print and file sharing enable, following from their faq:-



Q. Do clients need to have file and print sharing turned on for client push installation to work? (Updated April 30, 2004)
A. Yes. The Server service must be running, because you connect to the Admin$ share on the client. This is the same as in SMS 2.0.

Also, to enable Client Push Installation for client computers running Windows XP SP 2, enable File and Print Sharing in the Windows Firewall (formerly known as Internet Connection Firewall, or ICF) configuration on the Windows XP client. You might need to change the scope of the exception to define the set computers for which this port is open.

For more information about deploying SMS clients, see “Appendix C: Client Deployment Planning” in Scenarios and Procedures for Microsoft Systems Management Server 2003: Planning and Deployment on Microsoft TechNet. For information about how to configure Windows Firewall on Windows XP SP 2, search for "Windows Firewall" in Help and Support Center.


I hope this helps.

Dave

 

[PhilMarcum]

Thanks but I'm using ver2.0 and File & Print sharing is turned on on my test xp sp2 system.

 

[Sugrat]

Remote Tools, Remote Assistance, and Remote Desktop Do Not Function Properly on Computers Running Windows XP SP2
By default, SMS clients that are running Windows XP SP2 cannot be remotely managed by SMS Remote Tools, Remote Assistance, and Remote Desktop because of the default secure Windows Firewall configuration on the client.
WORKAROUND: Update the Windows Firewall settings for computers that run Windows XP SP2 with Group Policy.
Notes:

• Using a procedure below causes all Windows Firewall Group Policy settings in Windows XP SP2 to propagate to the group Policy Objects stored in Active Directory® directory services for the entire domain.

• You can perform a procedure from any computer that is a member of the domain. After you complete a procedure, Group Policy settings are permanent and can be viewed from other Microsoft Management Console (MMC) consoles available on supported operating systems.
To update Group Policy and enable Remote Desktop

1. On a computer that is running Windows XP SP2, open the Group Policy Object Editor, and then navigate to Default Domain Policy, Computer Configuration, Administrative Templates, Network, Network Connections, Windows Firewall, Domain Profile.
2. Select the Windows Firewall: Allow Remote Desktop exception option.
To update Group Policy and enable Remote Assistance

1. On a computer that is running Windows XP SP2, open the Group Policy Object Editor, and then navigate to Default Domain Policy, Computer Configuration, Administrative Templates, Network, Network Connections, Windows Firewall, Domain Profile.
2. Select the Windows Firewall: Define port exceptions option for TCP Port 135 and the Windows Firewall: Define program exceptions option for Helpsvc.exe.
To update Group Policy and enable Remote Tools

•Define port exceptions for the following ports that are necessary for each remote tool.

•TCP port 2701 for general contact, reboot, and ping
•TCP port 2702 for Remote Control
•TCP port 2703 for Chat
•TCP port 2704 for File Transfer