IApp does not match microsot recomendation

I've actually discussed this with MSFT on this explicit functionality (unofficial, we'll never admit it but I won the argument). We have to remember what ActiveSync was initially used for; short mobile delivery/submission bursts. Back then, 5 minutes (300 seconds) was the default recommendation for the work load expected of those clients. Even with push functionality introduced later, there was no logical reason a mobile device or any ActiveSync device kept anything open over 5 minutes; Blackberry was an exception with separate policies. ActiveSync was also a rather delicate service that still is susceptible to malicious use when CAS servers (in Exch2010) could drop at only a few thousand problematic connections (the calendar ActiveSync iOS issue comes to mind). So a 5 minute timer back then was a good idea.

Fast forward, MSFT is reusing ActiveSync services as a smaller alternative to old school Mapi/RPC access for clients, but these usually don't conform to mobile functionality; this prompted the change to recommendations to require/request longer open session states. This is partly the reason why when you click RPC we bump the timer up (for single name space at least). 5 minutes is still ok for certain workloads, but so is 30 depending on what types of clients are connecting to ActiveSync.

Given the error message by all means change strict mode and up the timer, remember the iApp is a template with the explicit idea that you may need to make customizations based off your need. In this case, we (F5) didn't update the iApp but mikeshumkus (the guy above) will fix to their current best practice needs. I know you already fixed the issue and Mike will update our guides, but I'd figure I give you the history our iApp and Exchange.

I was asked by another DevCentral member at a recent conference how we setup these iApps... we do work with MSFT constantly, including F5'ers that sit over in Redmond to help certify and validate our products and often these are the little things that even they don't catch when we update our BP to match their BP.

Just an FYI from the former F5 Exchange admin (and Exchange admin of 15+ years)...