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

  • Comments 99

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 5 and 8 and type the answer here:
  • Post
  • http://www.flickr.com/photos/29452822@N03/2753709169/

    I could not email the UI so I posted it online.  This is the dialog I receive in Vista.  It is very similar to the ones I receive in other OS

  • Thanks, Joe, for sharing the picture - that clears things up a lot!  That's not a server auth issue (which it sounded like earlier), but a prompt saying that your RDP file is not signed.

    To fix this and get rid of the prompt, you must sign the RDP files - in Server 2008 you can do it through TS RemoteApp Manager mmc or cmdline tool - see technet post here for info: http://technet.microsoft.com/en-us/library/cc753982.aspx; It's recommended and is safer to sign the RDP files with a cert issued by a trusted authority (e.g. verisign or your enterprise CA) but you can also use a self-signed cert created on your TS server.

  • THE NEED for RDC6.1 on Windows 2003.

    I need the RDC 6.1 for Windows 2003 because I can't publish Windows 2008 Terminal Server Applications through my IAG server unless the 6.1 client is installed.

  • I need the client as well.  What gives msft?

  • I need 6.1 for server 2003 because of ts easy print feature!

  • Response for Wintel:

    You mentioned that you need RDC6.1 for WS03 because you can't publish applications through your IAG server.

    Publishing applications from a 2008 TS Server does not depend on the version of the client you have on that Server.

    IAG shouldn’t be dependent on the version of the RDC client either.

    Hence you should be able to publish your applications from your WS08 Server.

    Could you clarify

    What OS are your client computers running? What version of IAG are you running?

  • I need the rdp 6.1 client in order to use easy print when connecting from server 2003 to server 2003

  • Microsoft officially didn't launched Terminal Services Client 6.1 for Windows 2003 yet. But you can resolve this issue by the available hotfix exclusively for Windows XP w/Sp2.

    Download the hotfix from here :- http://www.microsoft.com/downloads/details.aspx?FamilyId=6E1EC93D-BDBD-4983-92F7-479E088570AD&displaylang=en.

    Once the download is completed:-

    1.Right click on the hotfix and click properties.

    2.There you will find a compatibility tab. Check the box "Run this program in compatibility mode for"

    3.In drop down menu select Windows XP.

    Viola you are done, install the hotfix. The RDC 6.1 client dll's will be updated and you will be able to access TS RemoteApp smoothly.

  • To termserv:

    "Please add a brief description of the usage scenario for you/your business for these features."

    Excuse me? Why do I have to explain anything??

    According to http://support.microsoft.com/lifecycle/?p1=3198 , Windows 2003 *should* be supported to at least 2010. I have paid for Windows 2003 and I want to get the promised support. I think that class-action suit is needed.

  • The reason MSFT asked why this was needed is because 2003 is not a client operating system, and any development work needs some justification. For future reference the way to respond to a question like this and actually get what you want is to state the "business" case for adding support for this feature, not "so I can use this feature on Server 2003".  Games are not installed on 2003 and I don't hear an uproar about that.

    Explain to Microsoft what business value this has instead of complaining and you have a "chance" to get what you want. An example would be "we use Server 2003 as the Client OS for a group of 50 developers that create software X.  While they run their development tools locally, these employees run their line of business applications via 2008 Terminal Server RemoteApp, and they need to be able to print to their local prin devices without installing the drivers on the Terminal Server, because their printer's driver is known to be unstable on TS, or because it is the company's policy to not install 3rd party printer drivers on TS."

    Saying "because I want" is not sufficient, even if you are a paying customer.  It's not too much to ask that you explain what value this adds for you business.

    Patrick Rouse

    Microsoft MVP - Terminal Server

    http://blogs.inside.quest.com/provision

  • The reason MSFT asked why this was needed is because 2003 is not a client operating system, and any development work needs some justification. For future reference the way to respond to a question like this and actually get what you want is to state the "business" case for adding support for this feature, not "so I can use this feature on Server 2003".  Games are not installed on 2003 and I don't hear an uproar about that.

    Explain to Microsoft what business value this has instead of complaining and you have a "chance" to get what you want. An example would be "we use Server 2003 as the Client OS for a group of 50 developers that create software X.  While they run their development tools locally, these employees run their line of business applications via 2008 Terminal Server RemoteApp, and they need to be able to print to their local prin devices without installing the drivers on the Terminal Server, because their printer's driver is known to be unstable on TS, or because it is the company's policy to not install 3rd party printer drivers on TS."

    Saying "because I want" is not sufficient, even if you are a paying customer.  It's not too much to ask that you explain what value this adds for you business.

    Patrick Rouse

    Microsoft MVP - Terminal Server

    http://blogs.inside.quest.com/provision

  • "You can get further with a kind word and a gun than you can with just a kind word."

    Saying "class-action suit" *is* sufficient :-)

  • Someone has already posted a way to install version 6.1 of mstsc.exe on 2003, so what is the issue?  Mine would be the need for a supported configuration.

    As for your threat of a law suit, I think you're completely out of line, and acting in an unprofessional manner.  If you formulated a proper argument and presented it in a tactful manner you would have already received a response from MSFT. instead i've see a bunch of techies complaining "I want, I want, I want..." without ever articulating  the reason for the request.

    I agree that this client should be available for 2003, but I have no need for it. I am not going to ask MSFT to spend dev time that they could be applying elsewhere when no one has properly articulated why their business requires this functionality.

    If anyone wants to spend the time, I'd be happy to relay their requirement directly to the  MSFT Terminal Services Team.  I can be contacted at Myfirstname.Mylastname@quest.com.

    Patrick Rouse

    Microsoft MVP - Terminal Server

    http://blogs.inside.quest.com/provision

  • Where can find RDP Client 6.1 for Windows XP Professional x64?

    Windows XP Professional x64 is a client operating system, so I hope that I don't to make up a fake "business" case to download it.

    Thanks in advance!

  • Responding to RDP Rocks and the rest of the comments requesting RDC6.1, here’s a clarification of the platforms on which RDC6.1 is supported:

    Platforms on which RDC6.1 is currently supported by Microsoft:

    XP SP3 x86

    XP SP2 x86

    Vista SP1

    Windows Server 2008

    Platforms on which RDC6.1 is NOT currently supported by Microsoft

    XP SP2 x64

    Windows Server 2003

    If you feel you have a valid business case that Microsoft needs to consider please share the following information with Microsoft:

    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? Or whether you need RDC6.1 on Windows Server 2003 in order to perform you administrative tasks from Windows Server 2003?

    2) If you need RDC6.1 on Windows Server 2003 OR on XP SP2 x64 because you have end users using either as a client OS please let us know how many such terminals/computers you have in your environment and what features of RDC6.1 you need to use.

    3) If you believe you need RDC6.1 in order to administer machines please let us know why the RDC that is available on Windows Server 2003 is not sufficient for you to perform your administrative tasks.

    Please send the above information to your Microsoft Technical account manager  or please post it to https://connect.microsoft.com/WindowsServerFeedback

    Thanks,

    The Terminal Services Team,

    Microsoft

Page 3 of 7 (99 items) 12345»