we heard a lot of feedback from you about the need for the Remote Desktop Connection client 6.1 to be made available as a standalone install for Windows XP SP2 to ease deployments of Windows 2008 Terminal Services.
In response to this feedback, we have released the Remote Desktop Connection client (RDC 6.1) for Windows XP SP2 on x86 platforms.
You can download RDC6.1 for Windows XP SP2 from the Microsoft Download Center (KB 952155) for the following languages:
Arabic, Chinese - Simplified, Chinese – Traditional, Danish, Dutch, English, Finnish, French, German, Greek, Hebrew, Hungarian, Italian, Japanese, Korean, Norwegian, Polish, Portuguese – Portugal, Portuguese – Brazil, Russian, Spanish – Spain, Swedish, Turkish.
We have also released the MUI package for RDC6.1 on Windows XP SP2 from the Microsoft Download Center (KB 952230).
These are some of the supported features of Remote Desktop Client 6.1 for Windows XP SP2:
Please review the complete list of features and details about RDC6.1 for Windows XP SP2 in this Knowledge Base article.
RDC6.1 is now available on the following platforms:
Windows Server 2008
Windows Vista SP1
Windows XP SP3
Windows XP SP2 (KB 952155)
I need the RDC 6.1 for windows server 2003 to use the ts gateway funtionality of 2008. I have 200-400 users that access windows server 2003 desktop both as clients for Terminal services and for administration of our TS farm. We are able to publish urls instead of RDP files for users to access their server.
We are also able to use Citrix to enhance the client connection issues with RDP. IE using a java client, active client to provide access to a VDI ennvironment.
Making the RDC just for desktop is short sighted.
You also need to include instructions for customizing the RDP properties of the TS Gateway.
For example how would you make the following work.
My users can click and this url and go to a specific server/desktop though the ts gateway using RDP or Citrix ICA.
What about running on WinFLP? Doesn't seem to work... WinFLP supports multiple end-users, and the added benefits of 6.1 would be most excellent. Is this anticipated?
WinFLP is based on WinXP Embedded, so RDP6.1 client should be able to run. What does not work? the setup of the package? the client itself?
We have several dozen HP thin clients offsite, both at users' homes and at teleworking locations. The thin clients are HP T5530's running Windows CE 6. Unfortunately our rollout of Windows Server 2008 Terminal Services is severely hampered by the lack of Terminal Server Gateway support in the Remote Desktop client available on Windows CE 6.0 - we need the Terminal Server Gateway role is load-balancing.
Is there a RDP client available for Windows CE 6.0 that supports the Terminal Sever Gateway role?
If not are there any plans to release one? If so is there an ETA? Is there a workaround/hotfix that I can try?
Slightly O/T: Assuming that there is no client and there are no plans to make one is it possible to upgrade the HP T5530 from Windows CE 6.0 to Windows XPe? I know that this is slightly outside the remit of Terminal Services but I would assume that the terminal services team has experience with thin clients so I thought I'd ask...
We can just about afford to buy higher-capacity flash cards and RAM to get Windows XPe running but replacing all out T5530's, some of which were bought just a couple of months ago, makes Windows Server 2008 terminal services financially untennable no matter how much I like it! :)
the RDC 6.1 installer package won't work on WinFLP. Says something along the lines of "not for this architecture"
1) Whether you need the latest RDC client (RDC6.1) on Windows Server 2003 because you have end users using Windows Server 2003 as a client OS?
We have this situation, many of our developers use server 2003 as clients; some need access to tsrweb site. MS seriously you updated 2003 for 6.0, and skip it for 6.1, while pumping it out on XP-sp2 and sp3? Why in gods name would you not bother with 2003. It's sort of sad we even have to ask, and yes both x32 and x64 is needed.
Can you explain to me why RDP 6.1 initiates 2 connections in the background to my windows 2003 terminal server? What is 0ed000001234000300080002000000? And why does it cause my RDP 6.1 client to reinitiate a connection which means i cannot load balance RDP using hardware load balancers
How about TS Web Access support for windows CE. We have HP thin client 5530 and would like to run ts web access against 2008 terminal server
Since installing SP3 i have had no end of errors with RDP.
"AppName: mstsc.exe AppVer: 6.0.6001.18000 ModName: mstscax.dll"
Is there a simple fix?
Is there a way to package and distribute the 6.1 ActiveX in .CAB file so that users of our site have access to the new features without the need to install the whole app?
Is ther any simple deployment method for RDC 6.1.. We have an need to use the new printer redirection feature of 2008 TS and have 600+ clients running XPSP2. I don't really want to have to physically run the install as an admin on each PC. Is there and MSI deployment we can send out via Group Policy?
We would need RDP 6.1 for Win2003 to make a Connection from a Win2003 / Citrix Environment to Win2008/RDP 6.1 Terminal Gateway Platform where our subcontract order processing Application is Hosted.
Doesn't work with RDP 6.0. Only with RDP 6.1 from a WinXP Client.
So, it would be really great for us if RDP 6.1 would be released for Win2003.
We require RDP 6.1 on Windows XP X64 because we have dozens of computers running XP X64 and now have a server 2008 environment, Its needed to access Remote Web Applications, we support large trading environments and our clients use X64 xp because some of their products dont yet support Vista ( or they dont want to go to Vista X64) and use huge amounts of memory 8-16GB is a standard desktop
I have posted on many forums and blogs in the past and feel this is a business need. If you want me to write a business case for it I will.
I can be contacted at firstname.lastname@example.org and we are a Microsoft Certified partner
I have found an easy way to get around this for now.
Delete the mstscax.dll, mstsc.exe file for version 6.0 and replace them with the 5.0 files.
They are stored in windows/system32 folder.
Fixed my problems instantly.
At my company we regularly admin W2008 server TS boxes from other 2003 boxes. The TS boxes are configured to use Network Level Authentication/NLA which is great but we stumble when we try to connect to the 2008/TS boxes from 2003.