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.
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.
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" />
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
We just installed the Windows 2008 RTM, and now our Windows CE users can't login anymore!! They get an error dialog saying: "client and server versions do not match".
Please help, some of our users can only access the server from a Windows CE client, and they are stuck now!
Of course, on the Remote tab under System Properties I enabled the second option (running any version of Remote Desktop), but still, they are not allowed in.
Please tell me there is some sort of workaround, like a registry key that I can change to still allow Windows CE clients?
Thank you very much!
What version of Windows CE/RDC on Windows CE are you using?
1) Exactly what problem/message are you seeing with XPSP3 IE 7?
Have you tried the workaround mentioned in the above comments:
as a workaround can you try deleting the following registry keys:
Once you delete these keys, the activeX control should be enabled in IE7.
2) The Vista SP1 pre-release evaluation period is now over -hence the download is no longer avialable. Once Vista SP1 RTM is avialable you will be able to use RDC6.1 from Vista SP1
Thank you David for figuring out how we can install RDC 6.1 onto our WinXP SP2 machines.
We need to test Win2008 now, pushing out SP3 isn't an option for us (no telling what MS may decide to break in this release).
Hopefully MS will eventually package their on RDC 6.1 package, instead of forcing a 300+ meg download on everyone just to receive a single app.
In any case.. we appreciate the work you did in cleaning up MS's mess.
What about support for XP 64bit?
I'm getting the Active X error in Vista SP1 RTM...can anyone help? I've put the server in the Intranet zone...but it's not working.
I work in education and to tell 10,000 pupils to upgrade to the latest service pack so they can remote apps is just no good enough. I can tell them to install an application but not a whole service pack. I hope you reconsider in mind of our kids education.
Have 2 machines, one with XP SP3 and one with the RDP6.1 installed as per instructions above. Both are able to run apps from TS Web Access, but not via a gateway.
I get this error:
You have specified to use a gateway server, however this feature is not supported by your system configuration.
When I bring up the options for an RDP connection on the advanced tab under "Connect from Anywhere" the settings button is greyed out with the message "Connections using a gateway server are not supported by your system configuration"
So the big question is: Will there be a RDC 6.1 be made available for WinXP embedded clients?
The method David outlines above works on WinXP embedded (without the gateway functionality). We're running our thin clients on it in a pilot program.
Is there going to be a way that we can roll this out to MAC clients?
I'm followed the comments of this thread to successfully get RDC functionality on both Vista and XP systems in my lab. Thanks for providing this shared experience.
This situation though is very strange as Server 2008 is now launched. How can I sell this solution to my customer who needs this exact thing right now when there isn't any released client for Vista or XP in the public realm? This is like buying a brand new Ford GT-40. Its hot, its fast, its sounds great, but the custom size tires aren't yet for sale. Huh!? Well it looks nice in the window.
Come on guys, catch up and get this RDC software out to the market before I have to quote Citrix Application Virtualization solutions.
Server 2008 has OFFICIALLY launched!! Where is the damn client RDP 6.01 client. This is unacceptable!!
Server 2008 Terminal services
Client: Used WinXP SP3 with IE7...installed tswebsetup.exe. Hit Tools>Internet options>Advanced>RESET and all was right with the world. All your TSWebApps show up with a refresh...The only drawback is that it pretty much blows away everything you have set up in IE (Favorites,cookies,certificates,etc.)
Still working on Vista.
This is beyond stupid. I've to evaluate and present to my management by the end of the month. We use Citrix currently and I've to present on the App publishing of 2008.
We use XP SP2 and we won't be moving to SP3 for some time so if there's no client I can use for the web access we'll be renewing Citrix. Probably would have been anyway but at least MS have saved me some work by producing something that won't work with 75% of corporate desktops.