Thursday , July 18 2019

Hard coding a Domain Controller in Exchange 2010

Unlike the previous versions, Hard coding a domain controller became as simple for trouble-shooters

When to Hard Code a Domain Controller in Exchange 2010 ?

If you feel Exchange should not see some domain controllers which is not in a good shape

or

Exchange becomes too sluggish when its trying to contact the Domain Controller across site

Some more Scenarios…

For Temporarily , To Troubleshoot and isolate the issue, We can hard code a domain controller

Note: Hard coding a Domain Controller to Exchange 2010 , Gets you to a State of Single Point of Failure

Like, When The hard coded domain Controller Reboots Exchange 2010 will stop working

So Try to Give Multiple DC’s and GC’s while hard coding and It has to be used for temporary purpose as its a single point of failure

To Verify its already Hard coded or not

Run

Get-ExchangeServer “Server Name” –Status | fl Identity,Static*

image

To Hardcode a Domain Controller in Exchange 2010

Run

Set-ExchangeServer -StaticDomainControllers "DC FQDN" -StaticConfigDomainController "DC FQDN" –StaticGlobalCatalogs "GC FQDN"

Also You can use –StaticExcludedDomainControllers

The StaticExcludedDomainControllers parameter specifies whether to exclude a list of domain controllers to be used by the server.

Reference Link:

http://technet.microsoft.com/en-us/library/bb123716.aspx

To Verify the hardcode

Run

Get-ExchangeServer “Server Name” –Status | fl Identity,Static*

image

To Remove the hardcode

Run

Set-ExchangeServer –StaticDomainControllers $null –StaticConfigDomainController $null –StaticGlobalCatalogs $null

image

 

About Satheshwaran Manoharan

Satheshwaran Manoharan is an Microsoft Office Server and Services MVP , Publisher of Azure365pro.com. Specialized in Office365 / Microsoft Exchange / Virtualization , Sathesh is an Messaging Expert supporting/Designing/Deploying many medium size businesses to large enterprises when it comes to Corporate messaging and Virtualization Infrastructure

Check Also

Azure Virtual Network (VNet) Peering UAE to Central US

VNET Peering connects networks seamlessly within and across regions. Local and Global Peering pricing differs ...

3 comments

  1. simple and to the point explanation

  2. Hi Satheswaran,

    I got an issue with MS Exchange AD Topology service not starting once the mailbox server restarted. I did hardcoding site by regedit. then Nltest /getdssite finds the correct site. But still ADtopology service not starting. Before another mailbox server had shown issue with IS storre service & hardcoding site helped. But this time no use. Any suggestions pls..

Leave a Reply

Your email address will not be published.