• RSS
  • Twitter
  • FaceBook

Welcome to ISAserver.org

Forums | Register | Login | My Profile | Inbox | RSS RSS icon | 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
  Printable Version
All Forums >> [ISA 2006 General] >> General >> Redirect owa.mydomain.com to owa.mydomain.com/exchange Page: [1] 2   next >   >>
Login
Message << Older Topic   Newer Topic >>
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
Post #: 1
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...)

(in reply to marcus2v)
Post #: 2
RE: Redirect owa.mydomain.com to owa.mydomain.com/exchange - 9.Jul.2006 6:25:58 PM   
tshinder

 

Posts: 50013
Joined: 10.Jan.2001
From: Texas
Status: offline
Hi Dmatos,

Thanks!
Tom

_____________________________

Thomas W Shinder, M.D.

(in reply to dmatos)
Post #: 3
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 "/".

(in reply to tshinder)
Post #: 4
RE: Redirect owa.mydomain.com to owa.mydomain.com/exchange - 10.Jul.2006 4:12:44 PM   
tshinder

 

Posts: 50013
Joined: 10.Jan.2001
From: Texas
Status: offline
Hi Chris,

That's interesting, because I would think that would not work. If someone enters www.domain.com/exchange then they would be redirected to www.domain.com/  which would take them away from /exchange

Tom

_____________________________

Thomas W Shinder, M.D.

(in reply to Chris6)
Post #: 5
RE: Redirect owa.mydomain.com to owa.mydomain.com/exchange - 24.Aug.2006 5:54:07 PM   
jrice

 

Posts: 13
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

(in reply to dmatos)
Post #: 6
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

(in reply to jrice)
Post #: 7
RE: Redirect owa.mydomain.com to owa.mydomain.com/exchange - 24.Aug.2006 10:56:30 PM   
tshinder

 

Posts: 50013
Joined: 10.Jan.2001
From: Texas
Status: offline
Hi G,

That's a very nice tip!
Thanks!
Tom

_____________________________

Thomas W Shinder, M.D.

(in reply to gja)
Post #: 8
RE: Redirect owa.mydomain.com to owa.mydomain.com/exchange - 9.May2007 8:19:36 AM   
whooligan

 

Posts: 7
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

(in reply to marcus2v)
Post #: 9
RE: Redirect owa.mydomain.com to owa.mydomain.com/exchange - 9.May2007 8:51:55 AM   
tshinder

 

Posts: 50013
Joined: 10.Jan.2001
From: Texas
Status: offline
Hi Wholigan,

Thanks!
Tom

_____________________________

Thomas W Shinder, M.D.

(in reply to whooligan)
Post #: 10
RE: Redirect owa.mydomain.com to owa.mydomain.com/exchange - 9.May2007 10:31:03 AM   
whooligan

 

Posts: 7
Joined: 8.May2005
From: NL-UT
Status: offline
Hello Thomas,

Problem we run into is that the redirection still doesn't work.
When typing /owa we get the login page of OWA, but without we get the forms based login from ISA.
When using the latter and logging it we see it loading some things from /8.0.685.24/scripts/premium/ and /8.0.685.24/themes/base/
the outcome is as in the picture below:


Any ideas?

Kind regards,
Terence

(in reply to tshinder)
Post #: 11
RE: Redirect owa.mydomain.com to owa.mydomain.com/exchange - 9.May2007 11:30:10 AM   
tshinder

 

Posts: 50013
Joined: 10.Jan.2001
From: Texas
Status: offline
Is this Exchange 2007? If so, I can't help as I'm boycotting it until they come up with a useable User Interface

Tom

_____________________________

Thomas W Shinder, M.D.

(in reply to whooligan)
Post #: 12
RE: Redirect owa.mydomain.com to owa.mydomain.com/exchange - 9.May2007 12:48:37 PM   
whooligan

 

Posts: 7
Joined: 8.May2005
From: NL-UT
Status: offline
Hello Thomas,

Yes, Exchange 2007

Regards,

_____________________________

Terence Snijtsheuvel
www.virtuall.nl

(in reply to tshinder)
Post #: 13
RE: Redirect owa.mydomain.com to owa.mydomain.com/exchange - 10.May2007 11:43:55 AM   
tshinder

 

Posts: 50013
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.

(in reply to whooligan)
Post #: 14
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.

(in reply to marcus2v)
Post #: 15
RE: Redirect owa.mydomain.com to owa.mydomain.com/exchange - 22.May2007 8:50:43 AM   
tshinder

 

Posts: 50013
Joined: 10.Jan.2001
From: Texas
Status: offline
Hi Tigger,

Thanks!
Tom

_____________________________

Thomas W Shinder, M.D.

(in reply to tiggerspr96)
Post #: 16
RE: Redirect owa.mydomain.com to owa.mydomain.com/exchange - 23.Mar.2009 2:39:19 PM   
chetton2000

 

Posts: 34
Joined: 12.Apr.2007
Status: offline
Dmatos,

I know this is old, but bear with me as my redirector recently stopped working and it has been 2 years since I set it up so I can't even remember how I set it up.  When you say you have this set up on the root folder, I assume you mean the exchange server itself?  Is this safe?  Does this give direct HTTP access to the exchange server without providing the ISA security?  Anyone else, please provide info as well.  Thanks.

quote:

ORIGINAL: dmatos

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...)

(in reply to dmatos)
Post #: 17
RE: Redirect owa.mydomain.com to owa.mydomain.com/exchange - 23.Mar.2009 7:15:12 PM   
Jason Jones

 

Posts: 4663
Joined: 30.Jul.2002
From: United Kingdom
Status: offline
quote:

ORIGINAL: chetton2000

Dmatos,

I know this is old, but bear with me as my redirector recently stopped working and it has been 2 years since I set it up so I can't even remember how I set it up.  When you say you have this set up on the root folder, I assume you mean the exchange server itself?  Is this safe?  Does this give direct HTTP access to the exchange server without providing the ISA security?  Anyone else, please provide info as well.  Thanks.

quote:

ORIGINAL: dmatos

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...)



Yeah, this is bad practice as it allows anonymous access to your Exchange server - not good!

_____________________________

Jason Jones | Forefront MVP | Silversands Ltd
My Blogs: http://blog.msedge.org.uk/ and http://blog.msfirewall.org.uk/

(in reply to chetton2000)
Post #: 18
RE: Redirect owa.mydomain.com to owa.mydomain.com/exchange - 24.Mar.2009 8:35:46 AM   
tshinder

 

Posts: 50013
Joined: 10.Jan.2001
From: Texas
Status: offline
No need to do that now -- just create a deny rule and then redirect.

HTH,
Tom

_____________________________

Thomas W Shinder, M.D.

(in reply to Jason Jones)
Post #: 19
RE: Redirect owa.mydomain.com to owa.mydomain.com/exchange - 2.Apr.2009 5:07:59 PM   
chetton2000

 

Posts: 34
Joined: 12.Apr.2007
Status: offline
quote:

ORIGINAL: tshinder

No need to do that now -- just create a deny rule and then redirect.

HTH,
Tom


Tom, can you clarify what you mean on this?  Thanks.

(in reply to tshinder)
Post #: 20

Page:   [1] 2   next >   >> << Older Topic    Newer Topic >>
All Forums >> [ISA 2006 General] >> General >> Redirect owa.mydomain.com to owa.mydomain.com/exchange Page: [1] 2   next >   >>
Jump to:

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