rapid migrating guide from exchange 2010 to … server sizing ... exchange 2010 architecture report...

Rapid Migration from Exchange 2010 to Exchange 2016

https://ucservice.blogspot.com/

Dinesh Singh

[email protected]

Blog: https://ucservice.blogspot.com/

Follow on: http://ucservice.blogspot.com/

Twitter #Dinesh1Singh


1



Contents Rapid Migration from Exchange 2010 to Exchange 2016 ............................................................. 0

Executing Summary .................................................................................................................. 3

Overview .................................................................................................................................... 3

Planning ...................................................................................................................................... 4

Exchange Server Sizing ......................................................................................................... 4

Updating Existing Environment ............................................................................................ 4

Directory Service Requirements .......................................................................................... 4

Updating Outlook Clients ..................................................................................................... 4

Naming Services .................................................................................................................... 5

Hardware Sizing for Exchange 2016 ....................................................................................... 5

Assessment Existing Exchange 2010 environment ............................................................... 5

Exchange 2010 Architecture Report .................................................................................. 5

Generate Exchange Environment Reports ....................................................................... 5

Exchange 2010 Servers Mailboxes States .......................................................................... 6

Email Traffic Report ............................................................................................................... 6

Exchange Best Practices Analyzer ...................................................................................... 6

Updates for Exchange Server 2010 ........................................................................................ 7

Update Outlook for end user ................................................................................................... 8

Preparing the server for Exchange 2016 ................................................................................ 9

Prerequisites ........................................................................................................................... 9

Preparing Active Directory .................................................................................................. 9

Extend the Active Directory Schema ............................................................................... 10

Prepare Active Directory ................................................................................................... 10

Prepare Domain .................................................................................................................. 11

Installing the Exchange Server 2016 .................................................................................... 11

Updating Autodiscover (SCP) ............................................................................................... 13

Exporting the certificate from Exchange 2010.................................................................... 13

Configure Exchange URLs (virtual Directories) ................................................................... 14

Configure Outlook Anywhere ............................................................................................... 14

Configure Receive Connector .............................................................................................. 15

Configure DAG on Exchange 2016 ...................................................................................... 18

Set up MAPI and Replication Network ............................................................................. 18

2



Configure Witness Server .................................................................................................... 21

Configure Exchange 2016 Database Availability Group .............................................. 21

Testing the DAG ................................................................................................................... 24

Enable Datacenter Activation Coordination Mode ...................................................... 25

Testing Exchange 2016 base functionality .......................................................................... 25

Updating the Exchange 2010 Virtual Directory URLs .......................................................... 26

Update Internal DNS records and switching External HTTPS Connectivity ...................... 26

Change Mail Flow Routing ..................................................................................................... 26

Creating New Offline Address Book (OAB) ......................................................................... 27

Assigning an OAB in Exchange 2016 ................................................................................ 27

Migrating the Pilot Mailbox .................................................................................................... 29

Bulk Mailbox Migration .......................................................................................................... 33

Public Folder Migration .......................................................................................................... 34

Decommissioning the Exchange Server 2010 .................................................................... 34

Decommissioning Exchange 2010 .................................................................................... 35

3



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 it’s 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.

Following are the phases we have to follow:

1. Assessment of existing Exchange 2010 environment.

2. Plan & Design Phase

3. Define the Preferred Architecture

4. Verify the Exchange Dependent Components Compatibility

5. POC Phase

6. Build & Integration Phase

7. Pilot Migration

8. Production deployment.

9. Stabilization and Documentation

10. Decommission

11. Transition and Operations

4



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 Server Sizing

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.

Updating 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”

Directory Service Requirements

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.

Updating Outlook Clients

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).

Here you can check the support Outlook version.

5



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.

Hardware Sizing for Exchange 2016 As per Recommended by Microsoft we have to prepare Hardware configuration for Exchange 2016,

and make sure you have to run the sizing calculator.

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

Assessment Existing Exchange 2010 environment This is the very important part of the any of the migration to moving new environment to do the

existing/legacy environment assessment, which will give us exact details and very beneficial for the

planning and designing section. Also it will give us change to clean up the non-required data from

existing environment.

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:

Exchange 2010 Architecture Report

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

Generate Exchange Environment Reports

Generating Exchange environment report one of the best steps to upgrading/migrating

your existing Exchange environment.

There are multiple way to generate your Exchange environment report but i will suggest user Steve

Goodman's Power Shell which will give you a good overview of your environment. This script

generates a HTML report and can be scheduled and emailed.

6



Although with tools like Visio and Word you can make such a document, it’s hard to keep these

documents up to date or use previous versions to track and check changes.

Exchange Environment Reports

Exchange 2010 Servers Mailboxes States

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

Email Traffic Report

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

Exchange Best Practices Analyzer

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.

7



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)

8



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

9



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:

Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation, RSAT-ADDS

Preparing Active Directory

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:

• .NET Framework 4.5.2 must be installed

• The RSAT-ADDS feature must be installed

• Unified Communications Managed API 4.0 Runtime

• The forest functional level must be at least Windows Server 2008.

• The Account used to run the schema update and AD preparation must be a member of

Enterprise Admins and Schema Admins.

You can run the PowerShell command Get-ADInfo.ps1 or Get-ADForest for getting the Active

Directory information of the current forest.

10



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.

PS C:\> "Exchange Schema Version = " + ([ADSI]("LDAP://CN=ms-Exch-Schema-Version-Pt," + ([ADSI]"LDAP://RootDSE").schemaNamingContext)).rangeUpper

Exchange Schema Version =

Extend the Active Directory Schema Mount the Exchange 2016 installation ISO/DVD

Open the command prompt and navigate the setup file with below command prompt

Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms

After applying the schema update we can check the version number again

PS C:\> "Exchange Schema Version = " + ([ADSI]("LDAP://CN=ms-Exch-Schema-Version-Pt," + ([ADSI]"LDAP://RootDSE").schemaNamingContext)).rangeUpper

Exchange Schema Version = 15317

Prepare Active Directory To prepare Active Directory run the following commands. Note this will also apply the schema update

if you did not perform that step already.

11



Prepare Domain Once Active Directory preparation complete, we have to start prepare domain with following

command:

Setup.exe /PrepareAllDomains /IAcceptExchangeServerLicenseTerms

Installing the Exchange Server 2016 Once we have completed the Exchange Server 2016 pre-requisites on server now we can start the

installation of Exchange Server 2016 mailbox role with below command:

Z:\setup /Mode:Install /Role:Mailbox /IAcceptExchangeServerLicenseTerms

Welcome to Microsoft Exchange Server 2016 Unattended Setup

Copying Files...

File copy complete.

Setup will now collect additional information needed for

installation.

Languages

Management tools

Mailbox role: Transport service

Mailbox role: Client Access service

Mailbox role: Unified Messaging service

Mailbox role: Mailbox service

Mailbox role: Front End Transport service

Mailbox role: Client Access Front End service

12



Performing Microsoft Exchange Server Prerequisite Check

Configuring Prerequisites COMPLETED

Prerequisite Analysis COMPLETED

Configuring Microsoft Exchange Server

Preparing Setup COMPLETED

Stopping Services COMPLETED

Copying Exchange Files COMPLETED

Language Files COMPLETED

Restoring Services COMPLETED

Language Configuration COMPLETED

Exchange Management Tools COMPLETED

Mailbox role: Transport service COMPLETED

Mailbox role: Client Access service COMPLETED

Mailbox role: Unified Messaging service COMPLETED

Mailbox role: Mailbox service COMPLETED

Mailbox role: Front End Transport service COMPLETED

Mailbox role: Client Access Front End service COMPLETED

Finalizing Setup COMPLETED

The Exchange Server setup operation completed successfully.

Setup has made changes to operating system settings that require a reboot to

13



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

Updating Autodiscover (SCP) After installing the Exchange server 2016 we have to update the SCP. The default SCP is default urls

is

https://E16.tech.com/Autodiscover/Autodiscover.xml.

https://E16-1.tech.com/Autodiscover/Autodiscover.xml.

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.

Exporting the certificate from Exchange 2010 We are going to migrate the HTTPS name from the Exchange 2010 to Exchange 2016 so we can re-

use the same SSL certificate by exporting the from Existing Exchange 2010 servers.

14



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.

Configure Exchange URLs (virtual Directories) Next steps is configure the Exchange 2016 virtual directories, for configure the virtual directories you

can use either Exchange Admin Center or Exchange PowerShell, in my case i used PowerShell

Configure Outlook Anywhere After updating the Exchange 2016 virtual directories, we have to configure Outlook anywhere for

HTTPS name authentication. As you know Outlook Anywhere is the protocol Outlook client will use

by default to communicate to Exchange 2016 replacing the MAPI/RPC within the LAN.

It is very important all setting must be correct, still if you are not publishing Outlook Anywhere

externally.

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

15



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.

16



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.

17



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.

18



Configure DAG on Exchange 2016 There are some basic rules for DAG

• No shared storage required for Exchange DAG.

• All member servers must be in the same AD domain.

• 16 copies for each database support.

• Mailbox server cannot be domain controller.

• Windows failover cluster is set up when DAG is set up.

• Data Center Activation Coordination (DAC) is configure for site resistance for prevents a split

brain syndrome.

• DAG is only high availability for the Mailbox servers.

Set up MAPI and Replication Network

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.

19



For replication network adapters we need to disable "Client for Microsoft Network" and "File and

Printer Sharing for Microsoft networks".

Set the IP address for Replication adapter

20



Next set the DNS tab and uncheck the "Register this connection's addresses in DNS".

21



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.

Configure Exchange 2016 Database Availability Group

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:

22



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:

Get-DatabaseAvailabilitygroup DAG01 -Status

Now you can check the where our witness server is also:

We can verify into witness server also

As you know the Exchange 2016 DAG will configure Network automatically, so now you can check the

status of the DAG Network:

You can check some other configuration such as:

23



Now you check the mailbox database

Now you have to add database one by one on DAG

Now we can check the database copy status:

24



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:

Once NIC disabled, checked the Database copy status now

Now we checked the database getting active on another server properly, now i enabled the MAPI

network for mailbox server.

25



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”.

Set-DatabaseAvailabilityGroup DAG01 -DatacenterActivationMode DagOnly

Testing Exchange 2016 base functionality Before we can move namespaces and mailboxes across to Exchange Server 2016 we need to do test

the new server is fully functional.

I created some mailboxes in Exchange 2016 and test the email flow, i sent email from my Exchange

2010 admin account to Exchange 2016 admin it work fine.

26



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.

Update Internal DNS records and switching External HTTPS Connectivity We need to update the internal DNS record to direct traffic internally at the Exchange 2016 server,

we need to change internal DNS records so that both the autodiscover name and HTTPS namespace

are configure with the new IP address (Exchange 2016).

Client will not be immediately redirect to use the Exchange 2016 server as the proxy for client access,

as soon as client can access the server retry login and client access to ensure no issues exit. If internal

client can access works fine than update the external HTTPS publishing.

Change Mail Flow Routing In above we see we already tested Exchange 2016 can receive mail and delivered to Exchange 2010

users, default Exchange 2016 is already configured to receive email from the Internal using

Anonymous permissions on the default receive connector.

Also we have to ensure that inbound mail flow is not interrupted before moving on to migrating.

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.

27



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.

If you want to whats new in OAB http://ucservice.blogspot.com/2014/11/offline-address-book-

oab-continue.html you can click here

Open the PowerShell and type below command

New-OfflineAddressBook –Name “OAB16” –AdressLists “\Default Global Address List”

Now you can see the status of the OAB by using the Get-OfflineAddressBook command.

Assigning an OAB in Exchange 2016

Open Exchange 2016 ECP with Administrator account.

Click on “Servers” and select “Databases” select database you want to assign the OAB

28



Click on “Edit” and Click on “Client Setting”

Click on Brows.

Select the OAB16, which we created newly.

29



Click on save.

Migrating the Pilot Mailbox

We do have number of methods that can be used to migrate mailboxes from Exchange 2010 to

Exchange 2016, such as Exchange Admin Center

Open ECP select recipients and select migration tab, then click on + sign and select move to a different

database

Select the mailboxes which you want to migrate.

30



Give the Batch name and select the target database and select other required options.

31



Select the recipients which will get the notification after complete the Job and select preferred option

to complete the batch.

Once finish it will sync

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

32



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 it’s

working.

33



Also i verify the Outlook calendar whether availability is working or not, and found its working as

expected vice versa.

It means my end user don't have any issues.

Bulk Mailbox Migration Once we have tested the pilot user’s functionality, everything is working as expected, now we have

to migrate bulk mailboxes from Exchange 2010 to Exchange 2016.

We can use PowerShell command to migrate mailbox, which is the best way:

Import-CSV "C:\Move.CSV" | Foreach (New-MoveRequest _identity $_.Identity -TargetDatabase

MDB01)

34



We can also get the move status

Public Folder Migration

As you know most of our customer still using public folder in on premise Exchange 2010 and want to

migrate on newer version

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.

Migrating Public Folder to Exchange 2016 slimier to Migrating to Exchange 2013.

You can check the my post to Migrate Public Folder

“http://ucservice.blogspot.com/2016/01/migration-exchange-2010-to-exchange_98.html in

details which described step by steps

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 .

Decommissioning the Exchange Server 2010

Now we are reached to remove the Exchange server 2010 from our Exchange environment. As we

are good to go in Exchange Server 2016 environment, already we change the mail flow routing,

assigned new offline address book, moved all legacy mailboxes on Exchange 2016 also we migrated

public folder on new modern public folder.

35



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:

1. Double check all mailboxes has been migrated on Exchange 2016.

2. Verify all Public folder has been migrated to modern public folder in Exchange 2016.

3. Verify mail flow happening via 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.

6. Monitor the Exchange environment for one week.

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.

Decommissioning Exchange 2010

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:

Open PowerShell Management and run following cmdlet

Get-Mailbox –Archive Get-Mailbox –Arbitration

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).

36



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:

Once mailbox moved you can verify in Exchange 2016 server,

Now open Exchange 2010 Management Console select Organization Configuration-Mailbox-

Database Management-select mailbox database-right click-Select Dismount Database.

Now Remove the Database select Yes.

37



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.

38



Then delete or move the database file (.edb) and the logs for this Database

Then mount the database-Yes to all- it will mount empty database

39



Select Ok.

Now close the Exchange System Manager and open Control panel select Microsoft Exchange Server

2010 and select Uninstall

Click Next

40



Unselect all the installed roles-Unselect the Management tools-Next

Click Next

41



Click on Uninstall.

Again click on Uninstall

42



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 I’m employed, it’s 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.

Use it completely on your risk.

If you feel some Content has to be removed which is not meeting any guidelines, Please

email me at [email protected]

Follow on: http://ucservice.blogspot.com/

Twitter” #Dinesh1Singh

Thank you!

rapid migrating guide from exchange 2010 to … server sizing ... exchange 2010 architecture report...

Documents