Comments on: Clever Way to Redirect OWA Users Who Can’t Remember to Include /Exchange in the Path http://blogs.isaserver.org/shinder/2006/09/12/clever-way-to-redirect-owa-users-who-cant-remember-to-include-exchange-in-the-path/ Written by Dr Thomas W Shinder, consultant to Microsoft, HP and many Fortune 500 companies on ISA firewall and Web proxy deployments this blog is where administrators get information about ISA Server Universal Threat Management firewalls. Topics include how to manage, deploy, and troubleshoot ISA Server as a network firewall, Web proxy/Web cache, remote access VPN server and VPN gateway to provide a high level of network security for all corporate computers. Thu, 4 Dec 2008 21:14:33 +0000 http://wordpress.org/?v=MU by: Thomas Shinder http://blogs.isaserver.org/shinder/2006/09/12/clever-way-to-redirect-owa-users-who-cant-remember-to-include-exchange-in-the-path/#comment-204720 Sat, 23 Aug 2008 13:04:26 +0000 http://blogs.isaserver.org/shinder/2006/09/12/clever-way-to-redirect-owa-users-who-cant-remember-to-include-exchange-in-the-path/#comment-204720 Hi Rick, You bet! Glad to help. Thanks! Tom Hi Rick,
You bet! Glad to help.
Thanks!
Tom

]]> by: Rick Lim http://blogs.isaserver.org/shinder/2006/09/12/clever-way-to-redirect-owa-users-who-cant-remember-to-include-exchange-in-the-path/#comment-204719 Sat, 23 Aug 2008 13:02:56 +0000 http://blogs.isaserver.org/shinder/2006/09/12/clever-way-to-redirect-owa-users-who-cant-remember-to-include-exchange-in-the-path/#comment-204719 Thanks for this tutorial. I had been wondering how to do that until i read this. Thanks for this tutorial. I had been wondering how to do that until i read this.

]]> by: Marty http://blogs.isaserver.org/shinder/2006/09/12/clever-way-to-redirect-owa-users-who-cant-remember-to-include-exchange-in-the-path/#comment-159642 Tue, 12 Feb 2008 22:51:48 +0000 http://blogs.isaserver.org/shinder/2006/09/12/clever-way-to-redirect-owa-users-who-cant-remember-to-include-exchange-in-the-path/#comment-159642 The redirect works just fine if I publish OWA and have the DENY right after it. However, I also want to publish Outlook Anywhere and Exchange ActiveSync If I put the redirect after the anywhere and activesync rules then they work fine but the redirect doesn't seem to work at all. If I put the redirect before the outlook anywhere and activesync rules then the redirection works great but outlook anywhere and activesync don't work. How do I redirect HTTP://owa.mydomain.com to HTTPS://owa.mydomain.com/exchange AND publish all three CAS access methods (OWA, RPC over HTTP, and Activesync) The redirect works just fine if I publish OWA and have the DENY right after it. However, I also want to publish Outlook Anywhere and Exchange ActiveSync

If I put the redirect after the anywhere and activesync rules then they work fine but the redirect doesn’t seem to work at all.

If I put the redirect before the outlook anywhere and activesync rules then the redirection works great but outlook anywhere and activesync don’t work.

How do I redirect HTTP://owa.mydomain.com to HTTPS://owa.mydomain.com/exchange AND publish all three CAS access methods (OWA, RPC over HTTP, and Activesync)

]]> by: Blog du Tristank : ISA Server 2006 - URL Redirection Made Easy http://blogs.isaserver.org/shinder/2006/09/12/clever-way-to-redirect-owa-users-who-cant-remember-to-include-exchange-in-the-path/#comment-15431 Thu, 26 Oct 2006 04:50:26 +0000 http://blogs.isaserver.org/shinder/2006/09/12/clever-way-to-redirect-owa-users-who-cant-remember-to-include-exchange-in-the-path/#comment-15431 [...] http://blogs.isaserver.org/shinder/2006/09/12/clev... Filed under: IT Pro / Sysadmin, ISA Server, Networking [...] […] http://blogs.isaserver.org/shinder/2006/09/12/clev...#8230; Filed under: IT Pro / Sysadmin, ISA Server, Networking […]

]]> by: Gerhard http://blogs.isaserver.org/shinder/2006/09/12/clever-way-to-redirect-owa-users-who-cant-remember-to-include-exchange-in-the-path/#comment-12217 Thu, 21 Sep 2006 08:25:00 +0000 http://blogs.isaserver.org/shinder/2006/09/12/clever-way-to-redirect-owa-users-who-cant-remember-to-include-exchange-in-the-path/#comment-12217 Thanks a lot. I got it to work after reading the instructions very carefully. Thanks again. Thanks a lot. I got it to work after reading the instructions very carefully.

Thanks again.

]]> by: Philip Colmer http://blogs.isaserver.org/shinder/2006/09/12/clever-way-to-redirect-owa-users-who-cant-remember-to-include-exchange-in-the-path/#comment-11624 Fri, 15 Sep 2006 13:48:49 +0000 http://blogs.isaserver.org/shinder/2006/09/12/clever-way-to-redirect-owa-users-who-cant-remember-to-include-exchange-in-the-path/#comment-11624 I'm having trouble getting the steps right for this. Does the original article on the forum provide more detail or can an article with more detail please be written? Thanks. --Philip I’m having trouble getting the steps right for this. Does the original article on the forum provide more detail or can an article with more detail please be written?

Thanks.

–Philip

]]> by: Rod Payne http://blogs.isaserver.org/shinder/2006/09/12/clever-way-to-redirect-owa-users-who-cant-remember-to-include-exchange-in-the-path/#comment-11505 Thu, 14 Sep 2006 21:49:40 +0000 http://blogs.isaserver.org/shinder/2006/09/12/clever-way-to-redirect-owa-users-who-cant-remember-to-include-exchange-in-the-path/#comment-11505 This is excellent... just what I was looking for to make redirection work when moving from ISA 2004 to ISA 2006. I had been doing redirection in 2004 by adding a path with external="/" and internal="/exchange\". After the upgrade to 2006, OWA would get "The page cannnot be displayed" with "Error Code: 500 Internal Server Error. An internal error occurred. (1359)" Removing the extra path got rid of the error and adding this Deny rule took care of the redirection. On the Deny rule it looks like I also had to go into the properties and change the internal path from "/*" to "/", otherwise it redirected over and over. For FBA, the one complication was that I had to change Users on the Deny rule to All Users and ignore the non-authentication popup. This is excellent… just what I was looking for to make redirection work when moving from ISA 2004 to ISA 2006.

I had been doing redirection in 2004 by adding a path with external=”/” and internal=”/exchange\”. After the upgrade to 2006, OWA would get “The page cannnot be displayed” with “Error Code: 500 Internal Server Error. An internal error occurred. (1359)” Removing the extra path got rid of the error and adding this Deny rule took care of the redirection.

On the Deny rule it looks like I also had to go into the properties and change the internal path from “/*” to “/”, otherwise it redirected over and over.

For FBA, the one complication was that I had to change Users on the Deny rule to All Users and ignore the non-authentication popup.

]]>