SOLVED
Home

Change to internal namespace

%3CLINGO-SUB%20id%3D%22lingo-sub-3189%22%20slang%3D%22en-US%22%3EChange%20to%20internal%20namespace%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3189%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20All%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20part%20of%20migrating%20from%20Exchange%202010%20to%20Exchange%202016%2C%20our%20customer%20will%20also%20be%20moving%20to%20implementing%20split%20DNS%20(going%20from%20%22domain.local%22%20with%20a%20certificate%20issued%20by%20an%20internal%20CA%20to%20%22domain.com%22%20with%20a%20certificate%20issued%20by%20a%203rd%20party%20CA).%20Is%20anyone%20able%20to%20provide%20some%20advice%20on%20doing%20this%20in%20a%20way%20that%20minimises%20the%20impacts%20to%20clients%2C%20and%20also%20provide%20some%20information%20on%20what%20the%20impact%20to%20clients%20we%20may%20experience%20when%20performing%20this%20change.%3C%2FP%3E%3CP%3EThanks.%3C%2FP%3E%3CP%3EDan%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-3189%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3565%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20to%20internal%20namespace%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3565%22%20slang%3D%22en-US%22%3E%3CP%3EIn%20addition%20to%20what%20Thomas%20said%2C%20you%20can%20also%20check%20the%20Exchange%20Team%20blog%20about%20Namespace%20Planning%3A%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fblogs.technet.microsoft.com%2Fexchange%2F2015%2F10%2F06%2Fnamespace-planning-in-exchange-2016%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fblogs.technet.microsoft.com%2Fexchange%2F2015%2F10%2F06%2Fnamespace-planning-in-exchange-2016%2F%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CBR%20%2F%3ERegards%2C%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3228%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20to%20internal%20namespace%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3228%22%20slang%3D%22en-US%22%3E%3CP%3ENormally%20you%20would%20have%20to%20reduce%20the%20TTL%20of%20DNS%20resources%20records%20in%20question%20when%20changing%20IP-adresses%20or%20host%20names.%20But%20as%20you%20are%20changing%20the%20namespace%2C%20the%20clients%20would%20have%20to%20pickup%20the%20new%20urls%20provided%20by%20AutoDiscover.%20AutoDiscover%20caches%20the%20data%20requested%20for%20a%20single%20user.%20So%20a%20change%20in%20vDir%20url%20configuration%20will%20be%20picked%20up%20by%20clients%20immediately.%3C%2FP%3E%3CP%3EFor%20Exchange%202010%2C%20restart%20the%20AutoD%20application%20pool%3C%2FP%3E%3CP%3EFor%20Exchange%202013%2B%20you%20can%20use%20the%20follow%20two%20one-liners%20to%20restart%20the%20AutoD%20application%20and%20the%20service.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%3EGet-ExchangeServer%20%7C%20%3F%20%7B%20%24_.AdminDisplayVersion%20-like%20'*15.*'%7D%20%7C%20%25%20%7B%20Invoke-Command%20-ComputerName%20%24_.Name%20-ScriptBlock%20%7BRestart-WebAppPool%20MSExchangeAutodiscoverAppPool%20%7D%20%7D%0A%0AGet-ExchangeServer%20%7C%20%3F%20%7B%20%24_.AdminDisplayVersion%20-like%20'*15.*'%7D%20%7C%20%25%20%7B%20Invoke-Command%20-ComputerName%20%24_.Name%20-ScriptBlock%20%7BRestart-Service%20MSExchangeServiceHost%20%7D%20%7D%3C%2FPRE%3E%3CP%3EIn%20addtion%2C%20these%20changes%20should%20be%20implemented%20during%20off-hours.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECheers%2C%3C%2FP%3E%3CP%3EThomas%3C%2FP%3E%3C%2FLINGO-BODY%3E
Dan Snape
Contributor

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 to "domain.com" with a certificate issued by a 3rd party CA). Is anyone able to provide some advice on doing this in a way that minimises the impacts to clients, and also provide some information on what the impact to clients we may experience when performing this change.

Thanks.

Dan

2 Replies
Solution

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

In addition to what Thomas said, you can also check the Exchange Team blog about Namespace Planning: 

https://blogs.technet.microsoft.com/exchange/2015/10/06/namespace-planning-in-exchange-2016/

 


Regards,

Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
50 Replies
Extentions Synchronization
Deleted in Discussions on
3 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
32 Replies
Security Community Webinars
Valon_Kolica in Security, Privacy & Compliance on
15 Replies
Dev channel update to 80.0.355.1 is live
josh_bodner in Discussions on
67 Replies