Migrate SCCM CB2010 and SQL 2012 to new 2019 servers

Chong 846

Hi all,

We have two Win2012 servers which installed SCCM CB2010 and SQL 2012 Server. Now we planning to migrate them to Win2019 server and SQL 2019 Server
Seems we can use backup and recovery to migrate the SCCM to new server.

For the SQL server, do we need to migrate the existing SQL server first? Or just backup the database and restore to new SQL 2019 Server? How about the reporting services

Thanks

Chong

6 answers

Fiona Yan-MSFT 2,311 Reputation points

2021-01-06T08:30:17.697+00:00
@Chong

Thank you for posting in Microsoft Q&A forum.

There are many methods to perform the action, it's recommended that using in-place SQL upgrades and Site backup and restore.

The mainly steps should be like this:

In-place upgrade to SQL 2019 on the old server.

Migrate SQL to new server (2019).

Backup/restore SCCM primary site to the new OS server (same name for the server).

Move the database and SCCM roles.

SQL and SCCM same box (Server 2019 and SQL 2019).

The following articles including the site backup and restore:
backup-and-recovery the site
recover the sites

Also, we could refer to these two excellent blogs:
https://home.memftw.com/configmgr-site-backup-restore/
https://www.sysinfotools.com/blog/migrate-sql-server-database-from-one-server-to-another/
Note: This is non-official Microsoft article just for your reference.

Have a nice day!

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Please sign in to rate this answer.
TomDee 1 Reputation point

2021-08-17T20:25:31.29+00:00

Microsoft says SQL 2019 is not supported on Microsoft Server 2012R2 so can you still do a in-place upgrade even though the OS is not supported?

https://learn.microsoft.com/en-us/troubleshoot/sql/general/sql-server-windows-8-later-versions#:~:text=SQL%20Server%202019%20is%20not,or%20Windows%20Server%202012%20R2.&text=You%20can%20install%20the%20release,SQL%20Server%202014%20main%20page.&text=SQL%20Server%202016-,You%20must%20apply%20SQL%20Server%202016,2%20or%20a%20later%20update.
Sign in to comment
Chong 846 Reputation points

2021-01-06T08:53:59.937+00:00

Hi @Fiona Yan-MSFT ,

Thanks for the information.

For the "Backup/restore SCCM primary site to the new OS server (same name for the server)", it should use the same server name?
So we need to cleanup the existing SCCM server and disjoint it from the domain, then setup a new SCCM server?

This should required very long downtime. Any method can have shorter download time for the server migration?

Thanks

Chong
Please sign in to rate this answer.
Fiona Yan-MSFT 2,311 Reputation points

2021-01-06T10:12:35.053+00:00

@Chong

Thank you for the quickly reply.

The Backup/restore is the easier way I would recommend otherwise you will have a lot of work to do. The backup/restore method need to use same name for the server. We could shutdown the existing SCCM server instead of cleaning and disjoin from the domain.

Have a good day!

Jason Sandys 31,151 Reputation points Microsoft Employee

2021-01-06T18:00:03.567+00:00

So we need to cleanup the existing SCCM server and disjoint it from the domain

No. My recommendation is shut down and disable the SQL and ConfigMgr services and simply rename the server. That way, it's still available on the network for anything you forget and also easy to fallback to if necessary.
Sign in to comment
Chong 846 Reputation points

2021-01-07T03:21:48.827+00:00
Sorry that I am new on SCCM so may have many thing unclear

As we have existing SQL 2019 server for other services already, if we want to recovery the SCCM to this SQL, the step will be:

In-place upgrade to SQL 2019 on the old SCCM SQL 2012 server.

Migrate the SCCM DB to new SQL 2019 server.

Backup/restore SCCM primary site to the new OS server (same name for the server).

Move the database and SCCM roles. <<< Can explain more about this? The SQL and SCCM still to configure after restore to new server?

Thanks

Chong
Please sign in to rate this answer.
Fiona Yan-MSFT 2,311 Reputation points

2021-01-07T06:03:04.42+00:00

@Chong

Thank you for the kindly reply.

The step 4 means we need to check if we have moved the database and SCCM roles successfully. The logical steps like this:

In-place upgrade to SQL 2019 on the old SQL 2012 server.

Migrate SQL DB to new server (2019).

Backup/restore SCCM primary site to the new OS server (same name for the server).

SQL and SCCM same box (Server 2019 and SQL 2019).

Thanks a lot.

Fiona Yan-MSFT 2,311 Reputation points

2021-01-13T02:56:08.823+00:00

@Chong

May we know the current status of the question? If there is any other assistance we can provide, please feel free to let us know, we will do our best to help you.
Sign in to comment
Chong 846 Reputation points

