Share via

Exchange 2016 to 2019 Migration

DG1212-6330 20 Reputation points
2023-04-17T15:55:06.4466667+00:00

I'm in the process of standing up Exchange 2019 servers in order to migrate off of Exchange 2016. I'm just trying to nail down the required steps to ensure that users don't connect to Exchange 2019 before the servers are fully configured and operational as I've seen clients in the past auto connect and get presented with certificate prompts.

  1. Install Exchange 2019.
  2. Set-ClientAccessService -AutoDiscoverServiceInternalUri https://Exchange2019Srv/Autodiscover/Autodiscover.xml
  3. Import existing Exchange 2016 certificate on 2019 servers.
  4. Configure all Virtual Directories to mirror Exchange 2016.
  5. Create databases and DAGs.
  6. Add Exchange 2019 to send connectors.
  7. Lastly, add DNS records for the Exchange 2019 servers for autodiscover.

Following these steps, I shouldn't have clients connect to Exchange 2019 before step 7, correct?

Exchange Server
Exchange Server
A family of Microsoft client/server messaging and collaboration software.
1,197 questions
Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,503 questions
Accepted answer
  1. Jarvis Sun-MSFT 10,186 Reputation points Microsoft Vendor
    2023-04-18T08:25:38.64+00:00

    Hi @DG1212-6330

    Following these steps, I shouldn't have clients connect to Exchange 2019 before step 7, correct?

    Theoretically this can work, but I’ve also seen cases that clients could still connect to the new server unexpectedly. So to be on a safe side, it is recommended to put the Exchange Server 2019 in maintenance mode before the servers are fully configured.

    Please can refer to: Put Exchange Server in maintenance mode

    Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".  Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Amit Singh 4,956 Reputation points
    2023-04-18T09:38:41.9066667+00:00

    Use https://setup.microsoft.com/; you will find the detailed step.  Very clear step-by-step. I would move mailboxes at any time since 2016 can proxy to 2019; however, after step 5 makes sense for the bulk moves.  You must ensure the client URLs and certificates on the 2019 servers match 2016, move mailboxes, and remove the send connector on the 2016 side. Ensure the 2019 servers have the necessary firewall ports open to external (25. 443) and that DNS records are also updated. For deciding best migration path - https://www.infosecurity-magazine.com/blogs/best-migration-exchange-office-365/ Please Note: Since the web sites are not hosted by Microsoft, the links may change without notice. Microsoft does not guarantee the accuracy of this information.

    0 comments