Video Guide How to Migrate SCCM CB Primary server to New Hardware

This is a video tutorial which explains how to Migrate ConfigMgr SCCM CB 1606 Primary Server to New Hardware.

24

How to Migrate SCCM CB 1606 primary server to new hardware or new virtual server? How to restore SCCM CB primary server from full SCCM backup? I’ll try to answer these two questions in this blog post and the video.  I used SCCM CB full backup to migrate primary server into virtual server. In this scenario, I’ve SCCM CB primary site server and Database server on the same box. After the migration Intune/cloud communication was not working and all the logs (CloudUserSync.log, DMPUploader.log and DMPDownloader.log) filled with “Certmgr has not installed certificate yet, sleep for 1 minutes.“. The resolution was to remove Intune subscription and add it back. More details about “Migrate SCCM CB Primary server to New Hardware or to new virtual server”

Following are the prerequisites which we need to follow while migrating SCCM CB primary server to new hardware:-
Hostname Should be same :
Drive Letters should be same :
Installation Path should be same:
Should have same patch level:
Better to have the same IP:
The following steps will help to complete the migration steps easily  
1.Document local SMS group memberships of existing server
 
2.Perform differential Robocopy of the backup folders to the new server (Package Source\DP files\WSUS)
 
3.Shutdown Current SCCM CB Server
 
4.Delete AD object of existing SCCM Server from Active Directory Users and Computers
 
5.Rename new server to the old SCCM CB server name
 
6.Give New Server OLD IP address (Optional)
 
7. Perform Domain Join of new SCCM CB server. Provide FULL ACCESS to new SCCM CB computer object in System Management container and also add to respective AD groups wherever required.
 
8. Install all the prerequesites – ADK, WSUS, SQL etc….
 
9. Run the setup from CD.Latest folder to get the latest binaries of existing CB site

