26 August 2010

IIS and TMG default site redirection

I have just finished publishing Remote Desktop Services Web Access.  as part of "finishing it off" I like to make sure that there a redirects in place.

We want to make sure that users don't end up on this page:

First up we are going to tackle the internal.  This is quite simple.

We open up the IIS management console. On the default site we open up HTTP redirect.

  • Check "Redirect request to this destination"

  • In the RDSGW case I simply added "/rdweb/"

  • But the rest is pretty self explanatory

That's it - done - no custom pages or scripts  - just that.

Next We have to do a redirect for the External users coming in from the Internet.

I am going to do the redirect on the TMG server.

  • First I create a listener that listens on the correct external IP address.

  • I select HTTP as the traffic type

  • Then I create a rule with the action as Deny

  • Then I specify the redirect


Also pretty simple.

The result is that people will never end up on the IIS start screen.  You application and work will look professional.  Makes me wonder why everyone does not do this....


One IT - NZ Cloud Hosting Provider said...

How would I do this without the TMG. I had a server setup RDWEB and I would like that when a user types remote.domain.com it takes them straight to the RDWEB page. Preferably not changing the url, would this be possible with a ModRewrite rule?

Etienne Liebetrau said...

Just finished an article on how to do that!


Anonymous said...

When I did this, i get Error 310 (net::ERR_TOO_MANY_REDIRECTS): There were too many redirects.

Still looking for a resolution to this.

Etienne Liebetrau said...

If you are getting too many redirect you are probably getting stuck in a loop. The best is to use a http sniffer like the internet explorer dev tools or firebug to see what is going on.

This will give you a good place to start from.

Post a Comment