Remote Desktop Connection (Terminal Services Client 6.1) for Windows XP SP2 x86 platforms

Remote Desktop Connection (Terminal Services Client 6.1) for Windows XP SP2 x86 platforms

Hello everyone,

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:

  • Windows Server 2008 & Windows Vista feature support
  • TS Web Access support
  • TS Easy Print support
  • TS Remote Programs support
  • TS Gateway support

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)

Leave a Comment
  • Please add 7 and 2 and type the answer here:
  • Post
  • We bought new boxes for Windows and use old Windows 2003 boxes as workstations and to administer the new boxes. We would like to use NLA but we need RDC 6.1

  • Hi there... We require RDC 6.1 for WS2003 in order for our clients and staff to access RemoteApps from our TsWeb.  Any update and/or workaround would be highly appreiciated.  Please note this is a time sensitive matter, as my company has recently been commisioned to rollout multiple WS2008 TsWeb servers.

    Thank you in advance for you help with this matter.

  • Same as everybody else around here...  I need to get RDP'd to 08 from 03 and I think its a croc of crap that M$ hasn't released this when so many of us NEED it.  Not just some bunch of techies saying I want; No, we're saying rather clearly that we need it and now we're being ignored.  This is B$ M$.

  • I am in the process of migrating a company off of Server 2003 to Server 2008. I have installed and configured 2 terminal servers (2008 x64), a TS Session Broker, and a TS Web App server. Any modern XP and Vista PC can RDP the load-balanced TS's all day. However, the thin clients, using version 5 RDP, can't even connect. I have changed the security settings, encryption settings, disabled NTLM authentication, the whole nine yards. Is there anything else I can do to get these older thin clients connected to the new term servers? Some of the thin clients are not updateable, so I am stuck with a load of them unable to connect. My last resolution is to put server 2003 on the term servers and lose the TS gateway functionality and the TS web apps. Somthing that would greatly disappoint my customer. So, is there anything I can do to get these working?

    Thank you,


  • It's pretty simple to setup. You need to first install a printer to your local machine. Then set that machine up to share that printer. Then on the remote machine find the shared printer and add it to the remote machines printer list. This is how I do it for my <a=href"">computers and networks repair company, TechBranch of Tampa</a>.

  • We've not used TS Session broker,

    But I've got RDP 5 clients working in Terminal Server 2008.  

    I basically had to un-install the terminal services role and get remote desktop working with the clients. I reduced the security/encryption to client compatible and the remote desktop worked.

    I then re-installed the terminal services role and the RDP 5 clients (wyse, linux etc) continued to work.

    It seems that the Remote desktop settings over ride the terminal services settings so you have to get Remote Desktop working first!!!!


  • We would like 6.1 for 2003 purely for the performance increase.  I have anywhere from 40-60 users connecting to 2 W2k3 Terminal servers and from my remote users I am getting some extreme issues when scrolling graphics and other issues, even with things set to the lowest settings in the RDP client on the client computers.

  • The 6.1 client only gets you a performance increase when connecting to Vista SP1 or Server 2008.  For RDP graphics acceleration on XP and 2003 as well as Vista & 2008 you can use Quest vWorkspace.

  • That's all well and good, but being a non-profit that has moved to Terminal Services for costs savings and such, I don't have any budget to buy any new products, so your advertisement doesn't work for me.

  • Well you have three options, put up with complaining users, find a solution or go back to what you used to do before using Terminal Services.  Microsoft is not going to add the RDP 6.1 protocol stack to version 5 operating systems, i.e. XP and 2003, so you can either run 2008 Terminal Services and XP SP2+ clients with RDP 6.1 clients, or use an add-on product from companies like Quest or Citrix.

    RDP 6.1 provides a 40% decrease in bandwidth over 6.0 and 5.x, and Quest's EOP provides a 500% to 100% decrease in bandwidth consumption, which is designed specifically for WAN/Internet connected users.

    Other options if your users are connected from a remote office is to use QoS Appliances from Expand Networks or Cisco to cache & compress traffic.

    I worked as an IT Director for 4.5 years so I know what it's like to manage a budget that is very limited, and get by with what ships out of the box.  The worst your organization can do is deny your request to look at 3rd party solutions.

  • I'm trying to use easy print with a RDP connection. But my 2008 Server (Web edition) always use printer's drivers and not easy print driver. My computer configuration is ok because if I connect the same computer to another 2008 Server, Easy print is use. Why ? I must install something more on my server ?

  • You ask why would we need 6.1 on XP x64. To connect to my Windows 2k8 server for admin purposes.

    Why would you not provide 6.1 for x64?

  • So why not just copy the MSTSC.exe and MSTSCAX.DLL from a windows xp box that is running 6.1 and overwrite the files on the 2003 server?  I don't know if causes and issue, but it looks like it worked OK when I did it.

  • Tell me please, how to enable the NLA on XPx64 or Win2003 TS clients?

  • Hi, CredSSP (which is required for NLA) is not available on Win 2003. For information on how to enable it on XP SP3 please see:



Page 5 of 7 (100 items) «34567