Forum Discussion
7 Replies
- swo0sh_gt_13163Altostratus
I always experience the same issue when I deploy ASM for OWA 2010 / 2013. Especially for Active-sync.
Anyone has observed the same as a common issue?
- swo0sh_gt_13163Altostratus
It is in-house developed ASM template. And is being used for the general web application, including OWA. Your comment looks quite promising, i.e. "active-sync is a weird kind of traffic which isn't fully HTTP, from a recent case F5 support advised us to ignore everything that goes over the /active-sync URI and has the Content-Type: application/vnd.ms-sync.wbxml header"
I will try this out and let you know. Thanks a bunch!!!
was that in-house template build for OWA or general?
active-sync is a weird kind of traffic which isn't fully HTTP, from a recent case F5 support advised us to ignore everything that goes over the /active-sync URI and has the Content-Type: application/vnd.ms-sync.wbxml header
- swo0sh_gt_13163Altostratus
I have tried with "Rapid Policy deployment" and one in-house developed ASM template. Result was same for both of the deployments.
this F5 employee setup some nice templates, among others for exchange + active sync
https://devcentral.f5.com/d/new-asm-templates
- Chris_GrantEmployee
You will want to read through the deployment guide here:
https://www.f5.com/pdf/deployment-guides/microsoft-exchange-iapp-dg.pdf
The guide mentions activesync, but doesn't go into detail. Note that it does have links to understand Exchange in the same. You will probably have specific questions. Feel free to ask.