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
Thanks
I know I have to enable Outlook Anywhere on 2010 I was wondering if that would have any impact on the users
I know I have to enable Outlook Anywhere on 2010 I was wondering if that would have any impact on the users