Event banner
Event details
I have a Config Manager site installed on a physical server that is beginning to report hardware issues so I am working on migrating to a new Config Manager site in a VM. The old site is tenant attached, co-managed, and has a CMG. It has been suggested in various forums to deploy a script that will simply change the site code to the new site. I've done some preliminary testing and this seems to work, though various client logs such as policyagent show warnings concerning policies from the old site which I'd expect. My question is, is this a recommended method? Are there any "gotchas" in doing this? The new site isn't configured for the cloud yet (no tenant attach, co-mgmt, or CMG) and so I don't know if simply changing the site code on an endpoint will cause issues with it communicating with those components or other things that I haven't thought of.
Jason_Sandys
Microsoft
MicrosoftHi Michael,
The best path here is to do a "site" backup and restore. This will allow you to restore the site, as is, including all configuration to a new "server" (virtual or physical is irrelevant). This is completely transparent to the clients and thus requires no client-side changes (including site code) whatsoever. Here's a nice post that will help you understand what's involved (as this is essentially a disaster recovery scenario): https://techcommunity.microsoft.com/t5/core-infrastructure-and-security/change-configuration-manager-site-server-os-disaster-recovery/ba-p/3765562