The impact of replacing the domain controller on the exchange server

I have Exchange servers 2007 distributed in several offices, the network is a single domain (windows server 2003) and there is a domain controller in each office, one of the domain controllers need to be replaced because of hardware issues.
I want to know what is the impact of replacing the domain controller on the exchange server, and what actions need to be done on the exchange server.
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.

Thomas QvidahlDeveloperCommented:
You must not install a DC on a server which already has Exchange Server 2007 installed, as this is not supported and will cause all kinds of issues due to the stricter security policy on the DC.
However, If the DC is installed first, then you can install Exchange 2007 on the same box. It's not really recommended practice even if it's supported.
Good luck,

Agree completely with Snowdon but if you are simply installing a new DC and decommisioning the old one then you should make sure the Exchange server is pointing to the new DC for DNS and check the setting in the EMC under > Organization Configuration or Server Configuration node> Modify Configuration Domain Controller context menu to launch the Configuration Domain Controller.

This allows you to specify a domain controller to be used for AD read and write for organization or server configuration
ModeyAuthor Commented:
Thanks Snowdon

I will not  install a DC on Exchange Server 2007 installed , I will installed  on a new server
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

It is important to know whether you're running separate domain controllers and Exchange servers. From the wording I assume you have separate servers.
If you are able to place a new domain controller before removing the old one, you should upgrade it to a global catalog (should be the case in every site).
Once you're happy with the new one, demote the old server from a DC to member server.

As long as you keep a global catalog in the forest (and preferably in the site), Exchange will not be troubled by adding and removing domain controllers.
What snowdon means, if you are running an Exchange server that is also a domain controller, then Exchange cannot use other domain controllers than itself. Removing the DC role from an Exchange server will seriously break that Exchange server.

You will not have these issues if the Exchange server has never been a DC.
Thomas QvidahlDeveloperCommented:
Rant32 has it nailed, however the recommendation is to have one GC in each site where there is an Exchange Server. Also, if your forest consists of a single domain, you should make every DC also a GC. I multi-domain forests placing GC's is a bit more involved.
Mass2612, if you blank the "Modify Configuration Domain Controller" setting, Exchange will select it's most appropriate DC. Only populate this setting if you're experiencing problems with the default, which is blank.

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
Snowden and Rant32 agreed but you still need to check the setting in case its been populated in the past.
Thomas QvidahlDeveloperCommented:
Rant32 - in regard to removing Exchange from a DC - I haven't tried that. I have, however tried making an Exchange 2007 Server a DC - it does break stuff. Not so much the DC, but Exchange will have some serious issues.

Easy enough mate.

Create the new DC and put in on the network with the one its replacing. promote it to DC and let it replicate. Getit setup with what you need and make sure it is in the correct 'site' in AD sites and services. Make sure it replicates from the correct servers and that it is a Global catalog server.

Make sure DNS, GC and AD replication is working on the new server before doing anything else.

Once youre happy it s working, demote the old DC and remove from the network. Once done you can just restart the exchange server on the site to pick up the new DC and GC listings. You can amend the settings without rebooting it but a restart is easier.
mass2612 - absolutely right w.r.t. the Configuration DC's, good catch.
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.