Welcome to ISAserver.org
Forums |
Register |
Login |
My Profile |
Inbox |
RSS 
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Redirect owa.mydomain.com to owa.mydomain.com/exchange
|
Users viewing this topic:
none
|
Logged in as: Guest
|
Login  | |
|
Redirect owa.mydomain.com to owa.mydomain.com/exchange - 7.Jul.2006 7:38:43 PM
|
|
|
marcus2v
Posts: 78
Joined: 28.Oct.2001
From: Reading, UK
Status: offline
|
Hi,
I've set up publishing rules for Outlook Web Access and RPC/HTTPs using Tom's superb 4 part article. With ISA 2004 I was able to add an extra path to the OWA publishing rule ("/ redirects to /Exchange\*), but this doesn't seem to work with ISA 2006 (just corrupts the configuration until I delete both OWA/RPC publishing rules and associated objects).
How do I set it up so the https://owa.mydomain.com redirects to https://owa.mydomain.com/exchange ?
Thanks
Marcus
|
|
|
|
RE: Redirect owa.mydomain.com to owa.mydomain.com/exchange - 8.Jul.2006 9:49:36 AM
|
|
|
dmatos
Posts: 6
Joined: 17.Oct.2002
From: Portugal
Status: offline
|
Hello Marcus.
I currently use an aspx page on the root to redirect:
1. create a file named redirect.aspx on the root folder for owa.yourdomain.com
2. insert this into the file:
<%@ Page Language="C#" %>
<script runat="server">
private void Page_Load(object sender, System.EventArgs e)
{
if (Request.ServerVariables["HTTP_HOST"] == "owa.yourdomain.com")
Response.Redirect("https://owa.yourdomain.com/exchange/",false);
if (Request.ServerVariables["HTTP_HOST"] == "owa.yourdomain.local")
Response.Redirect("https://owa.yourdomain.com/exchange/",false);
if (Request.ServerVariables["HTTP_HOST"] == "owa")
Response.Redirect("https://owa.yourdomain.com/exchange/",false);
Response.Write(Request.ServerVariables["HTTP_HOST"]);
}
</script>
3. set redirect.aspx as a default document with high priority in IIS
4. notice that I have several redirects. I use this asp.net script to allow the users to type owa, owa.yourdomain.local or owa.yourdomain.com, over http or https. it all redirects correctly to the correct https site.
(you need asp.net enabled on the site. I could have used case-statements, but I was just lazy... it works...)
|
|
|
|
|
RE: Redirect owa.mydomain.com to owa.mydomain.com/exchange - 10.Jul.2006 3:28:51 PM
|
|
|
Chris6
Posts: 7
Joined: 22.Jun.2006
Status: offline
|
I don't know if this is the right way but I just changed the external path for "/exchange" to "/".
|
|
|
|
|
RE: Redirect owa.mydomain.com to owa.mydomain.com/exchange - 24.Aug.2006 5:54:07 PM
|
|
|
jrice
Posts: 12
Joined: 17.Jan.2006
Status: offline
|
Dmatos
How do you have your paths setup? I have the redirects working internally but not externally. I'm assuming it's the "/" to "/exchange\" path that's causing the problem, but I still can't make it work. any suggestions?
The redirect was creating using the MS article on redirecting OWA.
Thanks.
Rice
|
|
|
|
|
RE: Redirect owa.mydomain.com to owa.mydomain.com/exchange - 24.Aug.2006 10:01:32 PM
|
|
|
gja
Posts: 50
Joined: 15.Aug.2006
From: The Netherlands
Status: offline
|
The way I did is by making another rule blocking traffic to http://www.mydomain.nl with as path "/" and redirect all the traffic to http://www.mydomain.nl/exchange.
And this works very good
|
|
|
|
|
RE: Redirect owa.mydomain.com to owa.mydomain.com/exchange - 9.May2007 8:19:36 AM
|
|
|
whooligan
Posts: 5
Joined: 8.May2005
From: NL-UT
Status: offline
|
Hello,
Microsoft has posted a fix for this at http://support.microsoft.com/kb/930415
Regards,
Terence
|
|
|
|
|
RE: Redirect owa.mydomain.com to owa.mydomain.com/exchange - 9.May2007 12:48:37 PM
|
|
|
whooligan
Posts: 5
Joined: 8.May2005
From: NL-UT
Status: offline
|
Hello Thomas,
Yes, Exchange 2007
Regards,
_____________________________
Terence Snijtsheuvel
www.virtuall.nl
|
|
|
|
|
RE: Redirect owa.mydomain.com to owa.mydomain.com/exchange - 10.May2007 11:43:55 AM
|
|
|
tshinder
Posts: 47490
Joined: 10.Jan.2001
From: Texas
Status: offline
|
Hmmm. OK, I'm installing Exchange 2007 now and I'll see what the procedures are. I know there are a LOT of issues with 2007 compared to 2003, so it's going to take a awhile to figure these things out.
Tom
_____________________________
Thomas W Shinder, M.D.
Sr. Consultant/Technical Writer
Prowess Consulting http://www.prowessconsulting.com/
Blog: http://blogs.isaserver.org/shinder/
GET THE NEW ISA 2006 Book!: http://tinyurl.com/2gpoo8
|
|
|
|
|
RE: Redirect owa.mydomain.com to owa.mydomain.com/exchange - 21.May2007 3:41:20 PM
|
|
|
tiggerspr96
Posts: 1
Joined: 21.May2007
Status: offline
|
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.
|
|
|
|
 New Messages |
 No New Messages |
 Hot Topic w/ New Messages |
 Hot Topic w/o New Messages |
 Locked w/ New Messages |
 Locked w/o New Messages |
|
 Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|
Printable Version
