SCCM Clustered DB Migration to Single Instance SQL ConfigMgr Endpoint Manager. Through this post, I’m trying to explain my experience related to SCCM ConfigMgr central Server SQL DB migration.
We had migrated SCCM ConfigMgr 2007 central site DB from SQL 2005 to SQL 2008 R2. We also changed the SQL DB server from a clustered instance to a single instance.
Also, the ConfigMgr SCCM DB server is moving from a physical box to a virtual one. So, we don’t need clustering for a virtual box; the redundancy of the SQL server is taken care of by VMware VMotion.
SCCM Clustered DB Migration to Single Instance SQL ConfigMgr Endpoint Manager
Once migration is completed as per the document, you need to verify and confirm the sitecomp.log file whether the following entry is present or not. Once the next entry is there, you can restart the SCCM 2007 central site server and remote site system servers (Remote MPs, DPs, or SUPs – if required).
SCCM WSUS database (software update) move and remote SUP server reconfiguration have been completed by changing the following registry key in the remote SUP server.
After following the documented process, I got stuck with SCCM console connectivity issues explained in the following blog post: Unable to connect to the site database after it’s moved to a failover cluster. When I tried to launch the SCCM ConfigMgr console after migration, I got the following errors in SmsAdminUI.log and Smsdbmon.log !!
As mentioned in the above post, these errors pointed to the SPN registration issue. My SQL 2008 Database SQL Server (MSSQLSERVER) service runs with a domain service account. This SQL 2008 service account is already registered to Active Directory SPN (Service Principal Name) using the following commands. So SQL service account pointed to correct hostname and FQDN along with 1433 port of SQL server.
SPN registration commands – SCCM Clustered DB Migration to Single Instance SQL
So what is the issue now? Resolution:-
There is no need to worry about SCCM ConfigMgr SQL clustered instance DB to single instance SQL DB. The SCCM repair or reconfiguration wizard will take care of this complexity. I need to remove the old SQL DB site system roles (there must be two DB site systems roles because of clustered instances).
Simple resolution for complex problems:) I hope this helps !!
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 logger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. He writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc…