Demoted Domain Controller and now Exchange 2013 keeps getting topology errors!

[macdiesel1]

We recently migrated from Exchange 2007 to 2013. Everything was going good until we demoted an old domain controller. There is still a primary DC at this site. We keep getting topology errors on the Server 2012 Exchange server about not being able to contact DC. This happens about twice a day. A reboot of the server temporarily resolves it. Any thoughts? I have removed the name server DNS records referencing the old DC. That server is still in use, but no longer as a DC. We are on CU3 version of Exchange. Thanks for any help!

 

[ArizonaGeek]

Have you tried to rerun the Forrest Prep, Domain Prep, and Schema Prep? Did you update your domain controllers after your Exchange upgrade? What level are you running your domain, 2008 R2 or 2012?

Cheers
Rob

The answer is always "PEBKAC!

 

[ShackDaddy]

Try this:

Set-ExchangeServer -StaticDomainControllers “FQDN-of-NewDC” -StaticConfigDomainController “FQDN-of-NewDC" –StaticGlobalCatalogs “FQDN-of-NewDC”

Replace FQDN-of-NewDC with the full internal name of your new DC.

That will lock the server to only communicating with that server, hopefully without regard to any debris that may still exist in DNS or AD.

Dave Shackelford
ThirdTier.net

 

[macdiesel1]

I simple reboot of our other 3 domain controllers appears to have resolved the issue. Thanks for the replies.