Thread by @panusaukko

Just finished a project where an old physical Windows Server 2012 R2/SQL Server 2014 #MEMCM site server was replaced with a virtual Windows Server 2019/SQL Server 2019 server.

Site server also had MP/DP roles, but no SSRS/SUP.

Here are some points I learned!

1/6

Site server replacement is basically a ConfigMgr site recovery on the new hw.
Docs has nice info about the process.
Notice that you can change the #MEMCM installation directory if needed.
docs.microsoft.com/en-us/mem/conf…
2/6

It takes a long time to copy #MEMCM content library with millions of 1k files to the new server…
Remember: ReFS is not supported on content library partition!

3/6

When you rename your new server with the old name, grant the new computer account the right permissions to AD’s System\System Management container and give admin permissions to remote site servers.
Same old name, but new SID!
4/6

You need to re-type all the passwords that you have in #MEMCM: e.g. client installation accounts, NAA if used...
And all passwords in your task sequences: domain join account, local admin passwords...
If you have a lot of TSes, this might take some time.
5/6

If using PXE on your site server:
- Need to re-enter PXE password
- Check your switch/router configs. Even though the IP might remain the same, there might be port specific configurations
- Remember to re-add RamDiskTFTPWindowSize/ RamDiskTFTPBlockSize registry values
6/6