Forum Discussion
rich1977_120837
Oct 02, 2013Nimbostratus
Issues with Exchange 2013 owa
I've got the Big IP F5 virtual load balancer set up in my exchange 2013 lab getting ready for our migration in a few months and am having an issue. I've got an exchange 2007 environment set up to mi...
Michael_Koyfman
Oct 03, 2013Cirrocumulus
Does it happen only with the migrated accounts? Or does OWA 2013 not work even with the mailbox that was originally created on Exchange 2013? Do you have analytics profile enabled in your deployment by any chance? If yes, I suggest disabling it.
If "native" Exchange 2013 mailbox works with OWA and migrated does not, I suggest opening a support case and providing HTTPwatch dumps of working and non-working logs so that they can be compared in the troubleshooting effort.
- rich1977_120837Oct 03, 2013Nimbostratusneither works, migrated or newly created accounts if I go through the F5, also, unless it is enabled by default I have not enabled any analytics profile
- Michael_KoyfmanOct 03, 2013CirrocumulusOk, how did you setup Exchange? Did you leverage the deployment guide and iApp from here? https://clouddocs.f5.com/api/iapps/Microsoft-Exchange-2010-and-2013-iApp-Template.html I assume you did not try to setup SSL offload, as Exchange 2013 does not support it by default. I am guessing that there could be an issue happening with the SSL re-encryption. If you did not use an iApp, I suggest you set it up using the link provided. If you did set it up with an iApp, then I suggest trying to remove advanced profiles from the OWA Virtual server one by one to see at which point it starts working. By advanced profiles I mean NTLM, OneConnect, HTTP Compression, Web Acceleration, HTTP, and finally SSL. Once you find out which profile is causing the issue, it'll be easier to find a resolution. You should also feel free to open a support case to troubleshoot this.
- rich1977_120837Oct 04, 2013NimbostratusWell, turns out the virtual server for owa was never assigned the owa pool that was created by the iapp. That shouldnt be the case correct? If I deploy an iapp it should assign the pool to the virtual server that it created for it right? Once I assigned the virtual server to the owa pool (my cas servers) everything of course works fine. Thanks for your input michael but I am curious if I will need to assign the pool to the virtual server everytime I create a deployment using an iapp because none of my virtual servers created for exch13 had a pool assign to them.
- RyannnnnnnnnJul 28, 2014AltocumulusI believe the pool selection when using the configuration generated by the Exchange 2013 iApp is performed in the iRules applied to the virtual server. Depending on what options you chose during the initial configuration will determine if you require separate pools for separate exchange services (eg. ActiveSync, OWA, etc). Have you by any chance tried applying a persistence profile?
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