Forum Discussion
ScottB_85935
Jan 23, 2012Nimbostratus
Outlook WEB APP Sessions timing out
Hello,
We have recently migrated to Exchange 2010, and leverage F5 devices in a single virtual Server setup to load balance between our Exchange 2010 CAS front-end servers.
What we are experiencing are that Outlook Web App sessions (Web based mail for Ex2010) are timing out randonly early disconnecting clients. When using OWA one has the option to choose 'public' (15 minute timeout) or 'private' (8 hour timeout), but sometimes randomly users will select 'Private' option and still will be timed out/disconnected in 5 minutes.
Does anyone have any ideas on what might remedy this?
Also, F5 support directed me to the following technote.
http://support.f5.com/kb/en-us/solu...r=18886310
Could this idle timeout setting of 5 minutes be stepping on the 15 minute public, and 8 hour private setting? How do F5 settings work with Exchange Services like OWA that have custom timeout settings?
This is the portion of the irule in which we account for OWA connections that defaulted from the F5/Exchange 2010 single virtual server deployment template.
}
default {
This final section takes all traffic that has not
otherwise been accounted for and sends it to the
pool for Outlook Web App
persist cookie
pool Ex2010_single_owa_pool
If using the Web Accelerator module, uncomment the
following line and change the name to that of
your WA class.
HTTP::class select Ex2010_single_wa_http_class
}
}
}
Thanks in Advance. This has been very frustrating to resolve.
Scott B.
- J_Ford_41146NimbostratusI'm seeing the same issue when moving to the latest version of the Exchange iApp. The newest version fixed an issue I was having with getting Outlook Anywhere to work with Exchange 2010, but inadvertently caused this OWA timeout bug. I ended up rolling back to the previous version of the iApp until this gets sorted out.
- mikeshimkus_111Historic F5 Accounthi Scott/J,
- mikeshimkus_111Historic F5 AccountFYI, you will need to disable strictness on your Exchange iApp before attaching this rule to the virtual server. Once you have disabled strictness, you will need to run this command from the BIG-IP command line:
- J_Ford_41146NimbostratusMike,
- mikeshimkus_111Historic F5 AccountNo problem. Here's an alternate way to do it if that one ends up giving you issues:
- blaksplash_1044NimbostratusHey mikeshimkus,
- mikeshimkus_111Historic F5 AccountI think this is related to a separate issue with the persistence profile not treating the cookie as a session cookie, although that option is checked in the profile settings.
- mikeshimkus_111Historic F5 AccountSorry, the formatting left out some of that command; it should be:
- FernL_29896NimbostratusI had the same issue on our end, OWA disconnects after 5 minutes, when using template f5.microsoft_exchange_2010_cas.2012_04_06 . F5 support recommended downloading and using the latest version of the exchange CAS template, f5.microsoft_exchange_2010_cas.2012_06_08. This template is only available for LTM v12, but F5 support said it's ok to use on v11, which we did.
- Bjarne_10209Nimbostratus
Had the same problem. A OWA session timed out after 180 sec. Doing as described in SOL11679 solved my timeout problem.
http://support.f5.com/kb/en-us/solu...11679.html
Recent Discussions
Related Content
Â
DevCentral Quicklinks
* 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
Discover DevCentral Connects