Forum Discussion
Hello again, Hamish-
I have confirmed that the _sys_APM_activesync iRule should never been assigned, even when deploying ActiveSync on its own virtual server (which you aren't doing anyway). We're updating the Deployment Guide to reflect that and should have an update posted this afternoon.
We will have a more-complete overhaul of the Deployment Guide manual configuration section in the next week or two, with an eye towards making it easier to step through.
The iApp (version 1.2) already does the right thing on a single virtual server, and also always does the right thing when using BIG-IP 11.4 and higher, but on BIG-IP versions 11.0-11.3 incorrectly assigns the _sys_APM_activesync iRule to the ActiveSync virtual server [and only that one] when separate IP addresses are chosen for each virtual server. We have an internal bug filed against the iApp to correct the behavior in the next release.
The Deployment Guide contradicts the behavior of the iApp. As of this afternoon's update, the DG will have information consistent with what the iApp does, and a suggestion for a workaround for those using the iApp in the specific affected versions and deployment scenarios.
Again, I'd like to apologize for the trouble this has caused you. Please do let us know how version 1.2 of the iApp works for you. Given your scenario, I believe it will do the right thing.