How to remove a primary site in Systems Management Server 2.0 (840676)


The information in this article applies to:

  • Microsoft Systems Management Server 2.0
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

INTRODUCTION

You may have to remove and then reinstall a Microsoft Systems Management Server (SMS) version 2.0 primary site. For example, you must reinstall an SMS 2.0 primary site if you want to change the site code or the NetBIOS name of the site server computer. To remove an SMS 2.0 primary site, you must complete the following tasks:
  • Turn off all client installation and discovery methods.
  • Remove all site system roles for the primary site that are installed on remote computers.
  • Remove the SMS 2.0 clients that report to the primary site.

    Note Although removing the SMS 2.0 clients is optional, we recommend that you remove the SMS 2.0 clients.
  • Remove the SMS 2.0 primary site software.

MORE INFORMATION

To remove an SMS 2.0 primary site, follow these steps.

Step 1: Turn off all client installation and discovery methods

  1. Click Start, point to Programs, point to Systems Management Server, and then click SMS Administrator Console.
  2. Expand the Site Database\Site Hierarchy\your site name\Site Settings subtree, where your site name is your site code and your site name.
  3. Click Client Installation Methods, and then double-click Windows Networking Logon Client Installation.
  4. Click to clear the Enable Windows Network Logon Client Installation check box, and then click OK.
  5. Double-click Windows NT Remote Client Installation.
  6. Click to clear the Enable Windows NT Remote Client Installation check box, and then click OK.
  7. Click Discovery Methods, and then double-click Windows Networking Logon Discovery.
  8. Click to clear the Enable Windows Networking Logon Discovery check box, and then click OK.
  9. Repeat steps 7 and 8 for Windows NT User Account Discovery, Windows NT User Group Discovery, Heartbeat Discovery, and Network Discovery.

    Make sure that all discovery methods are turned off. To do this, make sure that the check box for each discovery method is cleared.
If the option to modify user logon scripts was selected, SMS removes references to SMSLS.bat from user logon scripts and removes the Logon Point(s) for the primary site. The SMSLOGON folder and the SMS_LOGON_DISCOVERY_AGENT service are removed from the domain controllers.

Note: If Logon Point(s) are shared among different SMS sites, the SMSLogon folder is not removed from the domain controllers. However, the SMSLogon\Sites\sitecode folder is removed, where sitecode is the site code of the primary site that you want to remove. You can monitor the progress by viewing the Nt_logon.log file. The Nt_logon.log file is located in the SMS\Logs folder of the primary site server computer.

Step 2: Remove the site boundaries for the primary site to automatically remove the SMS client software from client computers

  1. In the SMS Administrator Console, right-click Site Settings, and then click Properties.
  2. Click the Boundaries tab, remove the IP subnets that are listed, and then click OK.
Note SMS 2.0 clients connect to the Client Access Point (CAP) every 23 hours to run a maintenance cycle. During this cycle, if the client software detects that it is no longer included in the site boundaries, the client software is automatically removed. We recommend that you wait approximately two days to allow sufficient time for all the clients to be removed. For this method to work, client computers must be connected to the network and must be able to access the CAP. You can also use the 20clicln.bat file to manually remove the SMS client software from clients that are not connected to the network or that cannot access the CAP.

For additional information about how you can remove the SMS client software, click the following article number to view the article in the Microsoft Knowledge Base:

199078 How to remove a Systems Management Server 2.0 client

Step 3: Remove all site system roles for the primary site that are installed on remote computers

  1. In the SMS Administrator Console, click Site Settings\Site Systems.

    All computers that perform a function for the primary site are listed.
  2. Right-click a computer that is listed, and then click Properties.
  3. On the Client Access Point tab, click to clear the Use this site system as a client access point check box.
  4. On the Distribution Point tab, click to clear the Use this site system as a distribution point check box.
  5. On the Software Metering Server tab, click to clear the Use this site system as a software metering server check box.
  6. Click OK.

Step 4: Remove the SMS 2.0 clients that report to the primary site

  1. Click Start, point to Programs, point to Systems Management Server, and then click SMS Setup.
  2. Click Next two times, click Remove SMS, and then click Next.
  3. Click to select the Delete SMS site database and Delete software metering database check boxes, and then click Next.
  4. Click Finish.

Step 5: Verify that all SMS groups and user accounts have been removed from the site server, the site systems, and the domain

Make sure that the following groups and accounts are removed

  • The SMS Admins group (local)
  • The SMSClient_primary_site_code account (domain)
  • The SMS&_domaincontroller account, where domaincontroller is the NetBIOS name of the domain controllers that had the SMS client installed (domain)

    Important Do not remove the SMS&_ domaincontroller account if the domain controller is also managed by other SMS sites.
  • The SMSCliToknAcct& account (domain)

    Important Do not remove this account if the computer is a domain controller that is also managed by other SMS sites.
  • The SMSCliToknLocalAcct& account (local) after SMS 2.0 Service Pack 5 (SP5)
  • The SMSInternalCliGrp group (domain)
  • The SMSCliSvcAcct& account (local)
  • The SMSLogonSvc account (Logon Points)

    Important Do not remove this account if the computer is a domain controller that is also managed by other SMS sites.
  • The SMSServer_primary_site_code account (domain)
  • The SMS Service account (domain)

Make sure that the SMS services are removed

  1. Click Start, point to Administrative Tools, and then click Services.
  2. Make sure that the following SMS services are removed:
    • SMS Client Service
    • SMS Hardware Inventory Agent Service
    • SMS Remote Control Agent
    • SMS_EXECUTIVE
    • SMS_NT_LOGON_DISCOVERY_AGENT
    • SMS_SITE_BACKUP
    • SMS_SITE_COMPONENT_MANAGER
    • SMS_SQL_MONITOR
    • SMS_LICENSE_SERVER

If any SMS services remain, stop the services, and then manually remove the remaining SMS services

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.
  1. Click Start, and then click Run.
  2. Type regedit, and then click OK.
  3. Locate and then click the following registry key:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services

  4. Delete the following sub-keys if they exist:
    • Clisvc
    • Crystal Info Agent
    • Crystal Info APS
    • Crystal Info Sentinel
    • SMS Hardware Inventory Agent Service
    • SMS_EXECUTIVE
    • SMS_NT_LOGON_DISCOVERY_AGENT
    • SMS_SITE_BACKUP
    • SMS_SITE_COMPONENT_MANAGER
    • SMS_SQL_MONITOR
    • LICSVR_SERVICE

Make sure that the following folders are removed, if they exist

  • SMS
  • SMSDATA
  • SMSPKG
  • SMSPKGx$
  • SMSLOGON (domain controller only)
  • CAP_primary_site_code
  • Swmtr
Note You may have to restart your computer to remove any remaining files or folders.
Modification Type:MinorLast Reviewed:6/13/2005
Keywords:kbService kbCAP kbSiteComp kbServer kbsmsAdmin kbsetup kbhowto kbinfo KB840676 kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.