Shulou(Shulou.com)06/01 Report--

Today, I will talk to you about the step-by-step solution for migrating Exchange 2016 to Exchange 2019. Many people may not know much about it. In order to make you understand better, the editor has summarized the following content for you. I hope you can get something according to this article.

Part 1

Install Exchange 2019 on the new server

Part II

Install the SSL certificate on Exchange 2019

The installed Exchange server creates a certificate that is self-signed and also includes the FQDN and server hostname. Hostnames are typically used to establish external connections so that they can prevent internal servers from being exposed to Internet.

Note: when migrating the CAS role to Exchange 2019, we need to ensure that Exchange 2019 uses the same certificate as Exchange 2016, and we need to perform a switch to point the "MX" records used by the old exchange server to Exchange 2019.

Here are the steps above to install the SSL certificate

Use EAC to install SSL certificates (Exchange Management Center)

Download and start the certificate ZIP file. The certificate will be named your_domain_name.cer.

Your_domain_name.cer.file needs to be copied to an Exchange Server 2019 network shared folder

Now, copy the your_domain_name.cer file to the network shared folder of the Exchange 2019 server that saved the CSR.

Browse to the URL of the server and access the Exchange Management Center (EAC) by opening a browser.

Enter the domain / user name and password on the Exchange Central Administration credentials page and click Log in.

Now click the server on the left sidebar menu, EAC, and then click Certificate on the top menu.

On the Certificate page, select the certificate you requested, and then click the finish link in the certificate request.

Note: certificate requests are listed by their friendly name.

Now enter the UNC path where the SSL certificate is located, and then click OK. (for example. \\ Abc\ certificates\ your_domain_name.cer)

The certificate will be successfully installed on the Exchange 2019 server and check whether the status of the certificate request is now valid

Assign servic

Now, on the Certificate page, select the SSL certificate you just installed, and then select the pencil option.

Now click the service in the Certificate window.

Check all services to enable SSL certificates, and then click Save.

SSL certificates should be enabled for the service you select on the Exchange 2019 server

The third part is gradually

The following services must be configured:-

Set up Outlook Anywhere

Set up Exchange Control Panel URL

Set up Outlook Web Access URL

Set up the Exchange Web service URL

Set up ActiveSync URL

Set up offline address book URL

Set up the MAPI virtual directory

Outlook Anywhere Settin

Exchange Control Panel ECP URL Settings

Outlook Web Access URL Settin

Exchange Web Service EWS URL Settings

ActiveSync URL Settin

Offline address Book OAB URL Settings

Set up the MAPI virtual directory

MS Exchange AutoDiscovery AppPool recovery

We need to force the use of the autodiscovery service to use the new URL where we need to recycle MSExchangeAutodiscoverAppPool without shutting down the server

NAT rule firewall configuration (change port mapping)

The new Exchange server migration 2019 server requires a new static public IP to establish an external client connection. First, open server port 443, the standard TCP port for SSL connections, and assign static one-to-one NAT rules.

CAS server migration test (if you change the Autodiscover MX record, both the internal and external network DNS will be updated)

The "MX" record is used to establish client connections in legacy Exchange Server 2016 and to retrieve autodiscovery settings using external clients. After you complete the Outlook Anywhere configuration and virtual directory settings for the new Exchange server, you can easily migrate the client to the new server.

Add an X record to the managed file to redirect it to the new server (Exchange 2019) as an alternative to the old server. First configure the following settings; open the hosts file using notepad, and then add a new line to use the X record as the IP for the administrator to point to the new Exchange server.

After completing the above configuration settings, note that the client can connect to the new Exchange server. Also be sure to test the accessibility of shared mailboxes, public folders, calendars, send / receive e-mail, and download offline address books.

After all the necessity tests are complete, update the hosts file to resolve the X record to the public IP of the Exchange server. Ensure that clients on the external network are also connected to the server. After all the testing is done, you need to delete the entries in the hosts file.

The fourth part

Move and rename the default Exchange Server 2019 mailbox database (because it is installed on disk D, it does not need to be moved)

Move the Exchange Server 2016 mailbox to 2019

When you move the Exchange Server 2016 mailbox to 2019, make sure that there is enough space available because it creates a large number of logs. In addition, it is wiser to back up regularly so that it can be used at the time of backup.

Here are the types of mailboxes we will move:

Arbitration mailbox or system mailbox.

User mailbox

Public folders and archive mailboxes

Arbitration mailbox

To move the quorum mailbox first, you need to run this command to get a list of mailbox databases located on the Exchange 2019 server, which is executed on Exchange Server 2016

Get-Mailbox-Arbitration | FL Name,Displayname

Get-MailboxDatabase | Where {$_ .AdminDisplayVersion-Like "* 15.1*"} | Format-Table Name, ServerName

Get-Mailbox-Arbitration

Now, in Exchange 2016, run the following command to move the Microsoft Exchange system mailbox to the mailbox database on the Exchange 2019 server

Get-Mailbox-Arbitration | New-MoveRequest-TargetDatabase Mailbox2019

To confirm that the following mailboxes have been moved, run the command.

Get-MoveRequest | GET-MoveRequestStatistics

Move public folders in Exchange 2019

