Some of the users are using a mobile device (e.g. – Only Outlook 2010,20 is used on the PCs. But if you do not have one most of the steps will work for DNS load-balancing as well. – A hardware LoadBalancer is in front of Outlook Anywhere (OAW), Outlook WebAccess (OWA) and Mapi (Note: There is only MapiOverHTTP in Exchange 2016).

– The old exchange hubserver have a round robin for incoming and outgoing SMTP connection – The new Exchange 2016 environment one will contain only two server (as its no longer possible to split the roles) – exmail01 / exmail02 -> Exchange 2010 Mail Server (as DAG)

– excas01 / excas02 -> Exchange 2010 CAS Server (as CAS Array) – exhub01 / exhub02 -> Exchange 2010 Hubserver (as round robin for incoming and outgoing SMTP connection) Our current environment looks like the following: However that’s not the focus form this HowTo. Many steps here could also apply to a Exchange 2013 to Exchange 2016 migration. Abstract: In that short example we will walk true the needed steps, which will upgrade/migrate a Exchange 2010 environment to Exchange 2016.Īs there are different options how to move users from Exchange 2010 to Exchange 2016, this here is only ONE example so it might not fully fit your environment.

Exchange server 2010 to 2016