Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

We've released the new version of the Remote Desktop Client corresponding to Vista. Here are some of the new features:

  • 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.

 

To install the new version, go to Windows Update on the target computer and look for optional software updates, or download it from the Microsoft Download Center.

 

Remote Desktop Connection (Terminal Services Client 6.0) for Windows Server 2003 (KB925876)

http://www.microsoft.com/downloads/details.aspx?FamilyId=CC148041-577F-4201-B62C-D71ADC98ADB1

 

Remote Desktop Connection (Terminal Services Client 6.0) for Windows Server 2003 x64 Edition (KB925876)

http://www.microsoft.com/downloads/details.aspx?FamilyId=43C0EAE9-6B64-428F-A9DC-F97F5A1B4493

 

Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP (KB925876)

http://www.microsoft.com/downloads/details.aspx?FamilyId=26F11F0C-0D18-4306-ABCF-D4F18C8F5DF9

 

Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP x64 Edition (KB925876)

http://www.microsoft.com/downloads/details.aspx?FamilyId=160CE316-BF2B-48D0-A035-E2ABBC55D8E8

 

Localized versions and the Multi-User Interface Pack will be released in the coming months.

Leave a Comment
  • Please add 1 and 4 and type the answer here:
  • Post
  • The problem with controlling the RDP options via the default.rdp file, e.g. to turn off the double logon prompt, is that after installing the client, you now have to touch the default.rdp file for every user on every PC or server they use, no an elegant solution. Why in the world don't you have global setiings, or use a GPO?

    Another problem is that the Windows key now no longer works on the remote desktop, when you press the Windows key, it brings up the start menu, on the local desktop.

    Could you please fix these issue ASAP?

    Thanks,

    Chuck HAllback

    P.S. This blog is SO slow, it's almost unusable

  • The problem with controlling the RDP options via the default.rdp file, e.g. to turn off the double logon prompt, is that after installing the client, you now have to touch the default.rdp file for every user on every PC or server they use, no an elegant solution. Why in the world don't you have global setiings, or use a GPO?

    Another problem is that the Windows key now no longer works on the remote desktop, when you press the Windows key, it brings up the start menu, on the local desktop.

    Could you please fix these issue ASAP?

    Thanks,

    Chuck Hallback

    P.S>. This web site is SO slow it is almost unusable.

  • Sorry for the triple post, I kept getting server errors about page not found.

    The major changes in behavior from remote desktop 5.2 to 6.0: e.g. prompting for credentials before connecting, the Windows key not working on the remote desktop, etc, is analogous to Microsoft coming out with an MP3 player that is not Playforsure compatible, and won't play the DRM protected WMA files that law abiding people have been buying online for years ... Like a Zune. Didn't you beta test remote desktop 6.0?

    If Microsoft would get feedback from real people/users, they could avoid these major blunders that make people lose faith in them.

    Chuck Hallback

  • remote desktop 6.1 (coming with Vista SP1) will not have double logon problem and will not prompt for credentials before making a connection. So, you won't have to make changes to default.rdp.

    Vista SP1 is also going to have reacher GP support for remote desktop client.

  • Will the problem with the Windows key combos, and alt-tab, not working on the remote desktop also be fixed? For us this is the biggest show stopper on deploying the 6.0 client.

    I didn't see this mentioned on your list of issues for the 6.0 version.

    Thanks,

    Chuck Hallback

  • Installed the XP SP2 RDC update but now getting always this error. But if I move away the error dialog I'm able to sign on and get connected to remote system. Is this a known issue?

    AppName: mstsc.exe AppVer: 6.0.6000.16386 ModName: unknown

    ModVer: 0.0.0.0 Offset: 011a5c50

  • RDC6 was installed on my computer while making a repair install (yes, _now_ I know I should have unplugged my computer from the net :)) and cannot be uninstalled normally via Add/Remove Programms or WinUpdatesList. Is there a way to remove it manually, like deleting mstsc.exe and all references to it in registry?

    Thanks a lot.

  • To Girc:

    There should be a checkbox that controls whether to show updates.  Check that box, and you should see the RDC update, which will allow you to uninstall.

    Rob

  • To Rob:

    Thanks a lot for the answer, but I tried it and unfortunately it does not show, that's why I asked for a way to remove it manually :)

  • Will the problem with the Windows key combos, and alt-tab, not working on the remote desktop also be fixed? For us this is the biggest show stopper on deploying the 6.0 client.

    I didn't see this mentioned on your list of issues for the 6.0 version.

    I would hate to have to use a premier support call to find out the answer to this

    Thanks,

    Chuck

  • To Chuck:

    I also have the "alt-tab" problem with rdpclient 6.0...it's stopping to work sometimes but I really don't know why :/

  • I have a 22 inch monitor at work that's set to 1680x1050 resolution.  I connect from home to work PC via Remote Desktop just fine (using laptop from home - smaller resolution of course).  However, when I come to the office, I find a message on my monitor "Set screen resolution to 1680x1050" and only way to recover is to reboot my work PC.  

    I suspect Remote Desktop is not resetting work PCs resolution to what it's usually set to (1680x1050).  Is there anything I could do?

    Will this new client remedy this issue?

    Windows XP service pack 2 on both work & home pcs.

  • I also witnessed the same strange netbios lookups for '..LOCALMACHINE' - using strings, I verified they are in the RDP 6 client code. Any idea how to get rid of this ~7 seconds delay?! very annoying.

  • Setting up a new XPe thin client that came with RDC 6 installed.

    Trying to connect to a Windows 2003 SP2 terminal server.

    The terminal server has Novell Client 4.92 installed (we authenticate against NDS and AD).

    With RDC 5.x the user would be delivered directly to the Novell Client login screen.

    With this RDC 6 the user is prompted for login credentials which do not seem to work.

    If I enter the username password (usernames and passwords are synchronized between NDS and AD) I am told the username/password combination is incorrect.  This is because the RDC is trying to connect to a local account on the terminal server where the user has no account.  The user then has to change the setting from the local machine to the domain, uncheck the workstation only checkbox on the Novell Client and log in.  The same problem occurs when using a fully qualified name.

    The only way I have managed to get the users to connect is to have them enter a bogus name in the username field and leave the password empty.  

    Is there any way of turning off authentication?

    Is there way of changing the default user name?

    Is there any way of uninstalling RDC 6 from an XPe build that has it as a defualt so I can install RDC 5.2?  I tried installing RDC 5.2 but was told that I could not as RDC 6 was already installed.

  • Hi, we're having a strange problem that appears to be happening since upgrading to mstsc 6,

    we have four windows 2003 servers that we connect to via remote desktop / terminal server sessions.

    the mojority of the time we log on and off without issue, however sometimes the log off is not smooth.

    i click 'log off' and confirm this, desktop/explorer closes and i'm left with the blue background and the yellow task bar across the top of the screen, the sessin will stay like this for as long as you are prepared to leave it.

    if i press ctrl+alt+end whilst in this hung session i can choose log off again and the session closes.

    Strangely there are no entries in the event log to give me an ide how to troubleshoot.

    through testing i've found this happens more often if i fire up a connection and immediatly log off.

    Any thoughts as this ones driving me crazy

    Thanks in advance

Page 13 of 16 (229 items) «1112131415»