Forum Discussion
Bound to unbound namespace
We currently have exchange 2010 spread across 2 datacenters using a bound namespace. Users in the west use the mail-west.domain.com namespace while the users in the east use mail-east.domain.com. We...
VickVega Thank you for your feedback. I have gone through the deployment assistant, but it is not very clear on the introduction of a new namespace. It makes mention about updating the exchange 2010 outlook anywhere and autodiscover url to match the exchange 2016 namespace, but does that mean that is the only change on 2010?
I have found several articles that mention not to have multiple namespaces in the same AD site as it will cause issues, as well as others that mention it is not recommended to change the namespace during a migration.
https://practical365.com/exchange-server/changing-namespaces-exchange-migration/
PlumpJack
Adjusting those FQDNs, basically changes the end-point to which client is connecting for the provided services. Adding mail.domain.com onto the new Exchange 2016 certificate would allow you to point the users to the required client access server, usually the latest Exchange version. Depends on the state of the other virtual directories on other servers, Exchange accepting the connection would either proxy or redirect.
That's your name space change :).
VickVega So it is not necessary to update the remaining URLs (ECP,EWS,ActiveSync,OAB) on 2010, to the new namespace? Won't 2016 proxy the autodiscover request to the server housing the 2010 mailboxes, so 2010 would return the old URLs to the client? If that is the case, should the old URLs resolve to the exiting vip load balancing the 2010 servers, or the new 2016 vip?
