http://briandesmond.

com/blog/redirecting-owa-urls-in-exchange-2010/ Redirecting OWA URLs in Exchange 2010 One of the things I ve been doing for as long as I can remember is redirecting req uests that don t go to https://owa.customer.com/owa (or /exchange) to the correct URL. So, if someone goes to http://owa.customer.com or https://owa.customer.com, they get redirected to the correct (secure) URL. Historically I ve always done th is with two components: A custom website listening on Port 80 on each CAS server A default.aspx file in the root of the Default Web Site redirecting to /owa This approach no longer works with Exchange 2010 CAS because the PowerShell virt ual directory actually operates over Port 80 (authentication is Kerberized). If you try and tinker with this, you ll start getting errors from Remote PowerShell l ike this: VERBOSE: Connecting to cas01.customer.com [cas01.customer.com] The WinRM service cannot process the request because the r equest needs to be sent to a different machine. Use the redirect information to send the request to a new machine. Redirect location reported: https://owa.cust omer.com/owa/PowerShell. To automatically connect to the redirected URI, verify "MaximumConnectionRedirectionCount" property of session preference variable "PSS essionOption" and use "AllowRedirection" parameter on the cmdlet. + CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:Rem oteRunspace) [], PSRemotingTransportRedirectException + FullyQualifiedErrorId : PSSessionOpenFailed

In order to work around this, you need to use the HTTP Redirection feature in II S (the default.aspx trick mentioned above should work too), as well as remove th e requirement for SSL at the top level Default Web Site object. You have to be c areful doing this because when you set settings on the web site, IIS will push t hem down to any virtual directory below which does not explicitly set that setti ng itself. To setup the redirect, select the Default Web Site in IIS Manager, an d open the HTTP Redirect option under IIS. Complete it like this:

Warning: It s very important that you check the checkboxes exactly as shown in the screenshot above!

Once this step is complete, you need to remove the enforced redirect from each o f the virtual directories under the Default Web Site. To do this, select each vi rtual directory individually, and then open the HTTP Redirect property and unche ck the Redirect requests to this destination checkbox. You ll need to do this on the following virtual directories: aspnet_client Autodiscover ecp EWS Microsoft-Server-ActiveSync OAB PowerShell Rpc

Note: The Exchange, Exchweb, and Public virtual directories should redirect to / owa.

If at this point you simply browse to http://cas01.customer.com, you ll get an HTT P 403.4 error. This is because SSL is required at the top-level website. In orde r to get the redirect working, we need to disable SSL for the toplevel website w hile leaving it enabled for the relevant child virtual directories. Select the Default Web Site and open the SSL Settings properties. Uncheck the Re quire SSL checkbox as shown below:

Like the redirection settings, this change will be inherited down the tree for a ny virtual directory which does not explicitly set the setting independently. En sure that SSL is required for the following virtual directories: Autodiscover ecp EWS Microsoft-Server-ActiveSync OAB owa Rpc Warning: If you require SSL for the PowerShell virtual directory, you will rende r Remote PowerShell inoperable!

Once you ve configured the redirection and SSL settings, open a command prompt and run iisreset. At this point you should be able to browse to http://localhost on the CAS server and get redirected to https://owa.customer.com/owa. These steps were tested on Windows Server 2008 R2. While they should be similar under Window s Server 2008, they may not be identical