Mar 27, 2026 - For details about updated CVE-2025-53521 (BIG-IP APM vulnerability), refer to K000156741.

Forum Discussion

Aviv's avatar
Aviv
Icon for Cirrus rankCirrus
May 08, 2017

External Access to Exchange 2016 while migrating from 2010 APM LTM

Hi! I have exchange 2010 that is behind f5 bigip ltm and apm for external access.   lately I have installed exchange 2016 . move all the mailboxes to the new server will take some time. when i wll...
application delivery
BIG-IP Access Policy Manager (APM)
LTM
Chase_Abbott's avatar
Chase_Abbott
Icon for Admin rankAdmin
May 08, 2017

When you install Exchange 2016 next to 2010, after configuration, you'll actually swing the namespace over to 2016. 2016 is able to proxy 2010 requests but it's better to bring up Exchange 2016 on it's own virtual IP, especially if you're using the iApp to configure the services (the two are very different).

 

When you're assured your new APM/LTM config is working for the new VIP only then would you swing DNS over to the new name.

 

Check out the Exchange 2016 Rapid Deployment Guide and then test the configuration on a new VIP and APM policy in a staging environment before doing anything to production.