Forum Discussion

Michael_Koyfman's avatar
Michael_Koyfman
Icon for Cirrocumulus rankCirrocumulus

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.

 

Michael_Koyfman's avatar
Michael_Koyfman
Icon for Cirrocumulus rankCirrocumulus
Oct 03, 2013
Ok, 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.