Quantcast
Channel: Exchange Server 2013 - Setup, Deployment, Updates, and Migration forum
Viewing all articles
Browse latest Browse all 7129

Exchange 2010-2013 co-existence - need for OWA/ActiveSync legacy namespace?

$
0
0

Hi all

Straight to the point: how to I update units that were set up manually with Exchange ActiveSync (pointing to owa.domain.com) with a temporary legacy namespace owa-legacy.domain.com, and then back to owa.domain.com?

Background: I did a test run of migrating a single-server installation from Exchange 2010 to Exchange 2013. As expected, after moving a user's mailbox to the new Exchange 2013 CAS with owa.domain.com still pointing to Exchange 2010, the user was unable to log in at the Exchange 2010 OWA, and the ActiveSync unit was unable to fetch mail.

So I created a legacy namespace (owa-legacy.domain.com) and set this as the URL on the Exchange 2010 server, and waited for it to populate, then switched owa.domain.com to Exchange 2013. But the URL on ActiveSync units was still pointing to the wrong URL.

What did I overlook or not understand, or am I making migration more complex than needed?

Thanks for reading and best regards
/Maurice

PS: here were some of my pre-post readings: Exchange 2003-2013 co-existence, even better Exchange 2003-2013 co-existence, Exchange 2010-2013 co-existence slides, Upgrading ActiveSync to Exchange 2010,


Viewing all articles
Browse latest Browse all 7129

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>