Exchange 2013

Exchange 2013

Exchange 2013
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 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...

Exchange 2013 – Enable MAPI over HTTP

Exchange 2013 – Recreating Health Mailboxes

Exchange 2013 has a feature called "Managed Availability", it is a built-in monitoring system in Exchange. A quick overview as per the Technet site regarding Managed Availability: Managed availability, also known as Active Monitoring or Local Active...

Exchange 2013 – Enable MAPI over HTTP

Exchange 2013 – CU16 Installation and Tasks.

With the release of Exchange 2013 CU16, this one is not just a simple run and install. If you are on an earlier version other than CU15, this setup is a 2 step process, why?, because you need to firstly install .NET 4.6.2 Take note that you would need to do the...

Exchange 2013 – Enable MAPI over HTTP

Exchange 2013: Install failed on Frontend Transport

Scenario: When we introduce a new version of Exchange the first thing that needs to be done is that the Schema and AD need to be prepared for the new version. Run this from a domain controller or from a server with the RSAT-Tools installed: As shown above everything...

Exchange 2013: Client Access Role install error

Exchange 2013: Client Access Role install error

In my lab, while installing Exchange 2013 on another server, the following error was thrown: "The Registry Key "Software\Microsoft\ExchangeServer\V15\Transport" does not exist under "HKEY_LOCAL_MACHINE"" Navigating to that registry key, sure thing that the key doesn't...