Client Requirements for TS Web Access in Windows Server 2008 Release Candidate (RC0)

Client Requirements for TS Web Access in Windows Server 2008 Release Candidate (RC0)

Starting with the RC0 release of Windows Server 2008, Terminal Services Web Access (TS Web Access) requires the most recent update to the Remote Desktop Connection (RDC) client software. This updated version is available in the beta versions of Windows Vista Service Pack 1 (SP1) and Windows XP Service Pack 3 (SP3).

If you are taking part in a Microsoft Connect Beta program, you can download the beta versions of Windows Vista SP1 or Windows XP SP3 from the program Web page.

If you are not an administrator, and you are using TS Web Access at your workplace, contact your system administrator to determine whether your workplace is participating in a Microsoft Beta program. If it is a participant, your system administrator can help you to obtain the updated RDC client software.

Information for Administrators

When a user who has an older version of the RDC client tries to use TS Web Access, they receive an error message with a URL that points them to more information. The target URL of the link currently points to this article. You can modify the target URL by using an ASP.NET application setting. To modify the target URL, follow these steps:

Note To complete this procedure, you must be an administrator of the TS Web Access Web site.

  1. Open IIS Manager on the server that hosts the TS Web Access Web site. To do this, click Start, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
  2. In the navigation pane of IIS Manager, expand the server name, expand Sites, expand Default Web Site, and then click TS. (By default, TS Web Access is installed to this location. If you installed TS Web Access to a different site, locate and then click the site name.)
  3. Under ASP.NET, double-click Application Settings.
  4. In the Actions pane, click Add.
  5. In the Add Application Setting dialog box, do the following:
    • a. In the Name box, type rdcInstallUrl.
    • b. In the Value box, enter the target URL for the link.

Note   To restore the link to point to the default URL, right-click the rdcInstallUrl application setting, and then click Remove.

Alternatively, you can use a text editor, such as Notepad, to directly modify the Web.config file for the TS Web Access Web site. By default, the path of the configuration file is %windir%\Web\ts\Web.config. To do this, under the <appSettings> section of the file, add an entry that is similar to the following, where URL is the target URL for the link:

<add key="rdcInstallUrl" value="http://URL" />

Additional Information

For more information about TS Web Access and about other Terminal Services features, see the Windows Server 2008 Terminal Services TechCenter or the TS Team Blog.

Thank you for using the pre-release version of TS Web Access.

Terminal Services Team

Leave a Comment
  • Please add 8 and 3 and type the answer here:
  • Post
  • So, this is the official Microsoft Sidetrack for people testing out the new TS functionality in Windows 2008 (RC*)?

    Reading this blog i see a lot of users asking for the RDP client software and no one answering any of these questions. I had my hopes up for some kind of true web TS but at this point i feel (understatement) disappointed :-(.

    What's the point in having a webbased TS solution that only works on Vista clients anyway, like all of our employees have (or even want to) Vista installed at home.

    It just might be time to start looking away from MS since they don't seem to be able to provide in our day to day bussiness needs.


    - Will there be cross-browser support in the near future?

    - Will RDC 6.1 be released for XP Pre SP3?

    - When ?

  • Upgraded my machine to XP SP3 and made the reccomended Registry changes and it works like a champ. Published applications, and tswebaccess

    Teamserv, Thanks for finding a workaround. I would hope that this will be taken into consideration on the next release. Upgrading service packs is not something us admins want to do especially unless the service pack has been out for awhile and they got the bugs out of it.

  • We are trying to test TSWebApp for a significant deployment.  However due to the inavailability of the 6.1 client, management is asking us to abandon Windows 2008 and use Citrix instead.

    We would prefer to use TSWebApp for this, but we have to be able to pilot the solution this month, and without a beta 6.1 download we can't do this.

    Is there any info on the availability of a 6.1 downloadable for XP (beta or not) that we can use to hold off management forcing us to use Citrix?

  • get the beta of vista sp1 or xp sp3  these both include the rdp 6.1 client.

  • deleteing these keys fixed my issue thanks, no icons would show up on the remoteapp page, the only seemed to working when browsing the remoteapp page on the actual server.



  • Ok folks after a few days of playing about, I have finally cracked it! and managed to install RDP 6.1 onto Windows XP SP2, the client is fully working and TSWebApps also work just fine.

    I am running behind on giving a demo of this tech to my client so for now here are a couple of vids and I promise a full tutorial as soon as I get a few hours spare.

  • David:

    Holy crap!  I want that.  Where did you get the setup.exe file to install RDP 6.1?


    - Joshua

  • There is no setup.exe I made the install routine myself. Hopefully the tutorial will be ready within 48hrs.

  • Ok as promised here is a very quick tutorial on replicating what I did, there is lot of unrequired stuff in there so hopefully someone can carry on where I have left off.


    Send all feedback to

  • This install package replacing mstsc with another mstsc. What is in new mstsc? What does it do?

  • Any idea if this procedure will work on an HP thin client? (WinXP embedded)

  • Managed to get it working for a 5720 thin client.

  • Hi everyone,

    We would just like to remind everyone that any non Microsoft distributed RDC 6.1 packages

    like the one David Eales has posted on this blog comments section will not be supported by Microsoft.

    The Microsoft supported mechanisms to get RDC6.1 are by installing

    Vista SP1:  and

    XP SP3:


  • The replacement MSTSC.exe is very simple app, for some reason no matter what I did using TSWebApp always resulted in c:\windows\system32\mstsc.exe so the replacement file simply takes to the command line startup variable that is sent to mstsc.exe and passes it on to c:\program files\rdp6.1\mstscnew.exe The reason it is coded in an obscure language is because it is pretty much the only programming system I know inside out.

    Hopefully I will get round to making a file in a more widely used language so people get a better grasp of what is going on.

  • Hello,

    I'M a IT consultant in Canada. The French part of Canada. I can't find XP SP3 in french and none of my custommer run Vista. What can I do to make it run on a XP SP2 french edition?


Page 3 of 7 (101 items) 12345»