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.
I am NOT a Microsoft Employee, but am a customer. NLA is NOT, and as far as I know will not be added as a feature for downlevel OS. The Terminal Server team, as far as I know, does not have control over NLA, as this is not a Terminal Server, Remote Desktop, or RDP specific feature. A 6.1 Remote Desktop Client is in the works, as has been posted several times by Microsoft.
As for your quote of mine being a negative comment, it was not intended as such, but rather as a question.
Before I start some feedback:
NLA - Great
CredSSP - wow, looking forward to not typing my password 100 times a day.
RDP with Aero/Desktop Composition - Fantastic
New Vista logon UI - Fantastic for smartcards, annoying to put in domain name - I only have one domain, why can't it be default?
TSWeb - Hmmm
Using Vista with RDPClient 6.0 the old Win2k3 TSWEb AX errors with "Error in licencing protocol" and will not work.
Using XP with RDPClient 6.0 - works, but annoying "are you sure you want to connect the clipboard, etc?" messages - I NEED A WAY TO TURN THESE OFF, I am the administrator and I don't need to delegate this decision to our users, they don't care, they just want to get on with their job and let someone else look after security. I used to have drives on too but now have to turn off all sharing to give them a good experience and deal with the helpdesk calls when they can't use their USB sticks or clipboard and point them to a special URL with the settings and prompts.
Patrick, I thought you were clear. NLA is not a feature of XP, if you try to connect from XP it wont work. This is why CHARTS are better than paragraphs in some cases, put together a chart or table and everyone will be able to clearly see what works.
Hey, Terminal Services Team, this user humbly requests that you give us a nice link to an article that will show us the recommend ways to make the most secure connection possible to a TS machine. hopefully it will show how to add layers of security and include info on smartcards, certificates, etc.
thanks in advance
I have Windows Vista Business and Office 2007 installed on laptop. I can connect to the first client without any problem. Whenver I try to connect to an additioanl client (different IP) at the same time, Remote desktop crahes with the following signature:
Problem Event Name: APPCRASH
Application Name: mstsc.exe
Application Version: 6.0.6000.16386
Application Timestamp: 4549b425
Fault Module Name: StackHash_2ba6
Fault Module Version: 6.0.6000.16386
Fault Module Timestamp: 4549bdc9
Exception Code: c0000374
Exception Offset: 000af1c9
OS Version: 6.0.6000.2.0.0.256.6
Locale ID: 1033
Additional Information 1: 2ba6
Additional Information 2: edb81efb925a9e212708c512a1009784
Additional Information 3: c16e
Additional Information 4: d1e5272f31bf042e4e228a6256de90ab
Do you have any suggestions to help me?
Does anyone know if there is any shortcut to escape out of the fully maximized terminal services client? It seems the tsc grabs all keys, and it would be nice if there was a way to get out of it, other than using the mouse on the small title bar that appears at the top.
CTRL-ALT-Break will escape out.
I have trouble with the printer redirection on the XP computers with RDC 6.0 installed.
Is there any known issue about this?
Since upgrading to RDP 6 I have had some difficulty accessing my office PC remotely. My office PC is an XP/SP2 Tablet Edition.
The difficulty is connecting. The authentication is ok but during the connection process it appears to get so far (almost done) and then the whole session disappears.
This weekend the same problem was happening. I removed the upgrade with add/remove programs and was able to connect with no difficulty with RDP 5.
Will RDP 6.1 fix this?
For those having problems with loging in twice, do the following.
Click on the options button. Click save (this creates a default rdp in my documents
Op the default rdp with notepad and add a new line "enablecredsspsupport:i:0" at the bottom.
Thank You for your suggestion...Unfortunately, adding the new line to the default rdp did NOT solve the problem.
Here's an odd issue we're experiencing after upgrading to 6.0... On our terminal servers we use an application called Spectrum Messenger made by Telescan. It's an internal IM client and works for our needs. We have two terminal servers, one with 2000 on it (sp4 + up to date) and another with 2003 on it (sp2 + up to date). When a user connects to the 2000 box, there are absolutely no issues. However, if a user connects to the 2003 box AND has Spectrum Messenger running (doesn't matter if they are logged into it or not, as long as it's running) the session becomes slow and very unresponsive. If a user connects with v5.x everything works fine. I've tried turning all of the unnecessary options off (printers, smart cards, lowering the display to 8bit ect.) but the problem still persists. Spectrum Messenger uses port 6767 by the way. If anyone has ANY ideas as to what this could be please let me know.
Pls admit this is a useless bit of software. My remote users still use rdp5.2. Ver6 is useless. Why is it asking me to logon twice and why would I want to log on locally to a server?. Why can't it just work?. MS please listen to your customers. Thank you or at least test the software first. Im waiting for an update me thinks.
Is there any reason that RDC requires CTRL+ALT+DEL to be pressed on the target machine if the Novell Netware client is installed? If I have a user boot a machine up and just leave it I can not login remotely to do any work on it. Now if they press CTRL+ALT+DEL and bring up the Netware log in screen I can get right in no problem. Is this a problem with Netware, RDC, or the OS?
All systems are running XP Pro and the Netware client is 4.91 sp2.
If you have an RDP session within an RDP session, how do you send a CTRL-ALT-DEL to the inner session? CTRL-ALT-DEL is captured by the local machine, CTRL-ALT-END is captured by the first session, how can this be done on the inner session?
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?