F5 LTM load-balancer considerations during Ex2013 to Ex2019 namespace swing-over

Question

I'd imagine F5 LTM is one of the popular load-balancer commonly used in on-prem Exchange environments.

Has anyone been through a namespace swing-over from Exchange 2013 to Exchange 2019 with F5 LTM?

Based on my search it appears that these are Microsoft's recommendation:

• Gradually introduce Exchange 2019 CAS servers into the existing LB pool
• Gradually remove Exchange 2013 CAS servers from LB pool

Just wondering if anyone has been down this path and have any suggestions or lessons-learned to share?

Thanks

Will

Answer 1

Yep, that is exactly how you do it.
Set the 2019 Virtual dir URLs and autodiscover SCP to the same as the 2013 servers, and apply and enable the same cert for the services.
You can add the 2019 at all once to the pool and enable each in the pool one at time to ensure there are no issues, then disable/remove the 2013 servers as you see fit