Changing Exchange 2013 and Windows 2012R2 Domain controller's AD Site.

So I have an Exchange 2013 box and DC that I would like to change back to my default site. Is there anything I need to do before doing this? Right now I have an Exchange 2013 box with Mbx and CAS roles in the first site. I am moving the second Exchange back to the first default site so I can have some HA with my CAS boxes (as budget allows). There are no DAGs set up between the two yet. Please advise.

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

There should be no issues at all.  Once the IP's are updated and DNS reflects those IP changes you should be able to verify replication of AD is working.  Exchange shouldn't have any issues as long as AD replication is working.
internetworksAuthor Commented:
Which IP changes are you speaking of? When I add the subnet back into the First original site? I am not changing any IPs on the devices themselves.
I guess if you are keeping the same address range and just setting up internal routing at the one site between the two previously site separated subnets you shouldn't need to do much other than associate the subnet to the main site in AD sites and services and make sure that gets replicated around.
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Will SzymkowskiSenior Solution ArchitectCommented:
For this to happen correctly, all you need to do is this following...
- Stop all of the Exchange Services (to stop mail flow)
- Set all of the Microsoft Exchange services to disabled
- Change the IP address to the same scheme as the AD Site you want to move it to
- Power down the Exchange Server
- If you have to physically move the server do so
- Power on the Exchange server with the new IP (that matches the AD Site it is in)
- Login to the Exchange server
- Open the command prompt type set logonserver press enter
- This should show you which DC you are authenticating to (it should be the DC in the AD site you moved it to)
- Open Services.msc on the Exchange server, Set all of the Exchange services to Automatic
- Reboot the Exchange server and verify that services have started correctly
- Check your database/logs etc to ensure there are no errors

Those are the steps I would follow to ensure that nothing is missed.


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
Justin YeungSenior Systems EngineerCommented:
all you have to do is the change the IP subnet bind to the target site.

confirm replication

restart Exchange AD topology service on the target exchange server.
internetworksAuthor Commented:
Thanks for the great detail!
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

From novice to tech pro — start learning today.