This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(246.4, 19%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERM%3C/text%3E%3C/svg%3E)
Hello, We're currently running Endpoint Config Manager 2006, 5.0.9012.1000 with one Primary Site Server. After years of talking about it, we've finally decided to change our domain name. I know it's not supported but I was hoping for some guidance on what would be the best way to go about this with System Center installed. (Please don't say don't to it....I lost that fight already..LOL)
What would be the best thing to do......Just completely rebuild it or can I just uninstall the site on the current server, have it join the new domain and reinstall the site? If it's just build a new site from scratch....is it possible to migrate anything off the old server into the new server? (We have a few custom deployment task sequences and UDI options based on specific devices like thin clients, POS systems and standard machines). Any help that anyone can give or point me in the right direction will be greatly appreciated.
Thanks again, Michael
A migration to a new site (using the built-in migration toolset) is the only path here that is supported and will work. This will migrate most things, but not all so be prepared to either manually recreate some things or script their creation. This could be a good opportunity to adopt a DevOps approach to configuring the new site.
Things that don't migrate include client settings and RBA configuration although there are others. Basically, anything that didn't exist in ConfigMgr 2007 can't be migrated as the migration toolset was initially built for migrating off of 2007.
Ok so definitely just build a new site and migrate what I can over from the old site to the new. Once the domain name change occurs, the original site won't work anymore from what I read. Will that cause any issues with using the migration tool?
Oh wait, I read that as you are building a new domain and migrating to it but that's not correct, you are actually renaming the domain in-place.
In that case, the migration tool will not work either. You will need to export everything out manually from the existing site and then reimport into the newly built site (that you can build until after the rename). You can script a lot of this, but there are no pre-built scripts for this to my knowledge -- at least not supplied by the product. You may be able to reach out to a consulting org or MCS for help on this and they may have scripts to help with this.
Let me ask this......would it be possible to just uninstall all SCCM services on the server.....join the server to the new domain and reinstall all SCCM services? Or would that just be "messy"?
Would you know in any event, can I use the same site code or should that change also?
You can do this but no configuration can be preserved -- it would be a new site. You can use the same site code and it should work to my knowledge as long as you are publishing site information to AD (and the clients are AD joined as well of course). That could lead to confusion and ambiguity though as there'd be no direct way to distinguish between the old site and new site.
Reason why renaming is not supported is, that you have SQL and registry with a lot of keys and places where PS's name is mentioned. Also SQL relies on registry, so it might work just to search entire registry and rename values of keys after the real rename is done. But be ready for a lot of headache later :)