This post shows the steps to remove secondary site using configuration manager console. If you have got clients in remote network locations and slow WAN link, secondary site is the solution. You can manage the secondary site using CAS. Also, you can manage it using it’s parent primary site. When a secondary site is deployed, distribution point and management point is also installed. Most of all secondary sites automatically install SQL Server Express during site installation. You could also install use local instance of SQL server instead of SQL express. More information about secondary sites and it’s usage is documented here.
Remove Secondary Site Using Configuration Manager Console
Let’s look at the procedure to remove secondary site using configuration manager console. Initiate the secondary site un-installation only when it is connected to CAS or primary site. In the configuration manager console, navigate to Administration > Overview > Site Configuration > Sites. Right click Secondary site and click Delete.
In the next step you see two options Uninstall and Delete.
Choose Uninstall the secondary site option if you want to remove a secondary site that is accessible on network. Choosing this option uninstalls configmgr from secondary site server and deletes all the site info and resources from SCCM hierarchy.
Choose Delete the secondary site option if you know that a site install has failed or if the site is visible in SCCM console even after uninstalling it. This option deletes the info about secondary site and it’s resources from SCCM hierarchy. However it leaves ConfigMgr installed on secondary site server.
Choose Uninstall the secondary site and click Next.
On Summary page click Next.
Finally on the completion page click Close.
On the secondary site server, open the ConfigMgrSetup.log file and hman.log file on Primary site server to monitor the uninstallation process. In the below screenshot we see that we have successfully uninstalled the secondary site from ConfigMgr hierarchy.