24 COMMENTS

  1. Hi
    I want to migrate sccm 1606 to new server – but old OS is Windows server 2008 R2.

    are this steps well ?:

    new server is w2012 R2. Should I uninstall WSUS on old server and then do full backup ?

    thanks

  2. I don’t think you need to do uninstall of WSUS to take full back. You should take full backup with WUS and SUP etc… Also WSUS uninstallation is recommended only for in place upgrade of OS 2008 R2 to OS 2012 R2. Otherwise it’s normal process.

  3. Hi Anoop,
    Currently, I’m managing several departments (which are located in different regions) using SCCM 2012 R2 with a single Primary site and a Distribution Point in each department. SCCM is installed on Windows Server 2008 R2 and plan is to install CM1606 on a new server (Windows Server 2016). I’m asked to move each department gradually to new site. How should I plan for this?
    Thank you.

  4. Hi Anoop,
    Currently, I’m managing several departments (which are located in different regions) using SCCM 2012 R2 with a single Primary site and a Distribution Point in each department. SCCM is installed on Windows Server 2008 R2 and plan is to install CM1606 on a new server (Windows Server 2016). I’m also asked to create a new primary site and move each department gradually to new site. How should I plan for this?
    Thank you.

  5. concerning the migration and the intune subscription, you state: “remove Intune subscription and add it back”
    I suppose you must use the same .PEM file you used in the original environment.
    and for the record: this will not result in having to unenroll/re-enroll devices, right?

  6. Anoop need your help due to some issues we had to uninstall and install our primary, but the site code is same and it has been attached under our CAS.Clients have started reporting, but this primary was having 20+ DP’s. Now after installation none of DP’s are showing, how to proceed? Do we need to configure DP’s again, but what about the content library that was previously created? Or after configuring these DP’s will SCCM will know it was previously configured and start working?

    • Ankit, How did you install the primary site? Have you completed the restoration of primary site? I suppose, you need to have a good backup of the primary server to restore. Have you completed the supported way of SCCM restoration of primary server? If so the DPs should work without any issue. This is very complex scenario and I don’t think it will be easy to troubleshoot here. Rather I would recommend to raise a ticket with Microsoft.

  7. Hi Anoop,

    We are planning to Upgrade our SCCM to 1702 below are the challenges we see , need your inputs on how can we handle them,

    1. We are currently on SCCM 2012_1602 on Windows_Server_2008 and SQl 2008
    we are planning to build a new 2012 server and use site backup of old server to restore , and do the upgrade on it and if no issues found we will bring down the physical box and starting using virtual , will the Site backup allow us to configure a new SIte Code ?

  8. Hi Anoop,

    Tried the steps and i am getting error “Fail to create SQL Server Certificate”.
    Step up logs show,
    – SQL Server login failed for account corp\SMSAdmin
    – Cannot open the database CM_P01 requested by the login. Login failed.

    Environment details,
    – Moving Server OS 2012 R2 VM to OS 2012 R2 VM
    – ConfigMgr CB 1702 primary SA and SQL 2014 on same box
    – Using Default instance of SQL.
    – Using CM backup.

    Any suggestions.

    • PD, is your SQL server instance local on your SCCM server or are is the database on another server? If it is on the other server then you need to make the SCCM server computer account an admin on the SQL server and to generate a self signed cert from the SCCM server that you then install on the SQL broker.

    • Yes, corp\SMSAdmin account has sys admin.

      I tried following steps in the blog,
      http://henkhoogendoorn.blogspot.com/2013/01/fail-to-create-sql-server-certificate.html
      – But i could not add the local server account to SQL login. It only allows to add users & groups.
      – Also the error that shows up inside the log is, which is different from the above blog. In my case, the log file has following error.
      – SQL Server login failed for account corp\SMSAdmin
      – Cannot open the database CM_P01 requested by the login. Login failed

      • This is the way to create system account or machine account login in SQL for SCCM

        “Create SQL login for new computer object:
        a. Using SQL Script CREATE login [\$]from Windows

  9. Hello Anoop Nair, thank you for all the guides and videos, they are very helpful. Mr. Nair, do you have a guide or steps on how to move an existing primary site server (virtual) database to a new stand-alone SQL server (also virtual)?

    I need to expand an existing primary site server to a CAS. The existing primary site has SCCM, WSUS, IIS, DP, some other roles, and SQL database installed and configured on the same server.

    Here is what I am planning on going:
    • Move the primary site server database to stand-alone sql server
    • Build the CAS using the cd.latest
    • Point the CAS to the new SQL stand-alone server that has the database I moved from the primary
    • Build a new stand-alone sql server and install sql 2017 to serve as the database for the existing (old) primary site server that no longer has a database, since it was moved to served at the CAS database.
    • Point the existing primary (old) server to the its new stand-alone sql server and enable replication with the CAS sql server.

    At the end of the day, I am changing from 1 primary site server (all in one server) to a CAS, a Primary Server, and 2 stand-alone SQL servers.

    Will this work?…I am a bit concern on how to properly move the database to its own server and also spin a new database to replace the one I am taking away from the old primary site server.

    Thank you in advance for your time and support.

  10. Anoop or anyone that can answer this…Client install on non-trusted and workgroup machine. The environment has one primary and 3 additional site servers that has the MP, SUP, etc, roles installed.

    Question 1: SCCM Client install on workstations

    I have 300-400 machines that are on workgroups (no necessarily the same either) and I need to install the sccm client on them so my question is, do I need to move the sccm client files to each machine OR I place it in the site server they will be managed with and run script on each machine to perform the install?

    I am assuming I will need to include the network location where the files reside and the site server information in the script using a syntax such as this “network location\ccmsetup.exe /mp: SMSSITECODE=PPP SMSMP= DNSSUFFIX=” — now in case those machines can’t contact a DNS server, will I need to add the site server to the host file on each machine?

    Question 2: SCCM Client install on non-trusted domain

    I have about 500-700 devices that are part of different domains with-out trust with the domain the SCCM is on (non-trusted domains). I am thinking I will need to place the sccm client install files on a network location on each domain where devices can get to and create a GPO on each domain to push the client to each machine…if this is correct, where do I specify the site server information if I want to point half to one site server and the other half to another site server?…will I need to attach script such as the one above to point to the correct site server?

    Please note: I have experience pushing the SCCM client from within SCCM, have done GPO, and also manual installs but all in a trusted domain settings.

    Thank you in advance for your time and support.

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.