How to Recover SCCM CB Primary Server Using SQL Database Backup Configuration Manager ConfigMgr

How to Recover SCCM CB Primary Server Using SQL Database Backup Configuration Manager ConfigMgr with the following video tutorial from the HTMD community.

Let’s see “How to Recover SCCM CB Primary Server Using SQL Database Backup”. Sometimes you need to restore the SQL on the new virtual server or hardware. I have included that also in the below post.

So the important point over here is that “SCCM CB full backup” is not required for restoring your SCCM CB primary server. Rather, you can restore or recover the primary site server from SQL backup and CD.Latest folder backup (along with package source folders, WSUS folders/DBs, etc…).

Prerequisites:

Following are the prerequisites to Recover SCCM CB Primary Server Using SQL Database Backup Configuration Manager ConfigMgr.

  • Remove existing SCCM servers from the domain, ensuring you know local admin account details.
  • Shutdown existing SCCM servers
  • Rename existing SCCM servers in Vcenter or HyperV to .old
  • Rename the new SCCM server in Vcenter/HyperV to existing SCCM server names
  • Delete existing SCCM servers from AD
  • Take new SCCM/ConfigMgr servers off the domain and reboot, ensuring you have local admin account details.
  • Log onto new SCCM/ConfigMgr servers using the local admin account
  • Change IPs of new SCCM servers to reflect old SCCM server IP details
  • Change new SCCM servers names to existing SCCM server names and reboot
  • Log on to new SCCM servers as the local admin account
  • Add new SCCM servers to the domain and reboot
  • Verify OU, System Management Access, and AD membership information of new SCCM/ConfigMgr servers. Reboot if you have made any changes above
  • Storage migrates any back-end storage in VMware/HyperV to ensure that vmdk files and vmx/VHDX files are named correctly.

How to Recover SCCM CB Primary Server Using SQL Database Backup Configuration Manager ConfigMgr?

I’ve another 3 posts and videos related to SCCM Current Branch backup and recovery options. You can refer to those posts from here.

The installation of the SCCM CB standalone primary server should be done from CD.Latest folder (p.s – this is because we are making a recovery of the server). I used the native SQL backup option from SQL management studio to backup the SQL DB.

And once the recovered server OS is up and running with all the prerequisites(ADK, WSUS, SQL), I restored the SQL DB using management studio from the SQL full backup file. All these processes are explained in the below video tutorial.

Recover SCCM CB Primary Server Using SQL Database Backup
Recover SCCM CB Primary Server Using SQL Database Backup

Also, note the “post-recovery” process apart from the removal and addition of Intune subscriptions. It would be best to make sure that all the accounts configured in the SCCM ConfigMgr CB console should be removed and added back.

If there is any hotfix installed on the SCCM CB server, then we need to install the same hotfix after the completion of the recovery Wizard.

Following are the prerequisites which we need to follow during the recovery process SCCM CB primary server:-

  • The hostname Should be the same :
  • Drive Letters should be the same :
  • The installation path should be the same:
  • Should have the same patch level:
  • Better to have the same IP: All the prerequisite apps should be installed: SQL Databased is already restored (manually):

Recover SCCM CB Primary Server Using SQL Database Backup

Here is the end-to-end recovery experience video. (1) How to Recover or restore SCCM CB Primary server using SQL Database Backup – YouTube.

Resources

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…