Exchange 2007 reaches end of life on April 11th. What’s your plan to move?

On April 11, 2017, Exchange Server 2007 will reach End of Life. If you haven’t already begun your migration from Exchange 2007 to Office 365 or Exchange 2016, you need to start planning now. End of life means that Microsoft will no longer provide the following for Exchange 2007: Free or paid assisted support (including…


Exchange Server Deployment Assistant Updated with New Exchange 2016 Scenarios

We’re happy to announce the latest addition to the Exchange Server Deployment Assistant! You can now use the Deployment Assistant to help you configure an Exchange 2016-based hybrid deployment in organizations where Exchange 2010 is already installed. Configuring an Exchange 2016-based hybrid deployment gives you access to features like cross-premises e-discovery, enhanced secure mail, multiple…


Client Connectivity in an Exchange 2016 Coexistence Environment with Exchange 2013

Our goal with this article is to articulate the various connectivity scenarios you may encounter in your Exchange 2016 designs. To that end, this article will begin with a walk through of a deployment that consists of Exchange 2013 in a multi-site architecture and show how the connectivity changes with the introduction of Exchange 2016….

2

Client Connectivity in an Exchange 2016 Coexistence Environment with Exchange 2010

Our goal with this article is to articulate the various client connectivity scenarios you may encounter in your Exchange 2016 designs. To that end, this article will begin with a walk through of a deployment that consists of Exchange 2010 in a multi-site architecture and show how the connectivity changes with the introduction of Exchange…

4

Exchange 2016 Coexistence with Kerberos Authentication

With the release of Exchange Server 2016, I thought it would be best to document our guidance around utilizing Kerberos authentication for MAPI clients. Like with the last two releases, the solution leverages deploying an Alternate Service Account (ASA) credential so that domain-joined and domain-connected Outlook clients, as well as other MAPI clients, can utilize…

2

Enabling BitLocker on Exchange Servers

The Exchange Preferred Architecture, for both Exchange Server 2013 and Exchange Server 2016, recommends enabling BitLocker on fixed data drives that store Exchange database files. Over the years, there have been a number of questions regarding how BitLocker should be enabled on servers. However, before we discuss that, I think it is important to provide…

2

Ask the Perf Guy: Sizing Exchange 2016 Deployments

Uh oh. You are probably thinking to yourself, here comes another one of those incredibly long blog posts about sizing. Thankfully, it’s not. If you want to fully understand the sizing process for Exchange 2016, you are certainly welcome to read the previous post that I did for Exchange 2013, as the overall process is…


Exchange Server Role Requirements Calculator Update

v7.8 of the calculator introduces support for Exchange 2016! Yes, that’s right, you don’t need a separate calculator, v7.8 and later supports Exchange 2013 or Exchange 2016 deployments. Moving forward, the calculator is branded as the Exchange Server Role Requirements Calculator. When you open the calculator you will find a new drop-down option in the…

7

The Exchange 2016 Preferred Architecture

The Preferred Architecture (PA) is the Exchange Engineering Team’s best practice recommendation for what we believe is the optimum deployment architecture for Exchange 2016, and one that is very similar to what we deploy in Office 365. While Exchange 2016 offers a wide variety of architectural choices for on-premises deployments, the architecture discussed below is…

18

Load Balancing in Exchange 2016

Like Exchange 2013, Exchange 2016 does not require session affinity at the load balancing layer. To understand this statement better, and see how this impacts your designs, we need to look at how MBX2016 functions. From a protocol perspective, the following will happen: A client resolves the namespace to a load balanced virtual IP address….

6