Friday, April 29, 2016

Migrating from Exchange 2010 to Exchange 2016 Part-6

Till now in last 5 part i have covered process, assessment, installing Exchange Server 2016 & configuration of the Exchange 2016 such as virtual directory, Outlook anywhere,Exporting the Exchange 2010 certificate, Configuring receive connector and configure autodiscover url. Now in this part will focus on moving the mailboxes from Exchange 2010 Exchange 2016 and checking the all functionality.


Configure High Availability for Mailbox Server


Before moving the mailbox, we have to configure the out mailbox servers database properly, right now we do have two mailbox servers and we need to configure high availability for those servers as Database Availability Group (DAG). As you know Exchange 2016 DAG can contain up to 16 mailbox servers, each of which hosts copies of one or more databases that are replicated with database copies on other members of the same DAG.


Configure Database Availability Group (DAG)


As we discussed for high availability we need to create DAG for Exchange 2016, when a DAG is first created it has zero members. A minimum of two members is required for the DAG to provide high availability. You can click here for how we can configure the DAG in my post.

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.




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 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  step by steps.


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

Click on “Edit” and Click on “Client Setting” 
Click on Brows.
Select the OAB16, which we created newly.
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, than click on + sign and select move to a different database
Select the mailboxes which you want to migrate.

give the Batch name and select the target database and select other required options.
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



if you want you can check the Exchange 2010 EMC for mailbox hosting database and servers.


Once i 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.


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.

In above articles we have describe the configure high availability as a DAG for mailbox servers, updating the  Exchange 2010 virtual directories URLs, updated Internal DNS records and switching External Https connectivity, change the email flow from Exchange 2010 to Exchange 2016, created new Offline Address Book (OAB) and assigning to Exchange 2016 database and migrating the pilot mailboxes finally tested the end users functionality.

Hope it will help you to understand the migration process from Exchange 2010 to Exchange 2016.

Next part i will focus on bulk mailbox migration and public folder migration process.

Thank you!


Click here for Part-5                                                                         Here for Part-7




No comments:

Post a Comment