Forum Discussion

Dan_Snape's avatar
Dan_Snape
Bronze Contributor
Jul 25, 2016
Solved

Change to internal namespace

Hi All,   As part of migrating from Exchange 2010 to Exchange 2016, our customer will also be moving to implementing split DNS (going from "domain.local" with a certificate issued by an internal CA...
Exchange Server
  • ThomasStensitzki-MVP's avatar
    ThomasStensitzki-MVP
    Jul 25, 2016

    Normally you would have to reduce the TTL of DNS resources records in question when changing IP-adresses or host names. But as you are changing the namespace, the clients would have to pickup the new urls provided by AutoDiscover. AutoDiscover caches the data requested for a single user. So a change in vDir url configuration will be picked up by clients immediately.

    For Exchange 2010, restart the AutoD application pool

    For Exchange 2013+ you can use the follow two one-liners to restart the AutoD application and the service.

     

    Get-ExchangeServer | ? { $_.AdminDisplayVersion -like '*15.*'} | % { Invoke-Command -ComputerName $_.Name -ScriptBlock {Restart-WebAppPool MSExchangeAutodiscoverAppPool } }

Get-ExchangeServer | ? { $_.AdminDisplayVersion -like '*15.*'} | % { Invoke-Command -ComputerName $_.Name -ScriptBlock {Restart-Service MSExchangeServiceHost } }

    In addtion, these changes should be implemented during off-hours.

     

    Cheers,

    Thomas

Resources