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 installed it on a notebook & initially it seemed fine but then there were could not connect...virtual memory.. failures when connecting to XP systems while connection to Win2K systems still worked. How does one regress? It is not listed in Add/Remove programs. Can't see how to uninstall or overinstal...
I also have the failures noted by hgk. I installed this on my XP Pro notebook and I get the error message "Cannot Connect. The Problem might be due to low virtual memory..." If I logon to my notebook as the local machine Administrator I can connect to some but not all servers. As a domain user I cannot connect to anything.
Patrick, are you using ThinPrint? This application crash may have originated in the ThinPrint Client (http://www.thinprint.com/)
You may want to follow up with their technical support, by giving the crash-dump as a starting point.
Or, you can try some of their hotfixes
Also, if you have not already done so, when you hit the error during normal operation, please report the error to Microsoft (you should get a dialog).
I'm also recieving the mstc.exe - application error:
the instruction at 0x10006c40 referenced memory at 0x10006c40. the memory could not be read.
I get this error when I launch mstsc. if I ignore the error I can connect without a problem. I just have to leave the error on screen. What is the process to rollback?
I am also getting the same above error.
In case someone is wondering how to perform a rollback. I was able to rollback the install by installing WinUpdatesList then finding the TSC 6.0 update. Then I found the unistall command line for it. I uninstalled rebooted and an now back to my older 5.1 client.
Yes - it was indeed the thin print cleint. Using the new 7.0 (RDP) version of the Client fixes the issue. No server update required.
Getting "can't connect, low virtual memory" errors when trying to connect from a WinXP laptop to either a XP or Win2003 Server box.
is there any good way to make RDP6.0 work with windows 2000? I have a fair ammount of 2000 servers in my domain still. The "pre-auth" NTLM is not used currently in 2000 so i must enter my cridentials 2x can i turn that off in RDP client or can i fix that in 2000?
Is there any property available to change the text on Connection Bar in fullscreen mode. It default shows the server name. I tried using property FullscreenTitle but its changing only the title text on taskbar when the fullscreen window is minimized.
I have been testing the new RDP client prior to pushcing this update out via WSUS to all of my clients. I have noticed a few problems that I may have when I push this out to my clients and would like to see if anyone has some ideas.
We are a mixed Novell/Microsoft netowrk. All of our users have there home directories on our Novell Server. We use Microsoft for just about everything else. So I have a login script that runs via group policy when the users log into the terminal server that takes there username/password using Native File Access it maps there home directory on the terminal server session to the Netware box. This has worked great. However with the new client it seems that when I start a remote session it prompts me for a username and password (as expected). Lets say I enter useranme 'user' and password 'password. It will login and work. However the next time I connect to that box it tries to put the hostname or ip address of the server in front of the username. The first problem with this is that there is no local account so I can manully change it back to just 'user' instead of '192.168.0.1\user'. Being that we use Active Directory I was like ok, I can just enter either domain\user or user@domain. This works however the problem with this is that my homedirectory does not get mapped because there is no user on our novell box called test\user or email@example.com. I do like a some of the features of the new client but need to find a way around this prior to rolling it out. If not I will get many calls and that is something I don't want. One last side note -- This is why you test software prior to rolling it out.
I have the same problem that Anders talked about. I downloaded the new 6.0 client, but it still says that NLA is not supported. This is on a Windows XP Home with SP2, which the download webpage says is supported. Is there any setting I can change? I tried to connect to a windows vista machine and I can't because I get an error that my computer does not support NLA. Anything I can try? Thanks!
Uninstall RDC 6.0 on Windows XP from Control Panel | Add / Remove Programs. Check the box "Show Updates". Locate update "KB 925876" and uninstall.
Haven't had any problems since uninstalling.
In my opinion, the new Remote Desktop client is seriously broken.
Firstly, there should be an option (other than a hidden RDP file setting) to disable prompting for credentials before connecting. If the server is prompting for credentials anyway, it means I have to enter things twice.
Secondly, I can no longer remote desktop to a XP Pro SP2 machine in my workgroup. Looking at a network trace, the "server" machine is resetting the connection. There's obviously something in the data that's being rejected.
How on Earth was this software allowed to be released when there are so many bugs in it?
Easy to install. Added confusion along with new desired features. No compatability mode by default (assumes I am in the new Longhorn environment), even though it is pushed out via Windows Updates as an update.
Hard to figure out how to uninstall. Leaves new Icon after uninstall, just to continue the confusion I guess. I will try again next year(2008).