So we have an exchange 2010 environment and have recently deployed 2 exchange 2013 servers.  We also have an ADFS3 farm- 2 ADFS servers, and 2 WAP (web proxy) servers.

We have published several exchange 2013 urls successfully via wap- for example, https://email.myschool.edu/owa works great.

However, the redirect from the "friendly" url of https://email.myschool.edu does not work via WAP.

Internally (not accessing via WAP) it works- https://email.myschool.edu redirects to an OWA login page-

https://email.myschool.edu/owa/auth/logon.aspx?replaceCurrent=1&url=https%3a%2f%2femail.myschool.edu%2fowa%2f

Externally (using WAP)- I get a 404. 

Solutions for this?

Hi,

Please do the following steps to have a try:

1. Start IIS Manager.

• 2. Expand the local computer, expand Sites, and then click Default Web Site.

• 3. At the bottom of the Default Web Site Home pane, click Features View if this option isn't already selected.

• 4. In the IIS section, double-click HTTP Redirect.

• 5. Select the Redirect requests to this destination check box.

• 6. Type the absolute path of the /owa virtual directory. For example, type https://mail.contoso.com/owa.

• 7. Under Redirect Behavior, select the Only redirect requests to content in this directory (not subdirectories) check box.

• 8. In the Status code list, click Found (302).

• 9. In the Actions pane, click Apply.

• 10. For the new settings to take effect, open a Command Prompt window, and then type iisreset /noforce to restart IIS.

Regards,

Thanks Winnie, but we have already done this redirect in the exchange 2013 server.  It works fine on site, but the redirect does not work when I access via WAP.