Forum Discussion
Solved
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...
- 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
https://techcommunity.microsoft.com/t5/exchange-team-blog/client-connectivity-in-an-exchange-2016-coexistence-environment/ba-p/603945
- 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
- Dan_Snape
I've enabled OutlookAnywhere on exchange 2010 with external URL pointing to the Exchange 2016 server
I've also set the OWA,ECP,ActiveSync URLs of exchange 2010 to point to exchange 2016.
The only thing I did not change so far is the FQDN of the CAS Array in exchange 2010 which still points to Exchange 2010.
The problem is that with this configuration.
- Mailbox migrated to exchange 2016 are not able to connect.
- Mailbox still on Exchange 2010 still connects.
If I set the CAS FQDN to point to exchange 2016
- Mailbox Migrated to EX2016 are able to connect
- Mailbox still on EX2010 do not connect
- Thanks
I know I have to enable Outlook Anywhere on 2010 I was wondering if that would have any impact on the users