Update:Remote Desktop Connection (Terminal Services Client 6.0) for Windows Server 2003 SP2 released

Update:Remote Desktop Connection (Terminal Services Client 6.0) for Windows Server 2003 SP2 released

  • Comments 13

We've released the English and localized versions of the Remote Desktop Client for connecting to Vista.

We recommend that to install the new version, users go to Windows Update on the target computer and look for optional software updates.

The new version can also be downloaded  from the Microsoft Download Center however users should take care to install the package appropriate for their target OS and architecture. If you need to download the package manually on Windows 2003 SP2 please click the appropriate language link:

Windows Server 2003 SP2 x86: English, Chinese – Simplified, Chinese – Traditional, Czech, Dutch, French, German, Hungarian, Italian, Japanese, Korean, Polish, Portuguese – Brazil, Portuguese – Portugal, Russian, Spanish – Spain, Swedish, Turkish.

Windows Server 2003 SP2 x64: English, Japanese

Windows XP SP2 x64: English, Japanese

Here are some of the new features in this version of the Remote Desktop Client:

  • Server authentication
  • Plug and Play redirection
  • TS Gateway support
  • Monitor spanning
  • 32-bit color and font smoothing

More details on the features are in a Knowledge Base article.

 

Leave a Comment
  • Please add 1 and 8 and type the answer here:
  • Post
  • Does this fix the PinConnectionBar = 0 problem?

  • It does not fix the PinConnectionBar problem.  This is just a rerelease of properly signed and versioned binaries for installation on WS03 SP2.

    The fix for pinning the connection bar should arrive in the next release of the Remote Desktop client that will ship with Vista SP1, Longhorn Server, and as a new downlevel redistributable for pre-Vista OSes.

  • I' ve been testing the new client, using a Windows 2003 server, the client has some refresh issues with a Visual Foxpro Application.

    The Issue is in a Grid, and the problem is that screen doesn't reflect the actual position of the cursor. You have to wait about 70 seconds, or move the mouse to see the cursor in the correct position.

  • Does this upgrade fix the issue with the RDP Client v6 deleting the Default Domain Registry key on the server one is connecting to when logging on to a Terminal Server console using the username@domain.com method when logging on as administrator?

  • [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]

    "DefaultDomainName"=""

  • Could someone squeeze in an update to "Remote Desktop Protocol settings in Windows Server 2003 and in Windows XP (Article ID 885187)

    Some settings are no longer in use, and new ones have been added with no explanation of what they do or their parameters.

    Thanks, Fred

  • Is the "Windows key *not* working" has been resolved so far?

    I used RDP 6.0 on my XP SP2 and it was a huge pb. In each TS session, the keyborad shortcut did not work despite I enable this dfeature in the .rdp files! I uninstall the RDP 6.0 client to the 5.2... which worked perfectly.

    But i've just install XP SP3... and you know what? RDP client is bundled! So I've still got my pb... Hey MS gus, don't tell me you did not solved the pb with some registry tweaks!

  • We need to have multiple RDP sessions for single workstations.  5.2 worked great and it was fast.  6.0 is slow and does not allow for multiple sessions.  I've tried several ways to work around it with no success.  I can't believe, but I guess I do, that you made your product worse.  In general you seem to be failing at a lot of stuff.  Stop thinking of fluff and start thinking practical.  If you re-write something, try testing it thoroughly before you slam it down our throats.  Stop screwing up XP, it was fine.  Please write a fix and let me know, I have hundreds of users to support.

  • We need to have multiple RDP sessions for single workstations.  5.2 worked great and it was fast.  6.0 is slow and does not allow for multiple sessions.  I've tried several ways to work around it with no success.  I can't believe, but I guess I do, that you made your product worse.  In general you seem to be failing at a lot of stuff.  Stop thinking of fluff and start thinking practical.  If you re-write something, try testing it thoroughly before you slam it down our throats.  Stop screwing up XP, it was fine.  Please write a fix and let me know, I have hundreds of users to support.

  • Hi,

    24 bit color on Terminal Server 2008 and rdp 6.0 don't work. 32 bit and 16 bit works fine but if you have a client running 24 bit or if you configure the RDP Client to use 24 bit the server downgrades the session to 16 bit. Applications that need 24 bit do not work. To a Windows 2003 server it works.

    RDP 6.0 on CE version don't have a working TS GW function.

    USB support to USB memmory is very slow and session frezze on Winwdos CE devices running RDP 6.0.

    Windows CE version, don't work well whit redirection of streaming video to local media player.

    Citrix version works well, but I thought that then MS implemented these functions they should work on all devices and to 2008 servers.

    Will there sone be a new release or update for CE devices? It' works well on Winwdows XP and Vista. But if you use Terminal Server you shouldn't use a Vista or XP machine if you don't need to. So why don't you work harder to make a better thin Client experince?

    So we need to continue to use Citrix if we want to have basic funtions on Thin Clients.

  • Please mention concrete statement on supporting multiple sessions of Terminal Services Client 6.0.

    If it is not supporting multiple sessions which version can support?

  • There appears to be a problem with the RDP session thinking the Windows Key is stuck down in this new version.

    e.g. you press the L key in the session and it locks, as if you were holding the Windows key down.

    Pressing the Windows key a couple of times seems to resolve for a while.

    There is a fix for this on Vista (KB938080) but not on XP.

    Please sort it out.

  • Hello. We are using Win2003 R2 x64 RUSSIAN.

    For this language exist only rdp client 5.2 correctly ?

    To run published application is necessary rdp client 6 or better

Page 1 of 1 (13 items)