Uninstall Remove SCCM ConfigMgr CAS Primary Secondary server. This is the post where we can find some useful details about removal or uninstallation or deletion of Site server (s) rather than Decommission of sites and Hierarchies.
Also, we’re going to discuss the difference between the options Uninstall and Delete (Secondary site/s).
Uninstall Remove SCCM ConfigMgr CAS Primary Secondary server
We will be able to REUSE the site code of secondary server/s if it is no longer in use in your Configuration Manager hierarchy or the Active Directory forest. Uninstall Remove SCCM ConfigMgr CAS Primary Secondary server.
However, Site codes cannot be used more than once in a ConfigMgr hierarchy for a CAS or primary sites. If you reuse a site code, you risk having object ID conflicts in your ConfigMgr hierarchy.
Another way to uninstall /remove SCCM 2012 CAS server from hierarchy https://configmgrblog.com/2013/07/24/want-to-get-rid-of-your-configmgr-2012-central-administration-site/
When we want to remove the entire SCCM/ConfigMgr hierarchy with many site servers (primary and secondary etc..), we’ve to follow a bottom-up approach. That means, Removing secondary sites attached to primary sites, primary sites from the central administration site (CAS), and then the central administration site (CAS) itself.
More Details on decommission of sites and Hierarchies through TechNet.
Uninstall/Remove/Decommission Secondary Site
1. Go To Administration—> Site Configuration –> Sites, click on the secondary site you want to delete, and select the Delete option in the ribbon.
2. There are two options in the uninstallation wizard.
a) Uninstall the secondary Site
Use the first option, “Uninstall the secondary Site,” when you want to remove a functional secondary site accessible on the network.
When you uninstall a secondary site, this action uninstalls ConfigMgr from the secondary site server and deletes all information about the site and its resources from the ConfigMgr hierarchy.
b) Delete the secondary Site
Use Delete the secondary Site option if one of the following conditions is true:
– A site has failed to install
– The site remains visible in the ConfigMgr console after you’ve uninstalled it.
When you delete a secondary site, this action deletes information about the secondary site and its resources from the ConfigMgr hierarchy and leaves ConfigMgr installed on the secondary site server.
Uninstall/Remove/Decommission Primary or CAS site
You need to follow the same steps to remove the standalone/CAS attached Primary server. The same applies to CAS server removal. But the approach should always be BOTTOM UP.
What does Bottom-Up mean? – You need to remove in the following order
- Remote Site Roles (MP,SUP etc)
- Secondary servers
- Primary servers
- CAS
1. log in to the primary or CAS server and Click Configuration Manager Setup from the Start menu
2. Select the “Uninstall a Configuration Manager Site” option.
When there is a secondary site attached to the primary site, we must remove the secondary site before you can uninstall the primary site. Otherwise, it won’t allow you to proceed with the uninstallation.
When there is a primary site attached to the central administration site (CAS), we must uninstall the primary site before you can uninstall the central administration site.
3. Click Yes and Next
4. We can verify the ConfigMgrSetup.log file for more details about the uninstallation of the site.
INFO: Uninstallation the CAS site
INFO: Configuration Manager Setup - Uninstallation
INFO: Entering THREAD_Deinstall
5. Review the ConfigMgrSetup.log file to check whether Uninstallation has been completed successfully or not.
INFO: Completed the uninstall of the Configuration Manager Site
Author
Anoop is Microsoft MVP! He is a Solution Architect in enterprise client management with more than 20 years of experience (calculation done in 2021) in IT. He is a blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. E writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc…
Very good and informative article…
Hi Anoop,
This was such an informative article. However I am facing a problem where I am unable to remove the primary configuration site, I am being shown an error that says “Attempted to perform an unauthorized operation”. I have all the admin rights and still am seeing this error. Kindly help me out.
Regards,
Lohith
Hi ! – Have you removed all the secondary sites (if you’ve any) under this primary site? That would be the first step you must try.
Anoop
Hi Anoop, There is a google ad which hides the top portion of the blog content. i couldn’t read the first para.
HI Peer ! – Hope, it’s better now.
What about the roles installed on the Secondary Site servers ? Is it required to remove the roles (eg. SUP, MP, DP etc) prior to Uninstall of secondary site?
Thank you
Is this the Abhay Patil whom I know 🙂
Hi Anoop!
I have a disconnected network withsome primary site and secondary sites with a CAS on top. the CAS has developed some issues( SMS Executive is getting switched of every minute and the component manager is not available. Kindly suggest how to recover or reinstall CAS
Thanks and Regards
Kshitij
Try this link. Could be SCCM expired https://www.anoopcnair.com/sccm-is-expired/
I’m facing a challenge since the beginning After installation of CAS and Primary server I found there’s a replication process going for long long time even more than 48hrs Primary to CAS replication wasn’t happened, also updating to 1706 was also stuck so I decided to delete Primary site and instead of 1606 I will install 1802 in both the sites. Now I’ve uninstalled Primary site successfully but whenever I’m trying to uninstall CAS it’s showing “There are sites attached to this site. You must uninstall the attached sites before you can uninstall this site”
I had only one Primary server and uninstalled successfully but CAS isn’t uninstalling.
Please help I can share my PC if you need to see it in person.
I will try – check the log files to get more details or check the registry/SQL DB to confirm whether there is any trace of primary server. I will give a restart as well