Migration of critical infrastructure applications to a new domain
We just recently stood up a new domain for our company. We consolidated from 7 domains to 1, but prior to that we had just stood up some recent core infrastructure apps. My question is which of the below environments can i un-join from the old domain and join into the new domain and which environments will have to be built again. Below are the apps. we just stood up in an old domain and need to be migrated: Exchange 2013 Systems Center Service Manager 2012 Systems Center Config. Manager 2012 SQL Ent. 2012 Clustered SharePoint 2012 Clustered
December 18th, 2012 5:15pm

Hi Exchange 2013 will definitely need to be build again. Not sure about the rest but I think this might apply for all of them.. Cheers, Steve
Free Windows Admin Tool Kit Click here and download it now
December 18th, 2012 5:18pm

Thanks Steve. I feared so.
December 18th, 2012 5:46pm

Pretty much all of that will have to be rebuilt in the new domain, since they all rely heavily on SSIDs and GUIDs of the domain they are installed in. Exchange particularly. That said, you should be able to export/back up your Sharepoint sites in your old forest and restore them in the new one without too much difficulty, but you may have to install a Sharepoint Server that meets the new forest's installation in the old forest and migrate to it, then upgrade the data in it before migrating to the new forest. SQL should also allow you to mount whatever databases you have in the new forest as well, but the applications that use those databases could have issues depending on how much data they pull from AD. System Center is also heavily AD integrated, so you wouldn't be able to just move those servers over, either.
Free Windows Admin Tool Kit Click here and download it now
December 18th, 2012 11:57pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics