Forum Discussion
Upgrade Exchange Server 2016 DAG to 2019
Yes, a dag is a replication boundary and moving mailboxes to 2019 dag is no different than moving mailboxes from exchange server to exchange server. It can share the same name space as your 2016 dag and you are correct, you would add the 2019 nodes to the load balancer when you are comfortable. What I would do is go through the 2016 virtual directory settings and mirror them on the 2019 servers. Make sure you have any certificates installed on the 2019 server. You'll have to update your send connectors to include your 2019 servers as necessary and mirror the 2016 receive connectors and their settings on your 2019 servers.
Yes, a dag is a replication boundary and moving mailboxes to 2019 dag is no different than moving mailboxes from exchange server to exchange server. It can share the same name space as your 2016 dag and you are correct, you would add the 2019 nodes to the load balancer when you are comfortable. What I would do is go through the 2016 virtual directory settings and mirror them on the 2019 servers. Make sure you have any certificates installed on the 2019 server. You'll have to update your send connectors to include your 2019 servers as necessary and mirror the 2016 receive connectors and their settings on your 2019 servers.
Michael_Larrivee, thank you. Makes perfect sense. Just wish I could have found some documentation that explicitly noted "these steps also work with a DAG" and "a load balanced namespace" so I could assuage concerns from the change advisory board.