Forum Discussion
Solved
Exchange 2010 outlookanywhere
We’re migrations from exchange 2010 to 2016. As per the requirement for coexistence OutlookAnywhere on exchange 2010 should be enabled. Since in the current Exchange 2010 is not enabled we’d like t...
Found the issue, on the client there was a reg key that was disabling mapi/https
Removed it and then the client connected successfully
@TAE
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
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
Found the issue, on the client there was a reg key that was disabling mapi/https
Removed it and then the client connected successfully