Exchange OWA ActiveSync Outlook Anywhere with F5

Exchange is, unfortunately, a very complex application, so you'll need to pour a cup (or 10) of coffee and consume as much as you can about the deployment options. Thankfully the Exchange iApp goes A LONG WAY towards simplifying that process as possible. The document you reference is the guide that talks about what the iApp is doing and what is required to use it. Actual iApp execution is surprisingly very fast. It'll create multiple VIPs on different ports for OWA, OA, auto discovery, and optionally ActiveSync. I highly recommend this approach.

Hi Joe, one of the co-authors of the guide here. It can be rather dry, especially if you try to read the entire thing at once. The inline help in the iApp contains the most important points about deploying; you can use the guide as reference if you need more info.

We welcome any input about how we can make the guides better. If you can think of any specific suggestions or changes that would help, let us know.

thanks

Mike

Hi Joe, from an F5 customer point of view, we deployed the Exchange iApp to load balance our Exchange 2010 services recently, and what Mike and Kevin above say is 100% on track.

The iApp's 'inline help' (you are prompted for answers to key questions which help build your configuration) is more than enough to get you going. I'd recommend setting up a Proof Of Concept environment using the iApp, and then run exhaustive testing through it. Set up your POC with a new front end IP for your Exchange services, and then when it comes time to switch over, all you need to do is change your DNS records.

A one IP front end configuration works good enough for a medium sized site, but that ends up being a virtual server for each Exchange service. an iRule attached to that VS takes care of applying the right persistence setting, and assigning traffic to pools, which are separated out into services.

There are some caveats and subtle adjustments you might need to make to the configuration that the iApp builds for you though, and the deployment guides covers them off rather nicely. It might look like a lot of information, but do read it, it's worth it.

Bottom line though, the iApp is the way forward. Works like a charm :)

If you have any questions once you have a POC up and running, feel free to post them here and I'll answer if I can.

Cheers,

Gavin