This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(220.8, 93%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESK%3C/text%3E%3C/svg%3E)
Hello,
We have 4 exchange server 2016 and client connection for https/smtp relay happens via Load balancer. (for ex. connection to 'owa.abc.com'/'autodiscover.abc.com'/'smtp.abc.com' goes to VIP used for exchange 2016 servers)
We have installed 4 exchange servers 2019 (no change with namespace, same URL and certificate is used), we plan to test client connectivity and SMTP relay function.
Our plan is to create new VIP with exchange 2019 as backend servers on LB.
Then test by updating local host file where outlook/owa/smtp server name (owa.abc.com/autodiscover.abc.com) points to new VIP.
Once all tests are successful, update DNS record for 'owa.abc.com'/'autodiscover.abc.com/smtp.abc.com' to point new VIP used for exchange 2019 servers.
Questions -
-Is it proffered way (creating new VIP and server pools) or should we add Exchange 2019 servers to existing server pool along with 2016 servers? This way DNS change is not needed. (If yes, then what are the ways to do all test prior to adding exchange 2019 to existing pool?)
-How to make test for ActiveSync, is there any tool ? (not possible on mobile device to point server connection to private VIP)
Thank you for any feedback/help.
I would add the new 2019 servers to the existing pool and not create a new VIP. Use the same cert names and and add the same cert to the new 2019 servers, they can all seamlessly share the same pool:
to test for activeSync, you could add one 2019 server to the existing pool and then off-hours, disable all the 2016 servers in that pool. Then test using the 2019 server which is the only active server in the pool.
Thank you for reply!
I was just testing Outlook connection by changing host file record to point Exchange 2019 server. (Outlook and Autodiscover url points to one of 2019 server)
Outlook connection is ok.
I moved mailbox from 2016 to 2019 but in Outlook 'connection status' server version still showing '15.1.25.07.35' (which is exchange 2016 version)
Outlook restarted, created a new profile but version number is same in Outlook.
Thank you for any input. .
Ok, it's working now.
I can see correct server version in Outlook connection status.
It took unexpected amount of time.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(284.8, 17%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EYS%3C/text%3E%3C/svg%3E)
Hi @sachin kumar singh ,
Ok, it's working now. I can see correct server version in Outlook connection status.
Great to see that it's working now and thanks for share the update. By the way, if Andy's reply has been helpful, you can click "Accept answer" so that others in the community facing similar issues can easily find the useful information. Thanks!