Article ID: 886132 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
After you upgrade a Microsoft Systems Management Server (SMS) 2.0 secondary site server to SMS 2003 Service Pack 1 (SP1), the following symptoms may occur:
This problem occurs when the following conditions are true:
To work around this problem, run the SMS Manual Installation Wizard (Smsman.exe) to upgrade the Microsoft Systems Management Server (SMS) 2.0 client to an SMS 2003 SP1 Legacy Client. To do this, follow these steps:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
SMS 2003 SP1 cannot push the SMS 2003 SP1 Legacy Client when the site boundaries of the secondary site do not overlap with the site boundaries of the primary site. The SMS 2003 SP1 Legacy Client must be pushed from a primary site.
When you run the Smsman.exe utility on the SMS 2.0 client computer, the SMS 2.0 client components are upgraded to SMS 2003 SP1 client components.
If you experience this problem on multiple computers, you can create an advertisement for the Smsman.exe utility to target computers that were not upgraded after you upgraded the secondary site server. By default, SMS 2003 installs a query that is named SMS clients that have not been upgraded to SMS 2003. View the results of this query to identify client computers that have not been upgraded. For additional information about related issues, click the following article number to view the article in the Microsoft Knowledge Base:
833177For additional information about how to use SMS 2003 for software distribution and for patch management, visit the following Microsoft Web site:
(http://support.microsoft.com/kb/833177/ )The SMS Manual Installation Wizard cannot successfully upgrade an SMS 2.0 Client to SMS 2003 Legacy Client
Article ID: 886132 - Last Review: October 27, 2013 - Revision: 1.3