Microsoft releases Terminal Services Client 6.0 for Windows XP and Windows Server 2003
Microsoft just released the Terminal Services Client 6.0 for Windows XP SP2 and Windows Server 2003 SP1. This new client version provides a way to use any of the new Terminal Services features introduced in Microsoft Windows Vista and Microsoft Windows Server Code Name “Longhorn” from a computer running Microsoft Windows XP with Service Pack 2 or Microsoft Windows Server 2003 with Service Pack 1. Download the client from the links below:
Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP (KB925876)
Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP x64 Edition (KB925876)
Remote Desktop Connection (Terminal Services Client 6.0) for Windows Server 2003 (KB925876)
Technorati : Client, Microsoft, RDP, Terminal Services
Del.icio.us : Client, Microsoft, RDP, Terminal Services
Ice Rocket : Client, Microsoft, RDP, Terminal Services
Mark Says:
December 4th, 2006 at 10:23 pm
Be aware that on Windows XP SP2 machines Alt+Tab may not switch windows on the remote machine even when you set the option for it. As I frequently use Alt+Tab to switch between programs I have been forced to revert to a previous version of Terminal Services Client. The bug has not been fixed as of 5/12/2006.
Matt Says:
December 8th, 2006 at 1:21 pm
Ever since going to the 6.0 RDP client, I’ve had issues with windows thinking the Windows key on my keyboard is being pressed, even though it’s not. I hit L, the terminal locks, I hit E, I get explorer, I hit U and I get accessibility controls. Anybody else got this? I’ve had it, and one of my fellow admins has also experienced the same on his desktop. Keys are DEFINITELY not stuck.
Fix is to tap the windows key a few times, then it goes away for a while.
Joel Wasinger Says:
December 18th, 2006 at 4:50 pm
Matt,
I’ve encountered the same problem (the system thinks the Windows key is pressed). There’s no problem outside of RDP. Good to see that there is at least a temporary work-around.
Andy Says:
January 12th, 2007 at 7:46 am
Matt,
We have the same problem. Since we have installed the MSTSC 6.0 some Windows 2003 servers are working like the windows key is pressed instantly. But there is no windows-key on the keyboard. I’ve found no way to disable that “feature”. Disconnect or Logoff are no work-arounds. A server-restart solves the problem
The windows-key-tapping-action is not working. I’ve installed Windows XP Professional + SP2
Kim Says:
April 13th, 2007 at 11:03 am
Just to pitch, I experience the same problem and I just want to add to the discussion, that rebooting a remote server is not an option in any live environments. I sincerely hope Microsoft resolves this issue and deploys a new release of Remote Desktop.
On a side note to Remote Desktop.
It should be able to handle two concurrent connections and one /console connection.
Its our experience that this does not work well. We keep bouncing each other off if a user tries to connect to a server that already has a user connected.
Have you guys experienced the same problem?
Bryan Says:
June 6th, 2007 at 8:13 am
exact same issue but found that if I hit the L key a fair few times, then locked the TS session then hit windows+L (and locked my local machine) and then ctrl+alt+del and unlocked my machine it all seemed to go away..!
No doubt it’ll surface again some other time though…
Bry
Moni Says:
July 26th, 2007 at 11:49 pm
Regarding Generation of Terminal service gateway(TSGU) traffice over netmon :
Hi, i have a setup where-in i need to connect to remotely from a client(longhorn)to a target server(longhorn)through a Gateway server(longhorn).
I am able to connect using mstsc,but i am not gettng the TSGU packets over netmon 3.1.Can anyone help in this regard?
Greg_PL Says:
October 24th, 2007 at 5:25 am
have one quesion. What is effective response time for RDP in mseconds? Iam trying to find the perfect bandwidth for RDP
Szikra Istvan Says:
March 11th, 2008 at 4:19 am
Do any or all of you have ATI video card and a little ati icon on the tray?
Disable it!
Display Properties > Settings > Advanced > Options > “Show ATI icon on taskbar”
Solved the problem here.
I had similar problems back in the day with Terminal Services Client, ATI tray icon caused some freaky keyboard problems. After a month troubleshooting i found the solution. It seems to work in this case too.
Hope it helps.