Home » Exchange Server » Migrating to Exchange Server 2016

Migrating to Exchange Server 2016

This article is the first part in a series on migrating to Exchange Server 2016. To demonstrate the Exchange 2016 migration process I’ll be using the following scenario.

The customer, Not Real University, is currently running a mixed Exchange 2010 and 2013 environment. They were in the process of upgrading to Exchange 2013 but were delayed by some technical issues. With the release of Exchange 2016, Not Real University has decided to stop the Exchange 2013 project and upgrade the entire environment to Exchange 2016 instead.

That scenario provides the opportunity to demonstrate many of the technical requirements for migrating to Exchange 2016 from both Exchange 2010 and Exchange 2013.

Environment Overview

To begin with, let’s perform a review of the existing environment to gather information that can be used for planning the migration project. Steve Goodman’s environment report script is a good tool for this purpose. Running the script reveals the following information about Not Real University.


The existing environment contains:

  • An Exchange 2010 SP3 UR14 multi-role server, hosting one database for 78 mailboxes, and a public folder database
  • An Exchange 2013 CU13 multi-role server, hosting one database for 33 mailboxes
  • An Exchange 2013 CU13 Edge Transport server for inbound/outbound mail flow

Not Real University makes use of a broad range of Exchange features, including:

  • Webmail, Outlook Anywhere and mobile access for staff and students
  • SMTP relay for internal devices and applications
  • POP and IMAP for some legacy clients and systems
  • Shared mailboxes for various teams
  • Public folders for collaboration and information sharing

The current environment basically looks like this:


During the migration project, Exchange 2016 server will be introduced to the environment:


The end goal of the project is to decommission the Exchange 2010 and 2013 servers, leaving only the Exchange 2016 server running.


To get from the current state to the end state will require many small steps and changes along the way to take into account the different Exchange features that are in use, and to ensure a seamless migration for end users with no downtime. In this series of articles I’ll walk you through the Not Real University scenario to demonstrate how to perform the migration to Exchange 2016.

More in this series:

Paul is a Microsoft MVP for Office Servers and Services. He works as a consultant, writer, and trainer specializing in Office 365 and Exchange Server. Paul is a co-author of Office 365 for IT Pros and several other books, and is also a Pluralsight author.
Category: Exchange Server


  1. Maxim says:

    Hello Paul,

    I watched your amazing course “Migrating to Exchange 2016” in Pluralsight.
    My questions is can we export Certificate from Exchange2010 and then importe it to Exchange2016?

    Thanks you!

  2. Kiran Ramesh says:

    Hello Paul.

    I would have loved to see some namespace address in the current diagram & future state diagram. And the reason for having both the Exchange server 2013 & 2016 in the during migration project snapshot with a mention of (based on the up proxy limitation). Nice article & waiting to see the next one.


  3. Mustafa says:

    Hello Paul,

    After moving mailboxes from Exchange 2010 to Exchange 2016, the outlook clients still using RPC/HTTP, the connection fails and I made it works by enabling HTTP redirection to Mapi url (mail.domain.com/mapi) on RPC Virtual Directory for Exchange 2016, another way to make it work by deleting the outlook profile but these solutions are not effecient I guess so what would you suggest to solve this issue ? besides I am using KEMP Load Balancer and as far as I know there is no rule for RPC redirection to MAPI .

    • Jozef Wu says:

      Hi Mustafa, did you manage to resolve this? I am aware of some issues when migrating to Exchange 2016 whereby you have to recycle the Autodiscover App Pool. Also, I even had to disable MapiHttp in one scenario to get rid of the many credential popups.

  4. Marvin Franklin says:

    With regards to the Exchange 2016 migration, I have Kemp Load balancers in my Exchange 2010 environment, are there any gotchas to watch out for with the configuration? FYI, I will be migrating all users to Office 2013 products?

    • The 2016 config is largely the same as 2013. I haven’t made any changes to allow my Kemp to load balance for both 2013 and 2016 on the same VIP. That said, you should always ask the vendor directly for such concerns.

  5. Terence says:

    Hi Paul

    i take a keen interest in all your articles, your contribution to our success as exchange engineers is greatly appreciated.

    i have started going through this article but seems like the rest of the series is not available. If i attempt to click on the next series below i get a page cannot be displayed error.

    •Exchange Server 2016 Migration – System Requirements

  6. Maxim says:

    Hi Paul, I followed your course “Migrating to Exchange 2016” in Pluralsight.
    I have migrated a few mailboxes from Ex2010 to ex2016. The issue I am getting now is Outlook 2013 sp1 is constantly prompting for the password (for the mailboxes that were moved to Ex2016). OWA and even ActiveSync is acting properly, it seems like the issues with Outlook only. Outlook 2013 has all required updates.

    I checked certificates, MAPI over HTTP namespaces, etc… and couldn’t find any problems there.
    Just wondering what I could miss…?

  7. Rico Willis says:

    Just implemented an Exchange server 2016, and now OWA only works with Internet Explorer. All other browsers can not access the webpage. Any tips for this issue?

Leave a Reply

Your email address will not be published. Required fields are marked *