APM + GTM issue with OWA 2013

Hi,

This is common when using APM and GTM as the GTM could send the session to the wrong APM who doesn't know anything about the original session on the first APM.

Have you seen deployment guide?

https://www.f5.com/pdf/deployment-guides/f5-apm-gtm-dg.pdf

So the recommended way to "pin" the users to one APM is to do a redirect to a subdomain (or different DNS name) and then all request from GTM for that subdomain resolve to the APM intended.

It would work like this. User request app.company.com and then either with iRule or VPE redirect you would send them to dc1.app.company.com which would point to a specific APM and then all future requests should be send to this address instead of app.company.com and there is then no way for the session to be kicked to dc2.app.company.com.

Please let me know if you have any more questions.

-Seth