How to migrate Exchange 2013 to 2016 – Step by step (Part 5)

This is the fifth edition of the blog on “how to migrate exchange server 2013 to 2016 using step by step guide”. In the previous edition of the blog we have discussed about the process of migrating mailboxes and public folders to Exchange Server 2016 along with methods to create a mailbox database.

For other parts of the series follow the links below:-

Migrate from exchange 2013 to 2016 (PART-1)

Migrate from exchange 2013 to 2016 (PART-2)

Migrate from exchange 2013 to 2016 (PART-3)

Migrate from exchange 2013 to 2016 (PART-4)

Migrate from exchange 2013 to 2016 (PART-6)

Migrate from exchange 2013 to 2016 (PART-7)

In the fifth edition of the blog we will briefly discuss on how to migrate the email flow from the old server to Exchange 2016 so that external inbound and outbound emails are handled by our Exchange Server 2016.

Migrate Inbound Email Flow to Exchange 2016

Exchange Server Migration of inbound email flow is directly proportional to your current email flow which means that inbound email flow migration will depend upon how the current email flow is structured. MX records play a vital role in the redirecting the Exchange server 2013. The MX record is a type of DNS record in which MX stands for “mail exchanger (Note:-For further reference on MX record follow-up the link provided). The public MX records of the Exchange server is configured to a hostname which resolves one or more than one IP addresses. These IP addresses are for on-premises or a cloud-based email filter that retrieve emails and directs then to Exchange server. The IPs can also be resolve to Exchange 2013 servers.

Two conditions are there on the basis of which migration of inbound email flow is possible.

  • When Email filter is present
  • When Email filter is not present

Email filter is present

When email filter is present in this kind of scenario modification of mail filter to direct the emails to new Exchange Server 2016 need to be done instead of directing it to an old server. For which we have to make sure that port (25 for STMP) of your email filter is open to new server (i.e. Exchange Server 2016) and to send out emails.

No email filter is present

When no email filter is present, in this kind of scenario first we need to open the port 25 of STMP from internet to Exchange New Server 2016 after which modification of the MX record is required for delivering the emails to the exchange 2016 server. For making the process successful, we have to use public DNS provider for changing MX records.

Migrate Outbound Email Flow to Exchange 2016

The Outbound email flow migration setting is dependable on the emails which the current Exchange Server sends out through smart host which later transfers the emails to the internet.

Run the following command for better knowledge on smart host setting

Get-SendConnector | fl Name,SmartHosts,

SourceTransportServers,AddressSpaces

The following command will inform either the smart host is present or not. Furthermore, there are two aspects of smart host for Outbound email flow migration which are as follows:-

  • When a smart host is present
  • When a smart host is not present

A Smart host is present

In this kind of scenario when the smart host is present the modification of smart host is needed so that it can send and receive emails from the IP of Exchange Server 2016. For which the modification of transport server on send connector is required.

Set-SendConnector “Internet Send Connector” -SourceTransportServers SHIV-EX09

When the following setting has been set for sending and receiving emails which further can use Outlook/OWA for the purpose of testing the changes done.

A Smart host is not present

In this kind of scenario when the smart host is not present creating a reverse DNS record i.e. the PTR record for the public IP of new Exchange server 2016 is required. The public IP of the Exchange server 2016 is also required to be added to SPF record.

Run the following commands after the process is over for the modification of send connectors so that new exchange server 2016 sends emails directly to internet.

Set-SendConnector “Internet Send Connector” -SourceTransportServers SHIV-EX09

Conclusion

In the fifth edition of the blog on “how to migrate exchange server 2013 to 2016 using step by step guide”. We have deliberate the methodology to migrate external inbound and outbound email flow to Exchange server 2016 so that there is no further requirement of old exchange server. In an upcoming sixth edition of the blogs, we will be discussing on how to export email relay receive connectors and other devices to the Exchange 2016 and later discuss the procedure to uninstall old exchange server 2013.

Write your comment Here

Scroll Up