Decommissioning old domain controller. Anything to double check?

I currently have 4 domain controllers in one site. I am also running Exchange 2010. It is NOT installed on any of the domain controllers.

Domain Controllers:
DC1 - Win 2003 - Global Catalog - DNS server - Holds FSMO roles
DC2 - Win 2003 - DNS server
DC4 - Win 2008 R2 - Global Catalog - DNS server
DC2008 - WIn 2008 R2 - Global Catalog - DNS server

I want to demote DC2 and then decommission it. If there anything in particular I should double check before running DCPromo to demote it?
donohoe1Asked:
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.

amac81Commented:
I would just ensure that within DNS that there are no zones which are not AD Integrated.  Otherwise they wouldn't replicate around to the other DC's.  It is unlikely since they're all in the same site, but it is legacy.
0
Seth SimmonsSr. Systems AdministratorCommented:
also change any systems with static ip addresses and andy dhcp scopes that have dc2 as a defined dns server for clients
0
donohoe1Author Commented:
Already done. We've also waiting well last the DHCP lease period to ensure all clients have the new (non-DC2) settings.

Sorry I forgot to mention that.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

amac81Commented:
Then sounds like you're ready for dcpromo.
0
donohoe1Author Commented:
I'm mostly just worried about it affecting our Exchange 2010 environment in some way. I've heard a couple horror stories about demoting a DC taking down Exchange 2010.
0
Suliman Abu KharroubIT Consultant Commented:
Just make sure that all FSMO are hosted in DC01:
Run: netdom query fsmo

Then check the domain using dcdiag if there is any issue to be solved before the demotion.
0
donohoe1Author Commented:
We're good on both counts.
0
Suliman Abu KharroubIT Consultant Commented:
Then you should be safe to decommission... make sure that exchange servers are not using it as a DNS server.... remove its ip from exchange NICs config.
0

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
donohoe1Author Commented:
Done. I also checked each Exchange server to make sure its preferred DC wasn't DC2.
0
amac81Commented:
You could power off DC2 and see if Exchange tosses any errors.  Wait an hour or two or until tomorrow and then power it on then run the DCpromo.
0
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
Active Directory

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.