When I create a new mailbox using exchange 2016 service; MapiOverHttp is not enabled. Outlook 2016clients cannot connect to mailbox profile when this option is not enabled, while other clients can connect using RpcOverHttp.
It might be a good to have option to enable this selection / option during mailbox plan creation.
PS: To workaround; we still can use powershell to enable MapiOverHttp for a specific mailbox.
I’ve took a look into it on our environment.
That’s true, that MapiHttpEnabled has an empty value (NULL) in mailboxes on Exchange 2016. But according to the TechNet documentation (https://technet.microsoft.com/en-us/library/bb125264(v=exchg.160).aspx) the value from the Organization will be used, if the mailbox value for MapiHttpEnabled is empty.
Can you check in the Exchange Management Shell with “Get-OrganizationConfig | format-list mapi*”, which value is set globally to the organization?
Exchange 2016 has MapioverHTTP enabled by default for organizationwide, however the behavior for mailbox to support needs to be enabled by setting MapioverHTTP to $true for the mailbox as well. By default this value is null for a new mailbox.
setting mailbox level MapioverHTTP to $true will then enable Outlook 2016 profile setup, otherwise user gets an error during profile creation. ” Cannot connect exchange, server must be online etc etc””
https://technet.microsoft.com/en-us/library/mt634322(v=exchg.160).aspx article (through the end of page) has a matrix that explains how 3 values on a mailbox affects Autodiscover result..
My experience is ; after creating the mailbox for a user, I set MapioverHTTP value to $true by using
Set-Casmailbox <user ID or mailbox ID>-MapiHttpEnabled <parameter>
Hi Marco, I had issue connecting Outlook 2016 on Windows 10 through external with autodiscover. Same profile i can setup Outlook 2010 no problems, but always got an error message during profile creation with Outlook 2016. (clean install on windows 10). Successfully passed autodiscover step but sign in to server failed with error “Cannot connect exchange, server must be online..”
I connected successfully after I changed the value from null to true..
For the setups i did for Exchange 2016 they could always connect externally.
Not to say that command shouldn’t be set though, as i do think its best practice to set in on mailbox, just surprising it doesn’t work for you without it.
anyways, i will report back when i made a fix for that. normally it shouldn’t take too much time.
- Views3928 times
- Answers0 answers