Exchange 2013 – Enable MAPI over HTTP

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 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...
Exchange 2013 – Enable MAPI over HTTP

Exchange 2016 – Outlook on the Web

In legacy versions, when you logged into your mailbox from the web, it was referred to as OWA (Outlook Web App). In Exchange 2016, this is now called Outlook on the Web. It is supported on most browsers on the latest version. Let’s take a look at what is new in...
Exchange 2013 – Enable MAPI over HTTP

Exchange 2016 – MAPI over HTTP

MAPI over HTTP was introduced in Exchange 2013 SP, it is a new transport protocol. It was not enabled by default. In Exchange 2016 MAPI over HTTP is the default protocol. It is a more reliable and stable procotol used at the Transport Layer. Take note that if you...
Exchange 2013 – Enable MAPI over HTTP

Exchange 2013 – legacyexchangeDN attribute

There seems to be a number of questions asked about the Exchange 2013 – legacyexchangeDN  and RpcClientAccessServer attribute when migrating from Exchange 2010 to Exchange 2013. In Exchange 2010 when you had a CAS Array, the above two attributes where...
    wpChatIcon