Professional Documents
Culture Documents
Dinesh Singh
DINESH.111@HOTMAIL.COM
Blog: https://ucservice.blogspot.com/
Follow on: http://ucservice.blogspot.com/
Twitter #Dinesh1Singh
2
Rapid Migration from Exchange 2010 to Exchange 2016
https://ucservice.blogspot.com/
Executing Summary
Microsoft Exchange Server 2016 brings a new set of technologies, features, and services to Exchange
Server. Its goal is to support people and organizations as their work habits evolve from a
communication focus to a collaboration focus. At the same time, Exchange 2016 helps lower the total
cost of ownership whether you deploy Exchange 2016 on-premises or provision your mailboxes in
the cloud.
This documents will be focus on the detail migration steps to Exchange Server 2016 from Exchange
2010, which will also cover Database Availability Groups for high availability.
Overview
Before starting its important to understand that a key architectural change has been made in
Exchange 2016. Exchange 2010 had a number of separate roles; Client Access, Hub Transport,
Mailbox and Unified Messaging.
In Exchange 2016 only a single role is used, the Mailbox role. This contains all necessary components
required.
There are some best practices and recommendation before implementing /deployment/migration,
so in this series we are going migrate Exchange 2010 to Exchange 2016 which will also be co-existence
environment.
3
Rapid Migration from Exchange 2010 to Exchange 2016
https://ucservice.blogspot.com/
Planning
There are some major changes on the Architectural of Exchange 2016, in Exchange we do have
separate servers roles: Mailbox, Client Access, and HUB Transport & Unified Messaging. In Exchange
2016 Microsoft introduced only one server role, which contains all components.
As per Microsoft before migrating we have to follow up some best practices such as:
Exchange 2016 having only one Server roles which is taking care of all Exchange components so it
means hardware sizing is the most critical part of deployment. We can use the Exchange 2016
server requirement calculator https://gallery.technet.microsoft.com/office/Exchange-2013-
Server-Role-f8a61780, which will give us clear way to implements the Exchange server in existing
environment.
Before introduce the Exchange 2016 into Existing environment you have to have update the Exchange
2010 with require Service Pack 3 with Update Roll up 11. You can download from here
https://www.microsoft.com/en-us/download/details.aspx?id=49043
In Exchange 2016 Microsoft recommended first time minimum support Forest Functional Level and
Domain Functional Level is now Windows 2008 or above. So make sure your environment is ready for
this.
As you already know Exchange 2016 support outlook 2010 and above on Windows and on the Mac
Outlook 2011 and higher.
All version of Outlook 2016 and Outlook 2013 are supported, Outlook 2010 is supported with the
latest updates (KB2965295).
4
Rapid Migration from Exchange 2010 to Exchange 2016
https://ucservice.blogspot.com/
Naming Services
Before implements you have to decide the names used by the clients to access the Exchange. In Co-
existence with Exchange 2010, 2013 and Exchange 2016 allows sharing of the same HTTPS names for
autodiscover, OWA, ActiveSync and other services, which will make your transition very easy, so
before moving forward you have to finalize the names.
I will recommend to go for Physical hardware if not or some business decision you are choosing
virtualization than you have to follow up the guidance for Exchange 2016 in Virtualization
https://technet.microsoft.com/en-us/library/jj619301(v=exchg.160).aspx
There are many way to do the Exchange 2010 environment assessment, I will go for some very easy
way to do, there are some option:
First of all i will suggest you get the current your Exchange environment architecture details. some
time we do have old architecture documents but in between there are lot of the changes happen on
environment so best practice to the latest Exchange 2010 environment Architecture report, you can
use following PowerShell script which will give you details Architecture details.
Exchange 2010 Architecture Report https://gallery.technet.microsoft.com/office/Exchange-2010-
Architecture-9368ff56
5
Rapid Migration from Exchange 2010 to Exchange 2016
https://ucservice.blogspot.com/
Although with tools like Visio and Word you can make such a document, its hard to keep these
documents up to date or use previous versions to track and check changes.
Exchange Environment Reports
There are multiple way to get the Mailboxes States which include the size of the mailboxes in
current environment, i will suggest get the at least last 6 months report which will help you to
future forecast of the mailboxes size quota & storage calculation.
You can use following PowerShell script for getting Mailboxes States:
Exchange 2010 Mailbox Size Report
Generate Mailbox Size and Information Reports
We need to factor the storage & transport capacity for future Exchange environment. The simplest
way to deal with that would be to ignore this fact and oversize transport, which will provide
additional capacity for unexpected peaks in message traffic. An alternative way to determine daily
message flow would be to evaluate performance counters within your existing messaging system.
In order to figure out the messages per day that you expect to run through the system, you can look
at the user count and messaging profile. Simply multiplying these together will give you a total daily
mail volume. You can use following PowerShell script to get the Email Traffic report:
Email Traffic and Daily Email Traffic
The Exchange Best Practices Analyzer programmatically collects settings and values from data
repositories such as Active Directory, registry, metabase and performance monitor. Once collected,
a set of comprehensive best practice rules are applied to the topology. The Microsoft Exchange Best
Practices Analyzer is designed for administrators who want to determine the overall health of their
Exchange servers and topology. The tool scans Exchange servers and identifies items that do not
conform to Microsoft best practices. You can download from here: Exchange Best Practices Analyzer
https://www.microsoft.com/en-us/download/details.aspx?id=22485
you can use other tools, scripts to discover your Exchange environment before moving to Exchange
2010.
6
Rapid Migration from Exchange 2010 to Exchange 2016
https://ucservice.blogspot.com/
Updates for Exchange Server 2010
The minimum supported patch level for Exchange Servers 2010 is Service Pack 3 with Update Rollup
11 for introducing Exchange Server 2016.
You can download Exchange Server 2010 Service pack 3
Also you can download Exchange Server SP3 update Rollup 11 or you can download latest Rollup
as you can see my Exchange Server 2010 environment is updated and ready for getting Exchange
2016.
My Servers are with Update Rollup 12 for Exchange Server 2010 SP3 (KB3096066)
7
Rapid Migration from Exchange 2010 to Exchange 2016
https://ucservice.blogspot.com/
Update Outlook for end user
One of the very critical step is to update the Outlook client , in past experience this part is very
critical and show stopper, once you introduce the Exchange 2016 in your environment, your end
user can access their email without any issues.
Exchange Server 2016 supports Outlook 2010 and above for Windows client and on Mac Outlook
2011 and higher. Outlook 2007 is no more supported.
All versions of Outlook 2016 and Outlook 2013 are supported. Outlook 2010 is supported
8
Rapid Migration from Exchange 2010 to Exchange 2016
https://ucservice.blogspot.com/
Preparing the server for Exchange 2016
Prerequisites
Now we need to install prerequisite for installing the Exchange Server 2016, to install the pre-
requisite open the PowerShell and execute the following command:
A new installation of the Exchange Server 2016 will apply the Active Directory schema update.
Automatically. Windows Server 2012 R2 server with the Exchange Server 2016 mailbox server role
pre-requisites installed doesn't quite meet the requirements for that you need to add the RSAT-
ADDS feature.
When you are running the schema update from as Exchange server then the following requirement
you have to apply:
You can run the PowerShell command Get-ADInfo.ps1 or Get-ADForest for getting the Active
Directory information of the current forest.
9
Rapid Migration from Exchange 2010 to Exchange 2016
https://ucservice.blogspot.com/
Since, we already have the Exchange Server 2010 environment and we need to check the current
Exchange schema version before applying the any update. For that you can use the one liner, which
is created by Exchange Server MVP Michael B Smith.
After applying the schema update we can check the version number again
10
Rapid Migration from Exchange 2010 to Exchange 2016
https://ucservice.blogspot.com/
Prepare Domain
Once Active Directory preparation complete, we have to start prepare domain with following
command:
Setup.exe /PrepareAllDomains /IAcceptExchangeServerLicenseTerms
Copying Files...
installation.
Languages
Management tools
11
Rapid Migration from Exchange 2010 to Exchange 2016
https://ucservice.blogspot.com/
Performing Microsoft Exchange Server Prerequisite Check
Setup has made changes to operating system settings that require a reboot to
12
Rapid Migration from Exchange 2010 to Exchange 2016
https://ucservice.blogspot.com/
take effect. Please reboot this server prior to placing it into production.
After setup has completed restart the server before doing any configuration on Exchange Server
2016.
Once installation complete open Exchange Administrative Center
When launching EAC via local host we are getting the certificate error because we have not installed
the SSL certificate, just click on "continue to this website to access" the EAC
After successfully login we can see the all legacy mailboxes under the recipients
Which is not suitable because we don't have the trusted SSL and domain joined clients will get the
certificate warning error. So we will update the URL as per Exchange 2010
After making the changes, any client trying to connect the Exchange 2016 SCP (autodiscover) before
we make co-existence will be direct to use the Exchange 2010.
13
Rapid Migration from Exchange 2010 to Exchange 2016
https://ucservice.blogspot.com/
You can click here for follow the complete steps Exporting Certificate from Exchange 2010
http://ucservice.blogspot.com/2016/01/migration-exchange-2010-to-exchange_72.html , which i
export from Exchange 2010 to Exchange 2013, same steps we can follow for Exchange 2016.
First open the Exchange Admin Center, select the Servers tab select the server, click on edit, once you
get the edit page select the Outlook Anywhere than set the correct configuration such as External
Host Name, Internal Host Name and authentication Method
14
Rapid Migration from Exchange 2010 to Exchange 2016
https://ucservice.blogspot.com/
Configure Receive Connector
Next step is to configure the receive connector on Exchange 2016 as per Exchange 2010. Default and
client connector are already created.
Open the Exchange Admin Center select mail flow tab and select receive connectors
Click on + sign it will give you a new wizard for new receive connector, give the name of the connector
and select "Frontend Transport" from Role and select "Customize" from the type.
15
Rapid Migration from Exchange 2010 to Exchange 2016
https://ucservice.blogspot.com/
Next page, we will select the Network and default port will be 25 for SMTP
Next page we have to choose IP addresses that the receive connector will accept mail.
16
Rapid Migration from Exchange 2010 to Exchange 2016
https://ucservice.blogspot.com/
Once complete you can see the connector in EAC.
Now click on edit for newly created receive connector and select the security tab and select the
Externally secured" from authentication and select Exchange servers and Anonymous users from
permission groups.
17
Rapid Migration from Exchange 2010 to Exchange 2016
https://ucservice.blogspot.com/
Configure DAG on Exchange 2016
There are some basic rules for DAG
First of all we have to add one more network card to configure MAPI & Replication network in your
mailbox servers, you can rename for avoiding the confusion.
We are using 192.168.209.0/24 for MAPI and 172.10.0.0/16 for Replication network.
Next step is to disable the network features that are not require in MAPI adapters, IPv6 should be
enabled.
18
Rapid Migration from Exchange 2010 to Exchange 2016
https://ucservice.blogspot.com/
For replication network adapters we need to disable "Client for Microsoft Network" and "File and
Printer Sharing for Microsoft networks".
19
Rapid Migration from Exchange 2010 to Exchange 2016
https://ucservice.blogspot.com/
Next set the DNS tab and uncheck the "Register this connection's addresses in DNS".
20
Rapid Migration from Exchange 2010 to Exchange 2016
https://ucservice.blogspot.com/
Configure Witness Server
You must have an odd number of voters in a cluster. If you have an even number of mailbox servers
in the DAG, the DAG will use a node and file share majority quorum model where it will use a file
share witness which is created on a witness server during the DAG setup. If you have as odd
number of mailbox servers in the DAG then the DAG will use the node majority quorum model and
the file share witness will not be used.
As per recommendation domain controller or DAG member should not be witness server, when we
create the DAG, Exchange will create a witness directory and share on the witness server. For this
you the Exchange Trusted Subsystem" AD group is a local administrator on the witness server.
Also add the Exchange Trusted Subsystem group as a local administrator on the witness server.
I will start to use PowerShell to configure DAG, DAG Name is DAG01 and witness Server is my DC (I
don't have any option in my lab).
We can run the following PowerShell command:
New-DatabaseAvailabilityGroup -Name DAG01 -WitnessServer DC.tech.com -FileSystem ReFs
Now add the mailbox servers, we do have two mailbox server E16 and E16-1, we can use the below
cmdlet:
21
Rapid Migration from Exchange 2010 to Exchange 2016
https://ucservice.blogspot.com/
Add-DatabaseAvailabilityGroupServer -identity DAG01 -mailboxServer E16
Add-DatabaseAvailabilityGroupServer -identity DAG01 -mailboxServer E16-1
After that we can check the status of the DAG with below command:
Now you can check the where our witness server is also:
As you know the Exchange 2016 DAG will configure Network automatically, so now you can check the
status of the DAG Network:
23
Rapid Migration from Exchange 2010 to Exchange 2016
https://ucservice.blogspot.com/
Testing the DAG
Once configuration complete, i want to check the fail over, so now i have disable one of the mailbox
server MAPI Network card for testing the actual fail over:
Now we checked the database getting active on another server properly, now i enabled the MAPI
network for mailbox server.
24
Rapid Migration from Exchange 2010 to Exchange 2016
https://ucservice.blogspot.com/
Enable Datacenter Activation Coordination Mode
If you have the two site and DAG configure you can use the DAC mode to avoid the split-brain. You
can use below command to enable the DAC mode in DAG. You can click here for deep dive for DAC
MODE http://ucservice.blogspot.com/2010/05/datacenter-activation-coordination-mode.html.
25
Rapid Migration from Exchange 2010 to Exchange 2016
https://ucservice.blogspot.com/
Updating the Exchange 2010 Virtual Directory URLs
As you know Exchange 2016 can support as a proxy for Exchange 2010 servers. It means that it is easy
to allow Exchange 2010 and Exchange 2016 to co-exist using the same URLs to accessing the services.
Now we can move the autodiscover.tech.com from Exchange 2010 to Exchange 2016, along with this
we have to change the DNS/Firewall so that Https client traffic will go via Exchange 2016 to Exchange
2010 servers.
We have to update our core URLs for Exchange 2010 to remove the External URL value. We will also
enabled Outlook anywhere, configure with the Https name that will move to Exchange 2016, you
can follow same as in Exchange 2013 http://ucservice.blogspot.com/2016/01/migration-
exchange-2010-to-exchange_23.html process.
Next step is to make changes outbound mail flow and allow to Exchange 2016 take the outbound
email flow rather than via Exchange 2010 server. We have to make sure firewall rules allow the
Exchange 2016 server IP address to initiate connections to Internet hosts on TCP port 25.
Once ensure that the Exchange 2016 server is allowed to relay outbound mail, than we are ready to
update the Send Connector. For updating the Send Connector click here
http://ucservice.blogspot.com/2016/01/migration-exchange-2010-to-exchange_8.html step
by steps.
26
Rapid Migration from Exchange 2010 to Exchange 2016
https://ucservice.blogspot.com/
Creating New Offline Address Book (OAB)
As part of the installation of Exchange 2016, a new offline address book was created and set the
default. Now i want to create new OAB so that i will remove old Exchange 2010 OAB.
Now you can see the status of the OAB by using the Get-OfflineAddressBook command.
Click on Servers and select Databases select database you want to assign the OAB
27
Rapid Migration from Exchange 2010 to Exchange 2016
https://ucservice.blogspot.com/
Click on Edit and Click on Client Setting
Click on Brows.
28
Rapid Migration from Exchange 2010 to Exchange 2016
https://ucservice.blogspot.com/
Click on save.
Open ECP select recipients and select migration tab, then click on + sign and select move to a different
database
29
Rapid Migration from Exchange 2010 to Exchange 2016
https://ucservice.blogspot.com/
Give the Batch name and select the target database and select other required options.
30
Rapid Migration from Exchange 2010 to Exchange 2016
https://ucservice.blogspot.com/
Select the recipients which will get the notification after complete the Job and select preferred option
to complete the batch.
Second easy option to use the Power Shell to migrate the mailboxes.
Open Power Shell and type below command, as i have multiple mailbox so i'm using export csv option.
Import-CSV "C:\Move.CSV" | Foreach (New-MoveRequest _identity $_.Identity -TargetDatabase
MDB01)
Now you can monitor the move request with command Get-MoveRequestStatistics
31
Rapid Migration from Exchange 2010 to Exchange 2016
https://ucservice.blogspot.com/
If you want you can check the Exchange 2010 EMC for mailbox hosting database and servers.
Once moved pilot users, now i have Exchange 2010 and Exchange 2016 users, before moving
forward i will check the client end functionality.
From Exchange 2016 i sent email to Exchange 2010 and getting smooth delivery vice versa its
working.
32
Rapid Migration from Exchange 2010 to Exchange 2016
https://ucservice.blogspot.com/
Also i verify the Outlook calendar whether availability is working or not, and found its working as
expected vice versa.
33
Rapid Migration from Exchange 2010 to Exchange 2016
https://ucservice.blogspot.com/
We can also get the move status
Once all mailbox migrated into Exchange Server 2016, now one of the most critical part is migrate the
Exchange 2010 public folder to Exchange 2016.
There are some issue Data loss may occur during public folder migration to Exchange 2013, Exchange
2016, before starting batch migration, make sure that all public folders have a replica on the public
folder database that will be specified as the source for migration. Also, make sure that the public
replication is in sync. You can check here for more workaround for Public folder migration
https://support.microsoft.com/en-us/kb/3161916 .
34
Rapid Migration from Exchange 2010 to Exchange 2016
https://ucservice.blogspot.com/
Before removing the Exchange 2010 servers its important to verify the some of the application or
devices are using the Exchange 2010 server as a relay server, we need to double check all devices &
application has been moved on Exchange 2016 servers.
Also verify the inbound and outbound mail flow, it should be flow via Exchange 2016 servers.
For decommissioning the Exchange 2010 servers you need to follow up the ITSM process, there are
some steps you have to follow up:
2. Verify all Public folder has been migrated to modern public folder in Exchange 2016.
4. All related application & devices are configured Exchange 2016 servers as a relay server.
5. Once verify all above points stop the Exchange services from Exchange servers and set the disable
state.
7. If everything working fine than shutdown the server for 2 week and monitor the environment.
8. If everything fine after shut downing the Exchange 2010 server process for decommissioning the
Exchange 2010 servers.
Now we reached final stage of the migration, before we can retire the old server we need to remove
the all databases of those servers, even though we moved all mailboxes to Exchange 2013 servers, if
you try to delete the database it will give you error that it is not empty, this is because it will have
either Archive or Arbitration mailboxes in it, to see those mailboxes use following cmdlet:
You can see that still we have arbitration mailboxes in Exchange 2010 databases, to move those
mailboxes use following command (Execute this command from Exchange 2013 Server).
35
Rapid Migration from Exchange 2010 to Exchange 2016
https://ucservice.blogspot.com/
Get-Mailbox Database database name Arbirtration | New-MoveRequest TargetDatabase
DB2
Same command you can use for move your Archive mailboxes in case if you have. You may also have
discovery search mailboxes that will need migrate, to do so use the following command:
New-MoveRequest DiscoverySearchMailbox* -TargetDatabase Mailboxe Database-2016
Wait a while and you can check the status of the mailbox movement with following command:
36
Rapid Migration from Exchange 2010 to Exchange 2016
https://ucservice.blogspot.com/
Click on OK.
Now we need to remove Offline address book, Select Offline Address Book Tab- Default Offline
Address Book-Remove Select Yes.
If you try and remove the Public folder database it will send error that it contain replicas which you
cannot remove, the easiest way I have found to remove it is as follows. Dismount the Public Folder
Database.
37
Rapid Migration from Exchange 2010 to Exchange 2016
https://ucservice.blogspot.com/
Then delete or move the database file (.edb) and the logs for this Database
38
Rapid Migration from Exchange 2010 to Exchange 2016
https://ucservice.blogspot.com/
Select Ok.
Now close the Exchange System Manager and open Control panel select Microsoft Exchange Server
2010 and select Uninstall
Click Next
39
Rapid Migration from Exchange 2010 to Exchange 2016
https://ucservice.blogspot.com/
Unselect all the installed roles-Unselect the Management tools-Next
Click Next
40
Rapid Migration from Exchange 2010 to Exchange 2016
https://ucservice.blogspot.com/
Click on Uninstall.
41
Rapid Migration from Exchange 2010 to Exchange 2016
https://ucservice.blogspot.com/
Now click on finish
Finally we de-commissioned the Exchange 2010 from server and new environment is fully Exchange
2016.
Disclaimer:
The article or information provided in this documents, no way confers to Microsoft or the
company Im employed, its completely my personal view & thoughts and it may not suit
your Environment. Please have Good Knowledge and understanding on what you are
doing it is strongly recommended to test it on a lab, before making changes in the
production environment.
If you feel some Content has to be removed which is not meeting any guidelines, Please
email me at dinesh.111@hotmail.com
Twitter #Dinesh1Singh
Thank you!
42
Rapid Migration from Exchange 2010 to Exchange 2016
https://ucservice.blogspot.com/