Thoughts from the EPS Windows Server Performance Team
Hi, my name is Mark Ghazai and I am a Support Escalation Engineer on the Performance team. Today, we’re going to discuss how to modify the Remote Desktop option on the Windows Server 2008 TS Web Access page. This has been a fairly common question over the last few months. In particular, many of our customers have asked how they can force connections through the TS Gateway. Contrary to popular belief, making this configuration change is not as difficult as you might have thought …
Here’s the screen shot of Remote Desktop Option under TS Web Access page – if you’ve been using Windows Server 2008 TS Web Access, you are already familiar with this page:
In the TechNet article listed at the end of this post, there are instructions on how to specify the TSGateway for this Remote Desktop Connection (see the screen shot below):
Observing the TS Web Access behavior, you can see that IIS ASP application automatically detects if the user is on the local or external network. If the user is on the local network, the web application will bypass the TSGateway by default. But, what if you want to route all Remote Desktop connections using this option through your TSGateway server regardless of location? With a fairly simple page modification, this can be done;
And that brings us to the end of our post. Hopefully this helps answer some of your questions in this regard. Until next time …
- Mark Ghazai
where can i get help to fix my media player
Made the changes you suggested as we are experiencing the same thing, but i now just get a repeating login box ....
Any ideas ?
This worked perfect for me, thanks! This allows me to install the Web Access and TS Gateway on the same server and be able to use the Web Access over the internet to access my Terminal Servers on a private network. This also works for Server 2012 but the file path to the Desktops.aspx is slightly different.
I also had to configure the Remote Desktop Web Connection behavior:
Great work. Thanks again!