Outlook Client Does Not Connect to Mailbox on Exchange 2016
Thanks to: https://oddytee.wordpress.com/
Lately, it seems as if I run across some new issue or anomaly on a weekly basis after implementing Exchange 2016 for one customer or another. It’s quite frustrating but it does wonders for building a personal knowledge base.
One of the latest issues I’ve experienced has been with an Outlook client (2010 or newer) not connecting to a mailbox that has been moved to (or even newly created in) Exchange 2016.
What’s odd to me is that this experience is inconsistent with other mailboxes that were previously moved to Exchange 2016 and Outlook is connecting without issue.
Essentially what happens after an existing mailbox has been moved to Exchange 2016 and the Outlook client is restarted, the autoconfiguration process fails during the “Log on to server” task.
As a result, Outlook is never able to attach to the mailbox on Exchange 2016 or update the existing profile. And, unfortunately, during the Outlook profile reconfiguration, the option to run the Outlook connection status and autoconfiguration tests are unavailable to see what the issue might be from the workstation.
ECLPete
We have been experiencing this problem since we installed Exchange 2016 Standard on a network that already has Exchange 2010 installed. We are planning a migration to 2016 over the next few days.
Almost of the workstations are using Outlook 2010 and have no issues connecting through the new Exchange 2016 proxy connection. A couple of users are on later versions of office however and have been unable to connect to their mailboxes since the new server install.
By default, Exchange 2016 installs with MAPI over Http enabled by default if you are already running an Exchange 2010 server. But disables it if you are installing in an Exchange 2013 (or above) environment. This is what gave me the idea of disbling MAPI over Http on the new Exchange 2016 server.
It worked!
Now Outlook 2013 and 2016 clients can connect without issue.
To disable globally - Powershell:
Set-OrganizationConfig -MapiHttpEnabled $false
Almost of the workstations are using Outlook 2010 and have no issues connecting through the new Exchange 2016 proxy connection. A couple of users are on later versions of office however and have been unable to connect to their mailboxes since the new server install.
By default, Exchange 2016 installs with MAPI over Http enabled by default if you are already running an Exchange 2010 server. But disables it if you are installing in an Exchange 2013 (or above) environment. This is what gave me the idea of disbling MAPI over Http on the new Exchange 2016 server.
It worked!
Now Outlook 2013 and 2016 clients can connect without issue.
To disable globally - Powershell:
Set-OrganizationConfig -MapiHttpEnabled $false
To disable for a particular mailbox - Powershell:
Set-CasMailbox <user or mailbox ID> -MapiHttpEnabled $false
Both settings can be reversed by changing $false to $true
https://docs.microsoft.com/en-us/exchange/clients/mapi-over-http/mapi-over-http?view=exchserver-2019
Set-CasMailbox <user or mailbox ID> -MapiHttpEnabled $false
Both settings can be reversed by changing $false to $true
https://docs.microsoft.com/en-us/exchange/clients/mapi-over-http/mapi-over-http?view=exchserver-2019
To fix Outlook not connecting to server, you are supposed to follow and apply few important instructions. First of all, you are supposed to make sure your account credentials or exchange server name is correct. Now, you must repair a profile and then you must make sure that your computer is connected to the network. Now, you are supposed to check your Microsoft Exchange server connection. By applying the steps you can simply find out the ways to resolve it.
ResponderEliminar