Exchange 2010 OWA Redirects

If you are in the process of migrating from earlier versions of Exchange such as Exchange 2003 to Exchange 2010 or even to Office 365 URL redirects is a very useful setup to allow a single URL to re direct to multiple locations depending on where users are hosted.

To enable the re direction of 2003 OWA on the 2010 Exchange server open PowerShell and run the following command:

Set-OwaVirtualDirectory “OWA (Default Web Site)” -Exchange2003Url

Also depending on customer requirements you can also configure the OWA redirect so all users go to and get re directed accordingly to either or To re direct all the traffic in the 2010 Exchange go to the IIS MMC and set as shown below:

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 of the virtual directories under the Default Web Site. To do this, select each virtual directory individually, and then open the HTTP Redirect property and uncheck 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

If the customer wants to browse, you’ll get an HTTP 403.4 error at this stage. This is because SSL is required at the top-level website. In order to get the redirect working, we need to disable SSL for the toplevel website while leaving it enabled for the relevant child virtual directories.

Select the Default Web Site and open the SSL Settings properties. Uncheck the Require SSL checkbox as shown below:

Like the redirection settings, this change will be inherited down the tree for any virtual directory which does not explicitly set the setting independently. Ensure 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 render Remote PowerShell inoperable!

Once you’ve configured the redirection and SSL settings, open a command prompt and run iisreset.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.