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.
Along with this, we changed the SQL DB server from a clustered instance to a single instance. Also, the ConfigMgr SCCM DB server is moving from physical box to 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.
Along with SCCM ConfigMgr 2007 central Database, we need to move the WSUS database as well as SSRS. This adds to the complexity of this movement. Moving SCCM 2007 DB is documented over here by Sudheesh N.
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 following 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 has 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 here : Unable to connect to site database after it’s moved to a failover cluster. When I tried to launch SCCM ConfigMgr console after migration, I was getting following errors in SmsAdminUI.log and Smsdbmon.log !!
As mentioned in the above post these errors were pointing to SPN registration issue. My SQL 2008 Database SQL Server (MSSQLSERVER) service is running with domain service account. This SQL 2008 service account is already registered to Active Directory SPN (Service Principal Name) using following commands. So SQL service account was pointing to correct host name and FQDN along with 1433 port of SQL server.
SPN registration commands
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. Need to just make sure to remove the old SQL DB site system roles (there must be two DB site systems roles because of clustered instance).
Simple resolution for complex problem 🙂 Hope this helps !!