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_Koyfma1
Cirrus
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_120837
Oct 04, 2013Nimbostratus
Well, 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.
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