SCCM Remove a secondary site from a hierarchy

Today I will be talk about how to remove secondary site. We all knows how to remove but some time even if

You are doing correct way your secondary site will not get remove.

 

Some of the important tips which we must know.

 

Point 1: You cannot move a secondary site or reassign a secondary site to a new parent primary site.

Point 2: To be removed from a hierarchy, a secondary site must be deleted from its direct parent site.

Point 3: Use the Delete Secondary Site Wizard from the Configuration Manager console to remove a

Secondary site.

Point 4: When you remove a secondary site, you must choose whether to delete it or uninstall it:

 

·         Uninstall the secondary site. Use this option to remove a functional secondary site that is accessible from the network. This option uninstalls Configuration Manager from the secondary site server, and then deletes all information about the site and its resources from the Configuration Manager site hierarchy. If Configuration Manager installed SQL Server Express as part of the secondary site installation, Configuration Manager will uninstall SQL Express when it uninstalls the secondary site. If SQL Server Express was installed before you installed the secondary site, Configuration Manager will not uninstall SQL Server Express.

·         Delete the secondary site. Use this option if one of the following is true:

o    A secondary site failed to install

o    The secondary site continues to be displayed in the Configuration Manager console after you uninstall it

This option deletes all information about the site and its resources from the Configuration Manager hierarchy, but leaves Configuration Manager installed on the secondary site server.

Very important: If we do any Human error like without Follow steps we have deleted database and application

(Secondary Site) still running in console. What you will do. Best way follow above Point 2 to Point 4 and follow

Below steps to clean up.  

 

1.       Please follow these steps to manually delete the Secondary Site from the Secondary site server

2.       We also used the PREINST tool to remove the pending jobs.

3.       On the ConfigMgr primary site (parent) computer, click Start, and then click Run.

4.       Type cmd in the Open box, and then click OK.

5.       At the command prompt, type cd\, and then press the ENTER key.

6.       Type cd \<SiteServerName>\SMS_<SiteCode\bin\X64\00000409, and then press the ENTER key.

7.       To remove any pending or active jobs to a site, type Preinst /DELJOB SiteCode , and then press the ENTER key.

8.       We deleted the Secondary Site from the console of parent site.

To remove secondary site, type Preinst / DELSITE  SiteCode , and then press the ENTER key.

For more preinst tool refer this URL

10.   Click Start, point to All Programs, point to Systems Management Server, and then click ConfigMgr Administrator Console.

11.   Locate the Site Settings\Addresses subtree.

12.   Right-click the address for the failed secondary site, and then click Delete.

13.   Then we cleaned the registry, by taking the backup of the HKLM Node


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\SmsClien


Once completed Restart Server. Now you are good with cleanup. 

keep watching space @hiraniconfigmgr.com with many experts are here to share solutions

Many Problem, One Place solutions.

Thanks & Regards

Haresh Hirani

Email: hiraniconfigmgr@outlook.com, hiraniconfigmgr@gmail.com

Facebook https://www.facebook.com/Hiraniconfigmgr-120189361980772/

Follow me: https://www.linkedin.com/in/hiraniconfigmgr



0 Comments

    No Comments

Leave a Comment