MVP - Most Valuable Professional
rss

Just can't get enough of IT

This blog is about mostly anything in IT. But the primary focuses are Microsoft technologies like Exchange Server, Microsoft 365, Microsoft Teams, and Cloud Security.

When you install a Cumulative Update for Exchange Server 2016 you might receive the following informational message:

MAPI over HTTP, the preferred Outlook desktop client connectivity with Exchange server, is currently not enabled.
Consider enabling it using: Set-OrganizationConfig -MapiHttpEnabled $true
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.WarnMapiHttpNotEnabl
ed.aspx

This modern protocol for Outlook has been introduced to Exchange Server with Exchange Server 2013 SP1. The protocol removes the dependency on the Windows Server RPC over HTTP component. The reduced complexity enhances the reliability of the client access protocol. It's available for quite some time now. 

You can enable MAPI over HTTP on the organization level using the following Exchange cmdlet:

Set-OrganizationConfig -MapiHttpEnabled $true

You can still control the protocol setting at the user level by deactivating MAPI of HTTP for certain users if required:

Set-CASMailbox -Identity [USER] -MapiHttpEnabled:$false

If your IT infrastructure is still not ready for MAPI of HTTP, your IT components pretty outdated. It's time to move forward and modernize the infrastructure. 

NOTE
Did you know that MAPI over HTTP connects to Exchange Server using TLS to encrypt the connection? Even though that the protocol name is "over HTTP" it literally uses HTTPS to secure the connection.


What are your reasons to not enable MAPI over HTTP? Let me know.

Links

 

Enjoy Exchange Server 2016!

 

Read More »