Clients can become orphaned if you have an SMS 2.0 and an SMS 2003 hierarchy in the same domain

This article has been archived. It is offered "as is" and will no longer be updated.
Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
In a mixed-version hierarchy, Microsoft System Management Server (SMS) clients do not work as you expect, and the clients become orphaned. This symptom occurs if the following conditions are true:
  • The SMS clients are running operating systems that are not supported in SMS 2003. For example, Microsoft Windows 95 is not supported in SMS 2003.
  • The site server has been upgraded from SMS 2.0 to SMS 2003.
You can see this symptom by using the System Management tool in Control Panel. On the Sites tab, you can see the entries for the sites that manage the computer. However, on the Components tab, none of the components have an Installed status.
This problem occurs if there is an SMS 2.0 and an SMS 2003 hierarchy in the same domain and the following conditions are true:
  • User logon scripts have been updated by an SMS 2.0 site in the same domain as the SMS hierarchy that you are upgrading to SMS 2003.
  • User logon scripts contain client installation methods for both SMS 2.0 and SMS 2003.
  • The SMS clients are running operating systems that are not supported in SMS 2003.
Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To recover a client computer that has this problem, follow these steps:
  1. Stop all SMS client processes.
  2. Remove the %WINDIR%\MS\SMS folder and its subfolders.
  3. Delete the
    registry key and all its sub-keys.
  4. Remove all SMS-related files in the %WINDIR%\Temp folder.
  5. Log off the computer, and then log back on to the computer.
If you have added a Capinst.exe command line to the logon script, this procedure starts the SMS 2003 logon script initiated client installation. This installation installs the Windows 95 client in an SMS 2.0 site if the computer is in the boundaries of an SMS 2.0 site.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Logon points are not supported in SMS 2003. Before you upgrade an SMS 2.0 site to SMS 2003, you must disable Windows Networking Logon Discovery and Windows Networking Logon Client Installation. This process takes some time because it involves replication between domain controllers that are designated for Windows Networking Logon Client Installation, or Windows Networking Logon Discovery, or both. Do not continue with the upgrade until you make sure that the logon points are removed

For more information, see the "Preparing a Site for Upgrade" section in Chapter 14, "Upgrading to SMS 2003" in the Microsoft Systems Management Server 2003 Concepts, Planning, and Deployment Guide.
To obtain the most current version of the product documentation and additional technical reference material for SMS 2003, visit the following Microsoft Web site:
fail setup stopped deploy

Article ID: 886010 - Last Review: 01/15/2015 00:57:32 - Revision: 1.4

Microsoft Systems Management Server 2003, Microsoft Systems Management Server 2003 Service Pack 1

  • kbnosurvey kbarchive kbprb kbsmsdeploy kbsmsinstall kbsmsclients kbsms2003bug KB886010