KB ID 0001472
Exchange 2019 Migration
If Exchange 2016 was Exchange 2013 in a pretty dress, then with Exchange 2019 it’s simply added a hat. In the past, every third Exchange release was a major rebuild, but Exchange 2016 is simply Exchange version 15.1 (Exchange 2013 was 15.0 and Exchange 2016 is version 15.1).
So the Migration to Exchange 2019 is pretty much the same as it was from 2013 > 2016, or even 2016 > 2016.
- There should be NO Exchange 2010 servers in existence before deploying Exchange 2019. You would need to upgrade to 2013/2016 first.
- There’s no Unified Comms Role with Exchange any more! If you need to upgrade look at Skype for Business 2019.
- Edge Server Role is still supported.
- Windows Server Core (2016) is now supported with Exchange 2019.
- Windows Server 2019 (Standard or Datacenter) are supported host Operating systems.
As with all Exchange migrations make sure your Active Directory Domain/DNS/Existing Exchange organisation is healthy before you start. Then upgrade the existing Exchange to the latest cumulative update.
Exchange 2019 Prerequisites
You will need your Server 2012R2 or Server 2016 server fully updated and added to your domain, then to add the required roles and services use the following Powershell commands for Server 2012, 2016 and 2019;
Server 2016 / 2012 R2
Note: Not Required on Server 2019: You will need to install .Net 4.8 (link), on Server 2016 and 2012.
You need to install the MS Unified Communications API 4.0 (link).
You will also need to install Microsoft Visual C++ (link)
Either download the Exchange 2019 install media, or insert the Exchange 2019 DVD, and launch setup.exe > Next > Next > Files will be copied over.
Don’t I need to extend the schema, forest or domain? The setup does all this for you, you don’t need to do this manually anymore, (yes you can manually do this before installing, if you want to, but unless your schema master is in a different root domain, or you’re not a schema admin, then I don’t see the point!)
Introduction Page > Next > At the EULA tick “I Accept…” > Next > Tick “Use Recommended settings” > Next.
Select ‘Mailbox role’, and ‘Automatically install Windows Server roles and features…” > Next > Select the install directory, Note: In production you probably DON’T want this on the Windows System drive > Next > Unless you have a reason to disable Malware scanning then select ‘No’ > Next.
Readiness Checks > Fix and Errors and heed any warnings > Install > The product will install, this will take a long time!
Finish > Reboot the server.
An there’s our new Exchange 2019 Server.
Exchange 2019 EnterProduct Key
Servers > Servers > Select the 2019 Exchange Server > Enter Product Key > Save
Note: On the pre-release version of Exchange 2019, the Exchange 2016 keys worked fine.
At the warning click OK.
As directed Restart the ‘Microsoft Exchange Information Store’ service.
Transfer Exchange Certificate to Exchange 2019
I’m using a wildcard certificate so I want to export the cert form my Exchange 2016 server and import it onto my new Exchange 2019 Server. You will want to do the same if you have a certificate with your public domain name on it and this will be your ‘internet facing’ Exchange server. Servers > Certificates > Select the Exchange 2016 Server, in the drop down menu > Select The Certificate > Click the ellipses (three dots) > Export Exchange Certificate > Supply a UNC path and password > OK.
Change the Dropdown to the Exchange 2019 Server > Click the ellipsis > Import Exchange Certificate > Supply the UNC path and password you used (above) > Next.
Add in the Exchange 2019 Server > Finish.
Exchange 2019 Assign Services to Certificate
Select the newly imported certificate> Edit > Services > Select the services > Save > Note: Here I’m selecting SMTP and IIS. (You cant use a wildcard cert for IMAP,POP).
Exchange 2019 Rename Mailbox Database
Servers > Databases > Exchange always gives databases annoying names > Select the Database on the 2019 Exchange Server > Edit > Rename it > Save.
Note: The path to the Database retains the original name (we will fix that in the next step).
Exchange 2019 Move Mailbox Database
I’m pretty old school, I like my Exchange databases on their own drive/partition, and I like the logs on another drive/partition. To move both the Database and the Logs;
Add Exchange 2019 to the Send Connector
Mail Flow > Send Connectors > Select your mail SMTP connector(s) > Edit > Scoping > Source Server section > Add > Add in the new server > OK > Save.
Note: The Exchange server will now need to have TCP port 25 (SMTP) open outbound on your corporate firewall.
Hybrid (On-Prem) Exchange Migration Note
If your on-premise Exchange is part of an Office 365 Hybrid deployment you will need to add the new server to the ‘scope’ for that connector also!
Decommission Exchange 2016
From this point forward we are going to start getting rid of our Exchange 2016 server, they can of course coexist, (if you wanted to wait a while).
For that reason I change the ‘mail flow’ on the firewall to point to the new Exchange server at this point, and the HTTP access for OWA, Outlook Anywhere, and Phone/Tablet access
Exchange 2019 Mailbox Migration
Yes you can do this in the EAC, but I prefer to do this in PowerShell. But If I don’t put this here, I’ll get emails! Recipients > Migration > Add > Move to a different Database > Add in the mailboxes/users > Next.
Give the ‘Batch’ a name > Select to move Archive mailboxes (if you have them) > Select the destination (Exchange 2019) Database > Again if using archive mailboxes, select the target archive mailbox database > Set the bad Item limit to 99 > Next > Select Automatically Start > Select Automatically Finish > New.
From this point, this is where I don’t like the EAC it takes AGES to update with progress! From the Exchange Shell you can get an up to date view of that is going on!
For a better list of commands for moving user mailboxes, and monitoring the migration, and removing the move requests when you are finished, see the following article;
Migrating Exchange System Mailboxes
Before you start issue the following command;
In addition to the user mailboxes there are a multitude of different ‘System mailboxes’ that might be hanging around, before we can get rid of the Exchange 2016 Database we need to migrate those.
Firstly AuditLog Mailboxes
If there are any!
Get-Mailbox -AuditLog -Database “Mailbox-Database-2016” | New-MoveRequest -TargetDatabase “Mailbox-Database-2019“
Then Arbitration Mailboxes
If there are any!
Get-Mailbox -AuditLog -Database “Mailbox-Database-2016” -Arbitration | New-MoveRequest -TargetDatabase “Mailbox-Database-2019“
Then Monitoring Mailboxes
If there are any!
Get-Mailbox -Monitoring -Server “Mail-2016” | New-MoveRequest -TargetDatabase “Mailbox-Database-2019“
Make sure there are no archive mailboxes;
If there are, move them, (as above.)
Also move any Discovery mailboxes, and move them to 2019;
Migrating Public Folders
Remember after Exchange 2013 these are just mailboxes! you can move them like any other mailbox 🙂
Delete Exchange 2016 Database(s)
When you are 100% sure theres nothing left on the old database(s) remove them;
Uninstall Exchange 2016
Your install directory may not be on the C: drive so change your path accordingly;
At this point make sure your backup/replication software is pointed to the new Exchange 2019 Server.
Note: If you are running an On-Premise Exchange in Hybrid mode, and post migration if you have any mail flow problems see the following article;
Related Articles, References, Credits, or External Links