Exchange 2013: Enable MAPI over HTTP
If you are running Exchange 2013 and want to make use of MAPI over HTTP which is the new protocol, you need to ensure that you are running Exchange 2013 SP1 or higher.
Your clients also need to support it, depending on what versions you are running. For information of what is needed you can check the TechNet article below:
Exchange:
The first step is to logon to one of your Exchange 2013 CAS servers and head over to IIS. If you expand the "Default Web Site" you will notice a new directory called MAPI.
https://collaborationpro.com/wp-content/uploads/2017/10/ex2013mapi1.png
Now on the same server, launch the Exchange Management Shell (EMS).
If you run the command: Get-MapiVirtualDirectory, you will notice it has an Internal URL set but no External URL set.
https://collaborationpro.com/wp-content/uploads/2017/10/ex2013mapi2-1.png
Run the following command to enable it:
- Set-MapiVirtualDirectory –Identity “ServerName\mapi (Default Web Site)” -InternalUrl https://mapi.domain.com/mapi –ExternalUrl https://mapi.domain.com/mapi -IISAuthenticationMethods NTLM,Negotiate
https://collaborationpro.com/wp-content/uploads/2017/10/ex2013mapi3.png
Change ServerName with your server name and add in your own domain name where it says (domain.com).
The next step is to do an IISReset.
After this we need to run the final command:
- Set-OrganizationConfig -MapiHttpEnabled $true
Outlook
If your Outlook was still open, you would get the "Administrator has made changes" prompt. Close and open Outlook.
Now go and check the connection status for Outlook and the protocol should be HTTP.