<div>
Actually I would stagger it like this, move one DC, then the Exchange server and then the final DC. &nbsp;I say this because, Exchange will need at least one Global Catalog server in order to function properly. &nbsp;Your active directory can survive having only one DC but your Exchange server will not work properly if there are no global catalog servers. &nbsp;Since only your DC's can be global catalogs, moving both of them removes the global catalog servers. &nbsp;So, make sure both DC's are global catalog servers then proceed with the staggered approach.<br />
<br />
-saige-
</div>


<div>
I'm not removing any of the DCs.. &nbsp;I'm making a copy and sending them to a different LAN. &nbsp;The original copy &nbsp;will stay on the old LAN during this time. &nbsp;Then the next weekend I'll copy the Exchange server. &nbsp;The Exchange server will always have two DC's.. &nbsp;It's just when it moves it will be a copy of them on the LAN that it will connect to for they'll be moved the previous weekend.
</div>


<div>
I can only see a problem arising if there is cross communication between the LAN's.<br />
<br />
-saige-
</div>


<div>
They are 100% isolated from each other.. &nbsp;I'll give it a shot.<br />
<br />
Thanks!
</div>


<div>
You can not move to a physically different copy of AD on different &quot;copied&quot; servers and expect things to work. <br />
Active directory is in a constant state of change and update. If you take your AD server copies one week and then your exchange servers a week later they will be out of sync and you will almost always end up with a broken system.
</div>


<div>
You should create a NEW ad server in the same domain at the remote location joined over a wan connection. This will allow you to move things across just by changing the IP address to that of the new site when it moves. <br />
You really can not do this with COPPIES.
</div>


<div>
Should I go ahead and just move the Exchange and DCs all at the same time then? &nbsp;My only other domain members are fileservers and a webserver.
</div>


<div>
Never do the Movements in a sigle shot or at the same time. &nbsp;As &nbsp;I understood you have 2 DC's and an Exchange server. Migrate one of the DC and make it a Global Catalog &nbsp;and then Exchange server then the &nbsp; other DC. Or you can move all the DC one by one and then Exchange server. This will be ideal rather than going i to a already known trouble.
</div>


<div>
Can't I just move the global address server first and not worry about changing roles? &nbsp;Since I'm doing a copy based on flat files do I need to power off the production DCs or can they stay online? &nbsp;I plan on powering off the Exchange server during this time to void it talking to anything for it will be copied last.
</div>


<div>
Please also keep in mind these networks are segregated
</div>


<div>
What about file servers and Web servers? &nbsp;What if I power down both DCs and Exchange. &nbsp; Copy <br />
those to the isolated network. Then only power on the DCs on the old network and let the file server and webserver use those until next weekend. &nbsp;Then the next weekend copy over file server and Web server. &nbsp;Is that still an issue?
</div>


<div>
I'm going to have a cable ran between each of my racks at the data center and migrate over the LAN. &nbsp;Thanks!
</div>


<div>
<div class="content wysiwyg-content">
I'm about to migrate a series of domain member servers. &nbsp;The three I'm most concerned about are the DC's and the Exchange server. &nbsp;Now, if one weekend 1 I moved 2 x DC's to a different network.. &nbsp;Then the next weekend I move the Exchange server will I have issues? &nbsp;The Exchange server will stay connected to a different instance of the 2 x DCs for the ones I plan to move first will be moved by themselves and their original copy if left on the LAN where the Exchange server is... &nbsp;I'm running Windows 2008 R2 on the DC's and Exchange 2010 Standard non-DAG.
</div>
</div>


I'm about to migrate a series of domain member servers.  The three I'm most concerned about are the DC's and the Exchange server.  Now, if one weekend 1 I moved 2 x DC's to a different network..  Then the next weekend I move the Exchange server will I have issues?  The Exchange server will stay connected to a different instance of the 2 x DCs for the ones I plan to move first will be moved by themselves and their original copy if left on the LAN where the Exchange server is...  I'm running Windows 2008 R2 on the DC's and Exchange 2010 Standard non-DAG.

Domain Controller / Exchange Migration over two weekends

Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.

Windows Server 2012

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

Exchange

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.