2021-01-14T03:18:49.387+00:00

Hi @Fiona Yan-MSFT

I tried to restore the SCCM to the new server (Just restore the site server, SQL not restore as we will use the existing SQL first). The setup is completed but some components still "installing"

And the SCCM site cannot be connected

Any idea?

Thanks

Chong
Please sign in to rate this answer.
Fiona Yan-MSFT 2,311 Reputation points

2021-01-14T08:07:05.817+00:00

@Chong

Thank you for the update.

For troubleshooting the process of the installation, please check the ConfigMgrSetup.log located on C drive.

We could also click view log to see what happened during the process.

May we know if we could click the next button? Have we wait some time after installation and then open the CM console?(Because some components are still installing)

For "the SCCM site cannot be connected", please check the SmsAdminUI.log(C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\AdminUILog) Does the user have the correct permissions to connect to the site server?
Sign in to comment
Chong 846 Reputation points

2021-01-14T09:29:37.197+00:00

Hi @Fiona Yan-MSFT

I see the elapsed time stopped and wait around 1 hours but those components still show "installing" so I click next to completed the wizard.

From the SmsAdminUI.log, it have some RPC server error. I tried to fixed the problem as below:

https://social.technet.microsoft.com/Forums/en-US/6c55a1c8-64c7-4720-bc8d-a4ee25856b1e/sccm-console-cannot-connect-to-database?forum=ConfigMgrDeployment
http://schadda.blogspot.com/2012/08/how-to-fix-issues-related-with_7.html

But it still have many "ProviderLoadFailure" error and don't have more information to me
56467-smsadminui.log

Thanks

Chong
Please sign in to rate this answer.
Fiona Yan-MSFT 2,311 Reputation points

2021-01-15T09:59:20.627+00:00

@Chong

The core setup is completed does not really means this process was finished. We need to wait for more than one hour. We could open the ConfigMgrSetup.log to see the details of the installation process, we may see in the log with "exit" also with many "=", so we may need to be patient.

Thanks a lot.

Chong 846 Reputation points

2021-01-18T05:05:11.823+00:00

@Fiona Yan-MSFT

I setup another server to restore the SCCM. Same as last time, the SCCM console in new server cannot be access with same error
During the setup, the Elapsed time increase and the Next button is dim before the setup complete. When the setup "complete", it let me click Next and the installation log show completed, but some components still show installing...

Fiona Yan-MSFT 2,311 Reputation points

2021-01-18T09:52:19.687+00:00

@Chong

It seems that the WMI provider attempts to access to the site database and after several times it failed. Have we checked the Smsprov.log on our server side already?

Have a nice day!

Chong 846 Reputation points

2021-01-18T10:40:31.16+00:00

@Fiona Yan-MSFT

You are right. From the log, seems the console cannot open because it cannot login the SQL server (error: Failed login for user domain\sccmserver$)

But why it cannot login? The account is added in SQL already. I also tried to remove and add it again but still have the same error.

However, when I rename the original SCCM server back, the SCCM console can be access. So the account is added in SQL server correctly.

Thanks

Fiona Yan-MSFT 2,311 Reputation points

2021-01-19T09:00:08.34+00:00

@Chong

Thank you for the update and I'm glad the problem is solved now. As mentioned above, the server should use the same Host name and fully qualified domain name (FQDN) of the original site server.

Here is a recovery article for you to refer to:
recover-sites#reinstall-the-site-server

Have a good day!

Chong 846 Reputation points

2021-01-19T09:10:26.767+00:00

@Fiona Yan-MSFT

I think you misunderstand my meanings. My problem didn't solved. The recovery server still not work. I just rename the old SCCM server back and the services resume.

My step is:

Backup and rename old server from SCCM01 to SCCM01_old

Rename the new server to the SCCM01

Restore the backup to new server

New server not work, it have SQL login error

Rename the new server to SCCM01_new

Rename the old server SCCM01_old back to SCCM01

Services resume

Fiona Yan-MSFT 2,311 Reputation points

2021-01-20T11:46:12.993+00:00

@Chong

Thank you for the detailed reply.

If we want to use this method, please try the following steps:

Back up on the old server.

The old server join in the Workgroup (delete this old server name from the domain) or disconnect from the network.

The new server use the old server's host name.

Restore on this new server.

Have a good day!

Chong 846 Reputation points

2021-01-21T08:07:06.167+00:00

@Fiona Yan-MSFT

I follow your step to remove the old SCCM from the domain before restore on new server but it have the same problem.

And I found some of the services are missing in restore server
Sign in to comment