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.
Excellant. More Vista goodness for those stuck on XP.
Your links however point to the Microsoft webmail and not to the actual files.
I want so setup a TS Gateway but don't find any help or "How-to"s. Could someone help me, please?
Will any of these new features be available when using the new client to connect to the old version of the RDP server running on XP Pro/Windows 2000?
Thanks for the heads-up. The URLs are fixed.
TS Gateway is part of Longhorn Server. If you have access to the beta, you should be able to find documents on the Microsoft Connect site on how to set up TSG.
Will Terminal Services Gateway be released for Server 2003, or will it only be available on Longhorn Server?
It's a component of Longhorn Server. You can do the equivalent w/ 2000 or 2003 w/ 3rd party tools, i.e. an of the SSL VPN products listed here:
Since updating to Terminal Services Client 6.0, I cannot connect to one of my servers using Remote Desktop from any of my XP SP2 workstations although I can connect from a server running Windows 2003. I get the following message when I access from a workstation even though there are no sessions running on the server.-
The client could not connect. You are already connected to the console of this computer. A new console session cannot be established.
I have two servers running 2003 standard edition SP1, both domain controllers. One I can still access OK, the other I cannot although I can access both servers from each other.
I have proved this to be caused by the update by trying from a workstation before Terminal Services Client was updated and that worked OK but It failed after updating. I have also tried several workstations and different user names but they all fail.
Is this a known problem?
One other point when I can log in the credentials box prompts me with a user name prefixed with the server name rather than the domain name although this still works it is not what I expected. I would prefer the user name to be blank unless I have asked for it to be remembered.
No - the remote computer must be Windows Vista or Windows Server codename "Longhorn".
Will there be a Single Sign On for not-vista clients? As in the Citrix CSG?
Installed the new client, and I must say: Smooooth! Really nice work.
But it keeps saying: "Network Level Authentication not supported" in the about window. How can I enable this feature. My Vista machine has it enabled. Am I doing something wrong?
Remote Desktop Connection 6.0英語版(マルチモニタ対応)
great release but... all my TS users are now getting a mstc.exe application error when every they close the app. has this been reported by anyone?
The msrdp.ocx (3790) was registered and working on all of our machines. We understand that msrdp.ocx is not being updated by RDP 6.0.
However,installing the RDP 6.0 client results in a "Component 'msrdp.ocx' or one of it's dependencies not correctly registered."
As Admin, manually registering the file fixed the problem.
However, we have hundreds clients with user rights that cannot re-register the ocx manually.
Please advise to a possible upcoming fix.