We've released the new version of the Remote Desktop Client corresponding to Vista. Here are some of the new features:
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)
Remote Desktop Connection (Terminal Services Client 6.0) for Windows Server 2003 x64 Edition (KB925876)
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)
Localized versions and the Multi-User Interface Pack will be released in the coming months.
Until this update RDP worked fine for us. Would really suck if because of an update we had to go to something else. Hopefully stopped the roll out soon enough to minimize the number of users affected.
After upgrading to the TS 6.0 Client on Windows XP-SP2 the smartcard authentication is not working properly anymore.
After I select my Smartcard certificate and enter the PIN for my SafeNet Rainbow 2032 token, the server (Windows 2003SP1 with SSL Security layer and SafeNet Auth solution 4.7 -MU20) prompts me for my username and password again.
The Logon Settings on the server are set to "Use client-provided logon information".
The "Alternative Name" on my cert is correct and with the Windows XP Sp2 TS client I can connect without the username/password prompt.
With the TS 5.2 client from Windows 2003 Sp1 I get the best usuability on Windows XP Sp2, since smartcard logon detects the right cert automatically and SSL security works without any problems.
Is there something I can tweak on the TS 6.0 client to make the smartcard authentication working again?
Thanks for any help in advance.
Thanks for the response on this.
The error message is:
mstc.exe - application error
the instruction at 0x00c8fd50 referenced memory at 0x0000008. the memory could not be read.
all of our users get this when they exit an rdp session.
Can you please reconfirm that the Smart cards checkbox in mstsc -> Options -> Local Resources -> More... section is checked? If not, please check it and try again.
Thanks for your response. Don't think you could change the compatibility settings on 5.1 but that worked OK without any configuration so don't know why 6.0 doesn't. Looks like I will have to roll back to 5.1 on all my workstations - still there's only 50 to do!
Upgraded to the latest TS client and we are now having problems with Citrix logons. I traced this down to using the new TS client to logon to the Citrix Server consoles. When a qualified user id is entered in the logon dialog (domain or machine name) then the DefaultDomainName entry is changed in the WinLogon key. Users don't notice that the domain name box is now defaulting the the local machine name and so fail to logon.
Had to manually change the WinLogon keys back and NOT pass credentials to the TS client.
Is this working as designed???
I am also receiving the error:"The client cannot connect. You are already connected to the console of this compu........."
I only receive it when trying to connect to the DC, I have two member servers that I can connect to with no problem.
I updated to TSC 6 on this laptop i am currently on only, every other computer on the network still runs 5.1. When I attempt to connect to any other workstation I get the error "this computer can't connect to the remote computer. try connecting again." if i try to connect via IP. If I try to connect via DNS name says "rdp cannot find remote computer. contact blah blah blah" Is it because the only client that is this laptop and the older versions arent compatible? or am I missing something entirely.
So this version of mstsc wants the username/password first before even connecting to the remote server. Is there anyway to configure it to behave the old way (i.e. connect first, then logon with username/password/domain)?
initial connect is now extremely slow - approx. 10 seconds. Can I speed it up?
I discovered, that after launcing RDC 6.0, netbios queries start for "LOCALMACHINE <00>".
Disabling netbios helps to dismiss startup delay, but these netbios queries happen only since installing RDC 6.0.
Put us down for the mstsc.exe - Application Error
The Instruction at "0x00d0fd50" reference memory at "0x00000008". The memory could not be "read".
Click on OK to terminate the program
About 90% of our users get this message anytime they disconnect at Terminal server session - from any server. Graceful Logoff, or just closing the window. Those who get the error - get it every time.
Anyone have a fix for this? Please?
How do I stop it from asking for Server Authentication credentials entirely?
We only use this stupid program in our office where there is exactly zero chance that anyone is going to connect to the wrong server, so the added step of entering credentials *before* logging into anything has been very poorly received by our confused staff. Since I'm the one fielding all the calls on this, I am not at all happy that this was enabled by default with no obvious mechanism to disable it.
You can always roll back to the 5.1 or 5.2 versions of mstsc.exe.
Newer means newer, and often different, and almost never pleasing to everyone. I understand you are frustrated, but as an IT Professional it is your responsibility to test new software before deploying it. I've been testing the 6.x RDP Client for some time and it has new features that would make some want to use it, i.e. screen size > 1600x1200, 32 bit color, saved credentials... but I've yet to tell any of my clients to update their computers.
I don't accept the response 'use the old version'. The problem with that tactic is that it assumes that I can use it forever. It is never possible to simply 'go back' and use an older version, especially where MS is concerned. Having played with the beta, I happen to know for a certainty that the TSC built into Vista has this same anti-feature. Am I to assume that you expect me to use WinXP forever too? Are you telling me I can rely on MS to support WinXP from now to eternity?
How hard can it be for MS to figure out that security means giving control to people who know how to use it, not simply taking control away? I swear, MS is worse than BigBrother.
Does anyone have a *real* answer to my problem?