Forum Discussion
Exchange 2010 - 2016 migration user mailbox migration issue
we're migrating from EX2010 to EX2016 and testing the user migration process.
The exchange 2010 CAS Array is configured as cas.domain.local ( that was configured by others ) and we see outlook using that fqdn to connect to.
Autodiscover URL has been set for all the exchange server to point to new exchange server
URL on the EX2016 has been set to OWA.domain.com
we tested the migration of one user mailbox but when it starts outlook we see it fails to connect to exchange server ( the new one ) since is still trying to access "cas.domain.local" and the user is prompted for credentials which, then, are not accepted.
If we set cas.domain.local in the hosts file pointing to new server it connects to exchange 2016 without issues.
Shouldn't the outlook client reconfigure itself by looking at autodiscover ?
thanks
- Yes all the autodiscover point to the exchange 2016 server.
I found what the issue was.
On the client there was a registry key MapiHttpDisabled set to 1 .
I changed it to 0 and the client connected fine
thanks
- Have a read of this. It's pretty definitive on 2010/2016 co-existence.
https://techcommunity.microsoft.com/t5/exchange-team-blog/client-connectivity-in-an-exchange-2016-coexistence-environment/ba-p/603945- Thanks
I know I have to enable Outlook Anywhere on 2010 I was wondering if that would have any impact on the users - Hello Dan,
If I got it right, and remeered correctly from previous migrations, all the EX2010 services URL should be directed to Exchange 2016, is that correct?
Both Internal and External URL.- Yep...client connectivity and mail flow gets migrated to Ex2016 first, then migrate your mailboxes
