Learn Exchange the Guru way !!!


Hardcoding a domain controller in Exchange 2007

This is the powershell cmdlet to hardcode one or several domain controller for Exchange 2007.

Set-ExchangeServer -Identity “XXXXX” -StaticDomainControllers XXXXX -StaticGlobalCatalogs XXXXX -StaticExcludedDomainControllers XXXXX

By executing this, we are telling DS Access (AD Provider & AD Driver) were to look at. Providing multiple DC names by separating them with a comma will ensure availability if one of any DC’s are down.

To remove the Hardcoding use,

Set-ExchangeServer “ServerName” -StaticDomainControllers $Null -StaticGlobalCatalogs $Null -StaticExcludedDomainControllers $Null


6 Responses to “Hardcoding a domain controller in Exchange 2007”

  1. Louis Says:

    What is the best way to verify that this command is in place and the server(s) are now using the dc specified

  2. Ratish Sekhar Says:

    Filter for:
    Event Type: Information
    Event Source: MSExchange ADAccess
    Event Category: Topology
    Event ID: 2080

    Also,login to the Outlook client for a user residing on the hardcoded exchange server and do “Cntl + right click on the Outlook icon on the taskbar” and click “Connection Status” and look for “Directory Service”. That’s the DC exchange its pointing to.

    Please dont forget to recycle the services after hardcoding.

  3. Ratish Sekhar Says:

    Some light on the set of numbers in the event id:

  4. Louis Says:

    What about removing the hardcoding.

  5. Ratish Sekhar Says:

    My apologies for not adding the cmdlet to remove the hardcoding. I have included it now.
    Thanks Louis.

  6. reddy Says:

    Hi Louis,
    To check to see what domain controllers are in place after setting themup using the above command use the following

    Get-ExchangeServer -Status | select StaticDomainControllers,StaticGlobalCatalogs | fl


Leave a Reply




Do NOT follow this link or you will be banned from the site!