Configuring MAPI/HTTP in Exchange Server 2016

One of the many new features delivered in Exchange 2013 SP1 and Exchange 2016 is a new method of connectivity to Outlook referred to as MAPI/HTTP.  This protocol was first delivered with the update to Exchange 2013 called SP1 (otherwise known as CU4 or 15.0.847.32), however it needed to be manually enabled.  It was also rolled out to Office 365 in May of 2015.

Do you need help configuring MAPI/HTTP in Exchange Server 2016?  Email info@peters.com, and we’ll be happy to assist. For more info see – Managed IT Services.

Requirements

Before we jump into the Exchange Server 2016 configuration, let’s take a look at the requirements:

  • Currently the ONLY Outlook clients that support this are:
    1. Outlook 2016
    2. Outlook 2013 SP1
    3. Outlook 2010 (with the January 2015 Update, there were also additional patches released in the April 2015 updates)
  • A namespace that your Exchange Organization will use for the MAPI/HTTP connections (This can be the same as your existing namespace)
  • Certificates to support the namespace (if you are not using the current namespace)
  • Firewall / Load Balancer / Reverse Proxy – these will need to be updated to include the new MAPI virtual directory
  • If you are in coexistence with an Exchange 2010 Mailbox Server, the behavior will be:
    1. Exchange 2010 users will use the RPC/HTTP connections to Outlook
    2. Exchange 2016 users will use only MAPI/HTTP connections to Outlook

Configuration

First, let’s take a look at the new virtual directory settings.  You can use PowerShell to do this with the following command:

Get-MapiVirtualDirectory -server grayex1 | fl

black-box
You need to configure two things, the URL’s and the authentication method, so the PowerShell command should look something like this:

Set-MapiVirtualDirectory -server grayex1 -InternalUrl https://mapi.greyt3ch.com/mapi -ExternalUrl https://mapi.greyt3ch.com/mapi -IISAuthenticationMethods NTLM,Negotiate,OAuth

You will also notice that the virtual directory is visible though IIS also:

Configuring MAPI (2)

There is one more place where MAPI/HTTP can be controlled.  With Exchange 2013 this is defaulted to $false and with Exchange 2016 this is defaulted to $true.

black-box-small

 

 

Get-OrganizationConfig | fl mapi*

Once everything is configured, be sure to check that it is working.  You can do this by looking at the “Connection Status” screen in Outlook:

Configuring MAPI (4)

Configuring MAPI (5)

All the connections going to the server are now using the protocol HTTP.

Quick Notes:

If you are in coexistence and have an Outlook 2013 SP1 user that needs to connect to an Exchange 2010 mailbox and your CAS frontend is Exchange 2016, you can disable MAPI/HTTP by setting the following registry entry on that workstation:

  • HKCU\Software\Microsoft\Exchange
  • Create a new DWORD value named MapiHttpDisabled and set the value to 1
By |2018-12-18T11:42:37-05:00October 24th, 2016|Infrastructure Services|Comments Off on Configuring MAPI/HTTP in Exchange Server 2016

About the Author:

As a Cloud Solution Architect at Peters & Associates, Brad is responsible for providing design and strategy for Microsoft Azure, Office 365, Exchange Server and Enterprise Mobility + Security, to name a few. Brad is a Microsoft Certified Solutions Expert in Cloud Platform & Infrastructure, Messaging, Communications, Productivity, and Server Infrastructure. Brad has over 16 years of experience providing solutions and designs that make technology work better for organizations. Microsoft has recognized, trained and badged Brad as an internal Microsoft resource to allow him full access to solution architecture, roadmaps and competitive guidance.