In this video, Robert McMillen demonstrates how to plan for MAPI over HTTP and Outlook Anywhere. MoH and OA are features that allows Outlook and mobile users to connect to the Exchange server using certificate based security while away from the office. OA is being replaced by MAPI over HTTP but OA can still be accessed by older Outlook and other clients.
- [Voiceover] MAPI over HTTP and Outlook Anywhere are features that allows Outlook and mobile users to connect to the exchange server using certificate-based security while away from the office. Outlook Anywhere is being replaced by MAPI over HTTP, but Outlook Anywhere can still be accessed by older Outlook and other clients. Initially, we had RPC over HTTP, which stands for Remote Procedure Call, and that started out with Exchange 2000, although it was not well supported, and by the time it got to 2003 many companies and organizations took advantage of being able to use Outlook without having to VPN into the office or be in the office to connect to their exchange servers.
This continued on to 2007 and to Exchange 2010. In Exchange 2010, we also had Outlook Anywhere. This was much simpler to set up, and it also uses certificate-based security. And in Exchange 2013 and 2016, Outlook Anywhere is still available. And again, it does the exact same thing on the back end that RPC over HTTP does, and that is it allows Outlook users to connect to Exchange while away from the office.
It just uses competing technology to do it. RPC was not quite as secure, and Outlook Anywhere is also faster and more efficient. Now in exchange 2013 and 2016, we have the option of doing MAPI over HTTP. MAPI, or Messaging Application Programming Interface, over HTTP is a transport layer protocol that improves the reliability and stability of the Outlook and Exchange connections by moving the transport layer to the industry-standard HTTP model.
This allows for a higher level of visibility of transport errors, and enhanced recoverability. MAPI over HTTP has another great advantage, and that is a pause and resume function, which enables supported clients such as Outlook to change networks or resume from hibernation while maintaining the same server context. This means if your internet connection is broken, you don't have to stop Outlook, reopen it, or re-authenticate back into Outlook.
If you don't have enough clients that will support MAPI over HTTP, you can actually allow specific users to use MAPI over HTTP while the rest of the organization continues to use Outlook Anywhere. Let's take a look, now, at the different Outlook versions and if they support MAPI over HTTP. 2007 and older are not supported, and this goes all the way back to the very first versions of Outlook, you will not be able to use MAPI over HTTP.
However, with Outlook 2010, if you have this particular KB hotfix, 2965295, you will be able to use MAPI over HTTP, and of course Outlook 2013, although it is recommended to at least have service pack one, in order for it to be most stable. And of course Outlook 2016. The other new thing about Exchange Server 2016 has to do with namespace and certificates. The old way was to have an internal name and an external name.
Such as your active directory name would be the internal name on your certificate, and your external name would be your public domain name, such as widget.internal would be inside the network, and widget.com would be outside the network that everyone else would see your name when you send an email. This worked fine for many years, but then in 2015 Microsoft changed the rules and said we can no longer have an internal and external name.
We now need to have just external names only. This provides for a difficult situation, because we've all set up our certificates with both internal and external names. So everyone running an Exchange organization, regardless of what version it was, had to go back in and re-key their certificates with the external names only. On the inside of your network, what you would do is use DNS manager to point internally to the inside IP address of your exchange server, and externally to the outside IP address of your firewall that is nated to your exchange server.
In an upcoming video, we will demonstrate how to configure MAPI over HTTP and Outlook Anywhere, but as long as you have the namespace and certificates ready to go, you'll have an easy time setting up this technology to work with Outlook and mobile clients while away from the office.
Join Robert McMillen as he takes you through the process, from preparation, and configuration, to deployment. Along the way, he informs you of new features, so you'll know how the 2016 version compares to 2013 or 2010. This course is designed to provide new or experienced networking professionals the essential steps needed for a successful implementation of Microsoft Exchange Server 2016.
- Upgrading and migrating considerations
- Preparing Active Directory
- Planning for database size, performance, and virtualization requirements
- Creating roles and users
- Transporting with TLS
- Using command-line setup options
- Establishing DLP
- Creating Database Availability Groups
- Troubleshooting synchronization for High Availability databases