locked
OWA URL Issues RRS feed

  • Question

  • I just added a Exchange 2013 CU1 server to our Exchange 2010 SP3 organization and I'm having some issues with my external OWA URL.

    When I had our OWA FQDN pointed at Exchange 2010 I had setup a redirect so users could type in https://email.outsidedomain.com and it would redirect to https://email.outsidedomain.com/owa.  When I point the same FQDN at the new Exchange 2013 server I noticed that OWA responds to https://email.outsidedomain.com without any additional redirection configuration, but it redirects the URL to https://email.outsidedomain.com/owa/auth/logon.aspx?replaceCurrent=1&url=https%3a%2f%2femail.outsidedomain.com%2f (note the missing owa at the end).  If I log in with an account that still has their mailbox on Exchange 2010 I'm taken to https://email.outsidedomain.com that displays a very broken version of OWA.  If I manually add on the /owa after logging in I get a perfectly functioning Exchange 2010 OWA experience.  Also, if I hit the login page from https://email.outsidedomain.com/owa from the start I'm logged into a functioning OWA.

    What is strange is if I repeat the same experiment from inside the network using the internal server name, it works perfectly.  For example if I hit https://internalserver.insidedomain.local OWA automatically redirects to https://internalserver.insidedomain.local/owa/auth/logon.aspx?replaceCurrent=1&url=https%3a%2f%2finternalserver.insidedomain.local%2fowa (note the OWA at the end).

    Why is /owa not being added on for the external url?  I have the external url set as https://email.outsidedomain.com/owa in the vdir configuration.

    Thursday, April 4, 2013 2:07 AM

All replies