In this blog series of Exchange 2010 to Exchange 2016 migration, we have worked on Exchange 2010 to 2016 migration planning, installed Exchange 2016 server and in previous article of this blog series, we started to work on Exchange 2016 server post installation configuration. We configured the virtual directories, SSL certificate and renamed the default mailbox database. In this part of the series we will configure mail flow and web based traffic configuration to point to Exchange 2016 server and update the records accordingly.
Moving the mail flow and web based traffic from Exchange 2010 server to Exchange 2016 server requires a maintenance window and should be planned for after hours
Switch Mail Flow and HTTPS traffic to Exchange 2016 Server
Once you have performed the installation and initial configuration of Exchange 2016 server. The next step is to plan for advanced configuration of Exchange 2016 server that requires you to create new mailbox database, set up application relay connector etc.
I do not have any application relay configured on Exchange 2010 and we are not going to setup any receive connector on Exchange 2016 for application relay.
You can download a complete step by step guide for Exchange 2016 server installation from TechNet Gallery that talks about Exchange 2010 database move from one drive to another, creating/renaming a database, setting up connector etc.
Modify Send Connector to include Exchange 2016 Server
Once you setup the receive connector based on your needs for application relay, next step is to modify the existing send connector to add your Exchange 2016 server as authorized server to send external emails. To add Exchange 2016 server to outbound connector, perform the following steps.
- Login to Exchange admin center and navigate to Mail Flow > Send Connector
- Select the existing Connector and click on edit
- Click on Scoping and add Exchange 2016 server to the authorized list of outbound servers
Once the exchange 2016 server is added to the list, monitor the mail flow and send test emails from a mailbox hosted on Exchange 2016 mailbox to internet and verify the mail flow is working fine from Exchange 2016 server.
Update Internal DNS Records to Point to Exchange 2016 Server
Once the mail flow is tested and verified, next step is to update the internal DNS records to point to Exchange 2016 server. As of now, your current records will be pointing to your Exchange 2010 server. Update the records to point to Exchange 2016 server for web traffic and mail flow.
- To update the records, login to DNS server and start the DNS snap-in
- Select the Mail and Autodiscover record and click on modify
- Update the record to point to Exchange 2016 server
Once records are updated, wait for DNS cached records to be expired before performing a testing. Once the DNS is updated on end user side, login to Exchange 2010 mailbox using the URL https://mail.domain.com/owa and verify the OWA redirection and mail flow. Once internal access is verified and everything is working fine as expected, update the external HTTPS publishing which in my case is being done via NAT rule configured on router. We’ve updated the NAT rule to send the traffic to Exchange 2016 server instead of Exchange 2010 server.
In part four of this blog series, we have performed reviewed the advanced configuration options required for Exchange 2016 server post-installation and move the mail flow and web based traffic to Exchange 2016 server. In part five of this series, we will complete the prepare a migration batch and start migrating the test mailboxes and production mailboxes to Exchange server 2016.
If you would like to read the other parts of this blog article series, please go to: