How to remove and rebuild a SMS 2003 (SCCM 2007) secondary site

To manually stop and remove the failed secondary site, follow these steps:

1. Click Start, point to All Programs, point to Systems Management Server, and then click SMS Administrator Console.
2. Locate the Site Settings\Addresses subtree.
3. Right-click the address for the failed secondary site, and then click Delete.
4. To use the Preinst.exe tool on the SMS parent site to delete the failed secondary site from the database, follow these steps: 
5. On the SMS primary site (parent) computer, click Start, and then click Run.
6. Type cmd in the Open box, and then click OK.
7. At the command prompt, type cd\, and then press the ENTER key.
8. Type cd sms\bin\i386\00000409, and then press the ENTER key.
9. Type Preinst /DELSITE SiteCode ParentCode, and then press the ENTER key.
   
   NoteSiteCode is the site code of the secondary site, and ParentCode is the site code of the parent site.
11. To remove any pending or active jobs to a site, type Preinst /DELJOB SiteCode , and then press the ENTER key.
    
    NoteSiteCode is the site code of the secondary site. For more information about how to use the PREINST tool, click the following article number to view the article in the Microsoft Knowledge Base:
    212978  (http://support.microsoft.com/kb/212978/ ) Description of Preinst.exe for Systems Management Server 2.0
12. To make sure that the secondary site is completely removed, follow these steps:
    1. Make sure that no SMS or Winmgmt services are running on the computer, including the SMSBootstrap service. If these services are running, stop the services, and then change the Startup type to Manual.
    2. Use Registry Editor to make sure that the following SMS registry keys are removed:
       • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS
       • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NAL
       • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SMS_Executive
       • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SMS_Site_Component_Manager
       • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SMS_Bootstrap
       • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CLISVC
       • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SMS_Discovery_Data_Manager
       • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SMS_Lan_Sender
       • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SMS_Scheduler
       • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SMS_Site_Backup
       • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SMS_Software_Metering_Processor
       • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SMS_Status_Manager
       • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_CLISVC
       • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_SMS_BOOTSTRAP
       • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_SMS_EXECUTIVE
       • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_SMS_HARDWARE_INVENTORY_AGENT_SERVICE
       • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_SMS_KEY_CREATION_SERVICE
       • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_SMS_SERVER_BOOTSTRAP_servername
       • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_SMS_SITE_COMPONENT_MANAGER
       • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application\SMS Client
       • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application\SMS Performance Data Provider
       • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application\SMS Provider
       • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application\SMS Remote Control
       • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application\SMS Server
       • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application\SmsClient
    3. Make sure that the following folders are removed:
       • X:\SMS
       • X:\SMSBootstrap.log
       • X:\SMSBootstrap.ini
       • X:\SMSBootstrap.pkg
       • %Winnt%\MS\SMS
       NoteX is the SMS installation drive.
       
       Note You may have to restart the computer to remove some of these files and folders.
    4. Make sure that the CAP_SiteCode and SMSPKGdrive$ shares and their corresponding folders are deleted from the client access point computers.
       
       NoteSiteCode is the site code of the secondary site, and drive is the drive letter.
    5. Make sure that any site-specific accounts or groups are deleted, including the SMS_SiteSystemToSiteServerConnection_sitecode and SMS_SiteToSiteConnection_SiteCode groups.
       
       NoteSiteCode is the site code of the secondary site.
    6. Remove the following objects from Internet Information Services (IIS) Manager (if they exist).
       
       Under Application Pools (only on IIS 6.0):
       • CCM Server Framework Pool
       • SMS Distribution Points Pool
       • SMS Management Point Pool
       • SMS Server Location Point Pool
       Under the default Web Site (on IIS 5.0 or IIS 6.0):
       • CCM_Incoming
       • CCM_Outgoing
       • CCM_System
       • SMS_DP_
       • SMS_MP
       • SMS_SLP
    7. Restart the server.
       
       Note The server must be restarted to make sure that any of the SMS services that you deleted from the registry in step 6b are no longer running. If these services are still running when you try to reinstall the secondary site, the Setup program will try to remove these services, but the removal will fail because they are already gone from the registry.

After these items are removed, you can reuse the site code to reinstall the secondary site.

How to rebuild the secondary site

1. Reinstall the secondary site. As soon as possible, the secondary site installation should be started to minimize the effect on clients.
   
   To speed the installation, see the "Installing a Secondary Site Using SMS Setup" topic in the SMS 2003 Deployment Guide . To obtain this guide, visit the following Microsoft Web site:
   http://technet.microsoft.com/en-us/library/cc181264.aspx (http://technet.microsoft.com/en-us/library/cc181264.aspx)
   This section explains how to set up the site directly from the CD-ROM. This step lets you bypass the 76 megabyte (MB)-network installation package and to install directly from the CD-ROM.
   
   Important If you use Standard security, verify that the correct accounts and passwords have been specified. Problems can be very difficult to diagnose and repair and may require that you repeat the procedure. To make sure of success, test the account beforehand. To do this, log on to the new primary site by using the specified account, and then connect to the secondary site's c$, d$, and admin$ shares. Create, read, and write to folders and files from the secondary site drives to the primary site drives and back again.
2. Reconfigure the secondary site. Immediately after you install the secondary site and while the site configuration update is being propagated to the parent site, use the SMS Administrator MMC to configure settings that will prevent clients from having to unnecessarily change their configuration.