Event banner
Event details
MECM question - we are migrating our current MECM infrastructure from Azure back to on-prem, predominately due to cost reasons. We currently have (and will have) one Primary Site Server (Green DMZ), with Management Points in Amber and Red DMZ's with SQL replication setup so we adhere to certain security co-co's. We are planning on doing a SQL export/import (yet to work out how that works between Azure and on-prem), can we change the Site Code afterwards, or would it be best practise to stick with the original Site Code?
We also have co-managed configured with Intune so will also be setting that up from the new infrastructure. Not sure it has any bearing on this, but thought it was worth mentioning. Thanks
- Jason_Sandys
Microsoft
Hi Nick Mitchell, You cannot change the Site Code of an existing ConfigMgr site. What's the motivation for wanting to as this would, if you actually could (in a supported way) orphan all of the clients. > We also have co-managed configured with Intune so will also be setting that up from the new infrastructure. If you're simply backing up the database and restoring it using the supported backup and restore path, then there's nothing to set up again as you are restoring the existing site including all of its configuration. Have you considered simply transitioning to full Intune management instead? This is our ultimate goal for all orgs (where possible). Is there anything stopping you from doing this?Not much motivation other than we've changed our Company name so would be a good time to go with a new site code for the new infrastructure. That and it's playing havoc with my OCD 🙂 - we'll stick with the current one. We'll publish the new MP's into AD System Management and get clients to rotate with an installation package from existing MECM with command line pointing to new MP's.....either than or just discovery the domain joined ones and client deploy from within new Console, haven't decided yet. We have considering transitioning to full Intune management as we realise this is the direction of travel, however we're not quite there yet. Remote Support for one is still done through Intune, don't want to pay the additional cost of use remote support through Intune integration, we pay enough for Intune as it it 🙂 MECM is still utilised to patch our server estate (approx. 500), however this is separate to the endpoint device discussion
