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 7 and 5 and type the answer here:
  • Post
  • Seriously, this makes it way to hard to test.  I have access to windows 2008 and can publish apps but can't test with client devices.  Why would you not provide a 6.1 download for testing.  If it requires SP3 it could be sometime before our enterprise would adopt this making it useless for me.  As a terminal server adminstrator in our company I'm excited about the potential of 2008 terminal services but this dependancy on a service pack is a huge disappointment

  • My client is currently looking for a Remote App solution, I am trying my best to tempt them away from citrix but I am a little red faced when I have to explain that I cannot give a demo without putting an entire service pack on the client machine, which doesnt work anyway.

    Come on MS release the client on its own! I have tried for hours to extract the required files from SP3 but no joy yet.

  • Tieing to a service pack was really boneheaded UNLESS it requires some other system-level stuff to accomplish what it's doing. I doubt that is the case.

  • Is the specification for rdp 6.1 available?  Do you know of any moves to develop the open source rdp clients to be 6.1 compatible?    

    ICA has always been reckoned to to perform better than rdp.  Does 6.1 have better performance than 6.0?

  • So Microsoft plugs all these new Terminal Server functions for Windows 2008 which are great so far, but they dont release the damn client to even test it.  Disappointing MS!  I thought when RC1 came out they would have at least let us test it that way.  

  • Will this be a permenant thing? Please allow only RDP bits for download, at least not to install SP3 and SP1...

  • Yo ! I have tried the same. Can we not download just the components required to make it work? or if it is a package that has dependencies as a separate build? This is so frustrating since I was just about to announce the completion of my POC and here I am downloading the damn SP to make it work ..

    Also, going forward, it will be a tough rollout ..

    K

  • How about thin clients????  How am I supposed to test this with a thin client?

  • work harder we need the client ;-)

  • why can't MS release just the client to make it work in XP/Vista just for MSDN or TechNet or something?? Rubbish to download the SP1 for Vista just to get the client!

  • Installing XP SP3 doesn't seem to give you the ActiveX control to use Web access. It also doesn't seem to install stuff to run remoteapps. Nice to know that the two groups are talking to each other.

  • Hello Gadzoo,

    When you use Web Access from XPSP3, do you see a warning icon in the Internet Explorer Manage Add-Ons UI?

    If you open this and enable the Terminal Services activeX control, are you then able to use Web Access?

  • Hello Gadzoo,

    Can you also let us know what build of XPSP3 you are experiencing the issue on?

  • @termserv

    I would, if those addons popped up on my list in IE7. Worked like a charm on another computer with IE6 though, there i could just enable the addons.

  • Thansk for the information teval.

    We are investigating this behavior in XPSP3.

    In the mean time as a workaround can you try deleting the following registry keys:

    HKCU\Software\Microsoft\Windows\CurrentVersion\Ext\Settings\{7390f3d8-0439-4c05-91e3-cf5cb290c3d0}

    HKCU\Software\Microsoft\Windows\CurrentVersion\Ext\Settings\{4eb89ff4-7f78-4a0f-8b8d-2bf02e94e4b2}

    .Once you delete these keys, the activeX contro lshould be enabled in IE7.

Page 2 of 7 (101 items) 12345»