Domain Controller / Exchange Migration over two weekends

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.
gopher_49Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

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

-saige-
gopher_49Author Commented:
I'm not removing any of the DCs..  I'm making a copy and sending them to a different LAN.  The original copy  will stay on the old LAN during this time.  Then the next weekend I'll copy the Exchange server.  The Exchange server will always have two DC's..  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.
it_saigeDeveloperCommented:
I can only see a problem arising if there is cross communication between the LAN's.

-saige-
Your Guide to Achieving IT Business Success

The IT Service Excellence Tool Kit has best practices to keep your clients happy and business booming. Inside, you’ll find everything you need to increase client satisfaction and retention, become more competitive, and increase your overall success.

gopher_49Author Commented:
They are 100% isolated from each other..  I'll give it a shot.

Thanks!
Neil RussellTechnical Development LeadCommented:
You can not move to a physically different copy of AD on different "copied" servers and expect things to work.
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.
Neil RussellTechnical Development LeadCommented:
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.
You really can not do this with COPPIES.
gopher_49Author Commented:
Should I go ahead and just move the Exchange and DCs all at the same time then?  My only other domain members are fileservers and a webserver.
Rahul RamachandranCommented:
Never do the Movements in a sigle shot or at the same time.  As  I understood you have 2 DC's and an Exchange server. Migrate one of the DC and make it a Global Catalog  and then Exchange server then the   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.
gopher_49Author Commented:
Can't I just move the global address server first and not worry about changing roles?  Since I'm doing a copy based on flat files do I need to power off the production DCs or can they stay online?  I plan on powering off the Exchange server during this time to void it talking to anything for it will be copied last.
gopher_49Author Commented:
Please also keep in mind these networks are segregated
Neil RussellTechnical Development LeadCommented:
Segregated or not once you start moving to the new site that has no connectivity to the old then you need all servers powered off.
You can not "copy" an ad server that has anything attached to it and leave the old one running with connections and THEN move those other servers/workstations to the OLD copy at a later point in time. You will have big problems x

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
gopher_49Author Commented:
What about file servers and Web servers?  What if I power down both DCs and Exchange.   Copy
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.  Then the next weekend copy over file server and Web server.  Is that still an issue?
gopher_49Author Commented:
I'm going to have a cable ran between each of my racks at the data center and migrate over the LAN.  Thanks!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.