SOLVED Migrate SCCM from Physical Server to Virtual Machine

[rkg]

Hi Pra, i´m new with MECM, and we want to migrate current server that has the latest version 2107, from a physical server to a virtual server, current server was like abandoned for previous system administrators, so we are new with the client and want to update the server to 2019, install SQL 2019 (Current server is 2012 R2, with SQL 2012), and the MECM isn´t wotking properly, some errors with management point, etc, etc.

The client basically just wants to get Software and Hardware inventory from computers, no WSUS, no WDS, no Package deployment. they have anothers tools for that.

There is any Step by Step to migrate the database, the MECM, to a new server?

I appreciate any help, your site has been very helpful to my this last week.

Regards
Roger

 

[Prajwal Desai]

I am really not sure about the steps for migrating ConfigMgr running on physical server to Virtual machine.
Here is what I suggest.
What you can do is install create a VM > Install Windows Server > Install new instance of Configuration Manager on Virtual Machine with a different site code. Once you do that, on your old ConfigMgr server go to Administration\Overview\Migration\Source Hierarchy. Specify the source hierarchy details (new ConfigMgr server details) and connect to the server. Create a migration job and specify what you want to migrate.

 

[Garth]

Hi Pra, i´m new with MECM, and we want to migrate current server that has the latest version 2107, from a physical server to a virtual server, current server was like abandoned for previous system administrators, so we are new with the client and want to update the server to 2019, install SQL 2019 (Current server is 2012 R2, with SQL 2012), and the MECM isn´t wotking properly, some errors with management point, etc, etc.

The client basically just wants to get Software and Hardware inventory from computers, no WSUS, no WDS, no Package deployment. they have anothers tools for that.

There is any Step by Step to migrate the database, the MECM, to a new server?

I appreciate any help, your site has been very helpful to my this last week.

Regards
Roger

If it was abandoned, why not start fresh? aka why bring the old junk with you?

 

[rkg]

I am really not sure about the steps for migrating ConfigMgr running on physical server to Virtual machine.
Here is what I suggest.
What you can do is install create a VM > Install Windows Server > Install new instance of Configuration Manager on Virtual Machine with a different site code. Once you do that, on your old ConfigMgr server go to Administration\Overview\Migration\Source Hierarchy. Specify the source hierarchy details (new ConfigMgr server details) and connect to the server. Create a migration job and specify what you want to migrate.

Thanks, we are seeing different approachs, i will bring this to the table

 

[rkg]

If it was abandoned, why not start fresh? aka why bring the old junk with you?

Well, mostly to keep the Device collections groups, there are like 30 Device collections with different filters, is a big company with like 15 branch office, so i dont want to recreate the device collections, we are trying to simplify the post-migration tasks

 

[rkg]

I am really not sure about the steps for migrating ConfigMgr running on physical server to Virtual machine.
Here is what I suggest.
What you can do is install create a VM > Install Windows Server > Install new instance of Configuration Manager on Virtual Machine with a different site code. Once you do that, on your old ConfigMgr server go to Administration\Overview\Migration\Source Hierarchy. Specify the source hierarchy details (new ConfigMgr server details) and connect to the server. Create a migration job and specify what you want to migrate.

Doing that, the clients will report to the new server? can i re-deploy clients from the new server and clients will report to the new server ?

 

[Garth]

So hang on you state the CM isn't working properly, if this is the case, you should NOT move it until you fix that problem first. Once that is fixed, then move it. Otherwise you are bring the problem to the new server.
IMO if things are not working, it is easy to start over then to fix and move the server.

 

[rkg]

So hang on you state the CM isn't working properly, if this is the case, you should NOT move it until you fix that problem first. Once that is fixed, then move it. Otherwise you are bring the problem to the new server.
IMO if things are not working, it is easy to start over then to fix and move the server.

Thanks Garth and Prajwal, at the end we decided start fresh with the new server with a new site code, old server was uninstalled and decommisioned, i figure out that boundaries are created automatically, i configure discovered methods following Prajwal post about it, for now looks good, i will push client installation today, Thanks both.