Forum Discussion
carter91_13591
Nimbostratus
NimbostratusMicrosoft Exchange 2013 iApp - Can't login to OWA or ECP if more than one server is active in pool
I just deployed the latest 2013 iApp for Exchange 2013. We have 5 servers, and the iApp deployment went good and quick. However, we can not log into OWA or the ECP when more than one pool member is active. You get to the login page, you type your username and password and it looks like it's logging you in for a brief moment, then kicks you back to the logon page. If I go into the OWA pool, and disabled all but one of the members, you can log in and access your mailbox or ECP just fine.
Anything you can think of to look at? I have a support case with F5, but sometimes people on here have ran into this before.
destr0yr_22001I was experiencing this issue as well.
My External Domain is foo.com. My internal domain is corp.foo.com. The iApp was used to setup OWA/ECP, etc. for owa.foo.com. A wildcard cert for *.foo.com for Client and Server SSL on the F5 (configured in the iApp). Cert was also imported into exchange and applied to the IIS role for each CAS. I had to set all my Exchange URLs to match "owa.foo.com" using the PowerShell script at http://jaworskiblog.com/2013/04/13/setting-internal-and-external-urls-in-exchange-2013/, running it three times (once for each CAS server).
As soon as this was complete, I could login without issue. No cert errors, no issues.