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
Does the AutoDiscoverServiceInternalUri for all servers use a name that points to the Exchange 2016 server (get-clientaccessservice | select AutoDiscoverServiceInternalUri)
client access array isn't used by Exchange 2016
client access array isn't used by Exchange 2016
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
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