It is easier to move public folders than in previous versions. Before moving any further, we need to get a list of all available public folders by running the following command. Email is the exchange 2016 server name

Get-mailbox-Server email-PublicFolder

Used to move public folders to a new Exchange Server. To do this, you must use the following command.

New-Moverequest it-TargetDatabase Mailbox2019

Mobile user mailbox

You can use many different options to migrate user mailboxes. You can move individual and entire mailbox databases.

With the command mentioned, users can easily move their archive mailboxes and user mailboxes.

Run the following command to move all mailboxes from the old Exchange Server 2016 database to the Exchange 2019 database.

Get-Mailbox-Database Mailbox2016 | New-MoveRequest-TargetDatabase Mailbox2019

When there are multiple databases, if there are duplicates, clear the task first, and then migrate

Remove-MoveRequest eyou.com/email/****

Understand the status of the mobile request

Now, to understand the status of the mobility request, run the following command

Get-MoveRequest | GET-MoveRequestStatistics

The fifth part

Migrate inbound email flows to Exchange 2019

The migration of the Exchange Server inbound email flow is proportional to your current email flow, which means that the inbound email flow migration will depend on the structure of the current email flow. MX records play a vital role in redirecting Exchange server 2016. MX records are DNS records, where MX stands for "mail exchanger" (Note:-see the link provided for more information on MX record follow-up). The public MX record of the Exchange server is configured to resolve the hostname of one or more IP addresses. These IP addresses are used for on-premises or cloud-based email filters to retrieve e-mail messages and point to Exchange servers. IP can also be resolved to an Exchange 2016 server.

There are two conditions on which inbound e-mail flows can be migrated.

When there is an email filter

When an email filter does not exist

Email filter exists

When an e-mail filter exists in this case, you need to modify the message filter to direct the e-mail message to the new Exchange Server 2019 instead of pointing it to the old server. To do this, we must ensure that the port of your email filter (STMP is 25) is open to the new server (that is, Exchange Server 2019) and sends email

No email filter

When there is no e-mail filter, in this case, we first need to open port 25 of STMP from Internet to Exchange New Server 2019, and then we need to modify the MX record to send e-mail to the Exchange 2019 server. In order for the process to succeed, we must use the public DNS provider to change the MX record.

Migrate outbound email flows to Exchange 2019

The outbound email flow migration settings can depend on the e-mail sent by the current Exchange Server through a smart host, which later transfers the e-mail to the Internet.

Run the following command to better understand the smart host settings (empty, no smart host)

Get-SendConnector | fl Name,SmartHosts,SourceTransportServers,AddressSpaces

The following command informs the smart host whether it exists. In addition, the smart hosts migrated by outbound email flows have two aspects as follows:-

When there is a smart host

When the smart host does not exist

There is a smart host

In this case where the smart host exists, the smart host needs to be modified so that it can send and receive e-mail from the IP of Exchange Server 2016. The transport server on the transport server needs to be modified.

Set-SendConnector "Internet SendConnector"-SourceTransportServers ex2019

Smart host does not exist

In this case, when the smart host does not exist, a reverse DNS record is created, that is, the PTR record of the public IP of the new Exchange server 2016 is required. The public IP of Exchange Server 2016 also needs to be added to the SPF record.

Run the following command at the end of the process to modify the send connector so that the new Exchange Server 2016 sends the email directly to Internet.

Set-SendConnector "to internet"-SourceTransportServers ex2019

Part VI

In this release, we will migrate email relay receive connectors and other applications to Exchange 2019, and we will discuss how to uninstall the old Exchange server later.

Migrate email relay receive connectors and other applications to Exchange Server 2016

Relay emails from any device and application that passes through Exchange Server 2016 must be migrated to the new Exchange Server 2019. To do this, we must create the same receive connectors on Exchange 2019 as Exchange 2016, which are located on Exchange 2016 and later, with similar authentication settings, IP scope, and permission groups.

After creating the new receive connector, we need to modify the settings of the application and device so that they relay e-mail through the Exchange 2019 server. When configuring an application or device to use a DNS name like smtp.www.XYZ.com, we need to change the A record to resolve to the IP of the Exchange 2019 server.

Further steps include the process of deactivating Exchange Server 2016, so make sure that all applications have been migrated to Exchange 2019 before continuing with the deactivation steps.

Uninstall Exchange Server 2016

Before continuing to uninstall Exchange Server Migration 2016, make sure that all running services on the software are stopped. It is recommended that you gradually shut down the service to deactivate the server.

Here are some commands that successfully deleted Exchange 2016

Get-MailboxDatabase

Get-mailbox

Get-exchangeserver

Get-Mailbox-Database Mailbox2016-Archive

Get-Mailbox-AuditLog | Disable-Mailbox

Get-Mailbox-Database Mailbox2016-AuditLog

After all, the service has been stopped without any problems, and to ensure that the Exchange 2016 server has been successfully migrated to the new Exchange 2019 server, follow the steps provided below to uninstall Exchange Server 2016.

To uninstall Exchange Server 2016

After you go to add / remove and click Microsoft Exchange Server 2016, a confirmation window opens with the Yes option selected.

After reading the above, do you have any further understanding of the step-by-step solution for migrating Exchange 2016 to Exchange 2019? If you want to know more knowledge or related content, please follow the industry information channel, thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.