METHOD THREE : IIS redirection

I use Exchange 2010 OWA redirect like most others but I prefer the use htm redirect : http://www.lappari.com/2011/02/redirecting-owa-urls-method-one/

I do this mainly because I cant be bothered (lazy-admin) by teaching everybody the https…/owa link and simple webmail.company.com is easy to remember. I can also use the webmail.company.com for shared server where I have a single server handling email for multiple domains, I just make multiple unique hosts. Clean, easy and every “company” gets their own url to the mail server.

I would still like to share another redirect method I found online that looks promising. I am going to allow myself to cut out some parts of if but you can find the original post here : http://briandesmond.com/blog/redirecting-owa-urls-in-exchange-2010/

Here we go :

………….you need to use the HTTP Redirection feature in IIS, as well as remove the requirement for SSL at the top level Default Web Site object. You have to be careful doing this because when you set settings on the web site, IIS will push them down to any virtual directory below which does not explicitly set that setting itself. To setup the redirect, select the Default Web Site in IIS Manager, and open the HTTP Redirect option under IIS. Complete it like this:

image_thumb

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

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 HTTP 403.4 error. 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:

image_thumb_1

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. 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 Windows Server 2008, they may not be identical.

Skrifaðu nú skemmtilegar og jákvæðar athugasemd

athugasemdir