|
tiggerspr96 -> RE: Redirect owa.mydomain.com to owa.mydomain.com/exchange (21.May2007 3:41:20 PM)
|
Ok here's how I have configured Redirection to work in ISA 2006:
Configure a new web publishing rule using the wizard
Name the rule if you like "Exchange Redirection", click next
In the "Select Rule Action" window chose "deny", click next
In the "Publishing Type" window choose the publishing scenario that best fits your ISA 2006 implementation. In my case the default "Publish a single web site or load balancer" was choosen since external GSLB's are being used for load balancing and fault tolerance, click next
In the "Server Connection Security" window choose the level of security that best fits your implementation. In my case the default "Use SSL to connect to the published Web Server or server farm" was choosen since I am using certificates to deploy SSL, click next
In the "Internal Publishing Details" (part 1) window enter the name of the CAS server and/or it's FQDN as configured in your internal DNS. You can also enter the CAS server's IP address in case your ISA server cannot resolve the computer name or FQDN. In my case internal GSLB's are being used to provide a FQDN that will resolves to all the CAS servers in my environment for load balancing and fault tolerance, click next
In the "Internal Publishing Details" (part 2) window enter the path for the folder to be published which is, "exchange" (no quotes), click next
In the "Public Name Details" windows enter the public name or FQDN that your users will use to get to OWA. For example, webmail.yourcompanyname.com. Note: your certificate installed on ISA that your weblistener is configured for must have the exact FQDN or redirection will not work, click next
In the "Select Web Listener" window, select the same weblistener from the menu drop down that you used for accessing OWA using "webmail.yourcompanyname.com/owa", click next
In the "Authentication Delagation" window, select from the menu drop down, Basic Authentication Note: This option should be used stricly with having implemented SSL inconjunction. This method of authentication sends user's credentials in clear text, click next
In the "User Sets" window, accept the default for All Authenticated Users unless your needs demand other wise, click next
You will now be told that the wizard is complete and click finish
Now goto the newly created web access rule you have created and make sure that rule is just above the Exchange Published Rule for access to OWA. If it is not move the rule to the proper location by right clicking on the rule and moving the rule up or down as needed.
Once the rule is in the proper location right click on the rule again and choose properties. Then choose the "Action" tab and click the check box for "Redirect HTTP requests to this Web Page" and type in the box below the external FQDN of your OWA website with the following path afterwards, "webmail.yourcompanyname.com/exchange" (no quotes)
Then choose the "Paths" tab and click to highlight the default exchange path and click on the "edit" button on the right. In the "Path Mapping" window enter "/*" (no quotes) where the "Specify the folder on this Web Site that you want to publish. To publish the entire Web site, leave this field blank". Then in the "External Path" field make sure the "The following folder" option is selected and enter "/" (no quotes) in the field just below and click "ok"
The chose the "Application Settings" tab and click to choose "Use customized HTML forms instead of the default" and in the field below "Type the custom HTML form set directory (must exist on all array members):" enter "Exchange" (no quotes), then click "ok"
Finally, do not forget to click "Apply" and not "Discard" above the Firewall Polcy tab and you should not successfully have redirection configured. Note: do not forget the flush the DNS cache on your client side machines in case they have been resolving to the improper page prior to implementing this new web publishing rule.
|
|
|
|