If you are running Exchange 2013 and want to make use of MAPI over HTTP which is the new procotol, you need to ensure that are running Exchange 2013 SP1 or higher.

Your clients will 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:

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.

Exchange 2013 - enable mapi over http
Exchange 2013 - Enable MAPI over HTTP 1

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.

Exchange 2013 - enable mapi over http
Exchange 2013 - Enable MAPI over HTTP 2

Run the following command to enable it:

  • Set-MapiVirtualDirectory –Identity “ServerName\mapi (Default Web Site)” -InternalUrl https://wwwmapi.domain.com/mapi –ExternalUrl https://wwwmapi.domain.com/mapi -IISAuthenticationMethods NTLM,Negotiate
Exchange 2013 - enable mapi over http
Exchange 2013 - Enable MAPI over HTTP 3

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.

Hope it helps.

    wpChatIcon

    Discover more from COLLABORATION PRO

    Subscribe now to keep reading and get access to the full archive.

    Continue reading