CurrentConfDomainController change

Article
2017-06-15

Question

_{Thursday, June 15, 2017 9:14 PM}

Hello,

I am looking to decommission an old DC Server. But in my Exchange 2016 server when I look at the GC settings, this server is still showing.

If you see below, it would be the xyz.com.

CurrentDomainControllers        : {abc.com,xyz.com}
CurrentGlobalCatalogs           : {abc.com,xyz.com}
CurrentConfigDomainController   : xyz.com

Since I am looking to decommission the xyz.com server, how can I remove it from the Exchange CurrentConfigDomainController setting, and what happens after I do remove it ? Does it take another DC automatically or I have to enter it manually?

Anser Leon

All replies (2)

_{Saturday, June 17, 2017 3:20 AM ✅Answered}

Hi,

Do you complete the DC transition, include FSMO role, DNS, also promote new DC as GC?

By default without any configuration, Exchange server use the Microsoft Exchange AD Topology service to load balances its Global Catalog and Domain Controller in the same Active Directory site.

Therefore, we can restart the Microsoft Exchange AD Topology service then check the DC and GC settings by "Get-ExchangeServer -Status | Identity,Current*,Static*".

If the new GC (and DC) place the current GC (and DC) list, it's safe to decommission old DC.
Tips: we can manually specify GC or DC by Set-ExchangeServer with Static* parameter, for example: StaticDomainControllers.

Best Regards,

Allen Wang

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Friday, June 16, 2017 2:03 PM}

Hi,

We are currently looking into this issue and will give you an update as soon as possible.
Thank you for your understanding and support.