[SCCM/MECM] Migrate endpoints from one site to another

[Garacesh]

Calling the old SCCM and the new MECM, just for clarity.

 

I've gotten to the point now where the MECM box has all the software, drivers, task sequences etc set up that SCCM had, and I've got it listing windows updates with ADR's configured.

How do I tell my endpoints to make the switch?

 

At first I thought, easy, just remove all the devices from the SCCM server, disable device discovery, then deploy the Configuration Manager Client Package package from MECM to the endpoints. MECM has device discovery running just fine and can see all the devices, after all.

Except, deploy isn't an option.

It is for the Piloting Package, and the USMT, but not for the default one..

 

I've found some chatter about creating a script that essentially says "join this site code" (e.g. here and

) and deploying that from the old server. Is that considered the best way? Edited March 22, 2021 by Garacesh

[clareq]

There's a GPO to do this - you can add it from :\Program Files\Microsoft Configuration Manager\tools\ConfigMgrADMTemplates.

[ranj]

I have used the GPO method and its really easy, just add the required template, update the GPO to point to new site code. Scope your machines to that GPO and after a gpupdate it should move the client to new site.

[MartinByard]

When we moved from our old environment to our new one, we created a package in the old one with the source files pointing to the CCM client folder (this is found at \\\SMS_\Client) and the program it ran was a custom powershell script that was:

 

Copy-Item -Path .\New_Client -Destination C:\Windows\Temp\New_Client -Recurse -Force

Start-Process C:\Windows\Temp\New_Client\ccmsetup.exe -ArgumentList "/MP:[b][/b] /skipprereq:Silverlight.exe /forceinstall /source:C:\Windows\Temp\New_Client /usepkicert SMSSITECODE=[b][/b] SMSCACHESIZE=25000" -Wait

 

Obviously this command line can be tailored to your needs (you might not want to skip silverlight, or have PKI certs for HTTPS communications - or need a 25Gb cache).

 

Once this has run on a client in the old environment - it pulls down and installs the client from the new environment and populates itself.