Forum Discussion
Persistence Profile for ActiveSync and AirWatch
- Oct 01, 2014
That's a very old version of the iApp. The problem is that the default source IP persistence is overriding the command to persist on the basic auth header in the iRule.
You could disable strictness and remove the source IP persistence from the VIP, but I recommend upgrading your deployment using the new v1.4.0 template since it has many other fixes. You can get an RC version here: https://devcentral.f5.com/wiki/iApp.Microsoft-Exchange-2010-and-2013-iApp-Template.ashx
Or you can wait until October 6th, when we'll be officially releasing v1.4.0 to downloads.f5.com. If you do decide to go with the RC, you'll still want to get the official version once it's out.
Hi Russell, I assume you are using Exchange 2010 since 2013 doesn't require persistence. Which version of the iApp are you using? It should default to persisting on the basic auth header for ActiveSync, but older versions of the iApp had an issue with connection clumping if you deployed with a fallback persistence profile of source IP (if you deployed RPC MAPI clients at the same time, for example). Can you post the tmsh configuration of your ActiveSync VIP here?
thanks
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com