We are pleased to announce the availability of Remote Desktop Connection 7.0 for downlevel operating systems on Wednesday, October 28th. KB969084 provides a detailed description of available functionality and provides links to the download package. This follows the previous post here that described in detail the functionality available using Remote Desktop Connection 7.0 on Windows 7, Windows Vista, and Windows XP SP3.
The Windows XP SP3 Multilingual User Interface (MUI) package release is also coming soon. Stay tuned for this announcement in a few weeks.
Update: If you have previously installed the fix in KB968358 (You cannot use a mouse to select combo box items in a RemoteApp program that you connect to through Remote Desktop Connection (RDC) 6.1), installing RDC 7.0 will undo the fix. We'll let you know when this is corrected.
Update 2: The Multilingual User Interface (MUI) package for XP SP3 is now available for download. Please follow the KB article 969085 for package description and download information.
Any chance this update will be resolving the issue that's existed for what seems like forever.
In more detail, if one connects to a system that's running dual monitors - all the icons on the desktops of both monitors get shifted to the main monitor and remain so, even after the session is over. Hence when the user gets back to their machine - they find all the icons on the one desktop :/
I would have thought consideration to small nuances like this would have been paid, especially since dual desktops are becoming every more prevalent.
Hope you can help.
Did I understand Gopikrishna correctly, meaning there will be a working way to access RDG/Win2k8 combination with the new client on WinXP SP3, WITHOUT enabling CredSSP?
Scripting the registry change really isn't something we wanna do in multiple customer domains. Extra logon-time VBS scripts always tend to add some more complexity and possible problems anyway..
I have the same problem with 6.1.7600 client on Windows XP Pro SP3 (and CredSSP enabled). I can connect a Windows Server 2003 SP2 TSE session. The desktop appears fine. But if I try to open something, I get a protocol error (without error code) and the RDP client closes. I uninstall KB696084 and everything works fine again.
Works great, Thanks!!!
Echoing the request for a work-around for Windows 2003 Server. Our citrix servers are still 2003, application servers are 2008 and we are having occasional rdp 6.1 application errors...6.0 was a no-go (didn't work nearly so well) so we chose the unsupported variant, which works ok. It would be really nice to use the newer client...
I have a big problem with RDC 7 for XP SP3. It breaks TS Farm (not single TS Server) RemoteAPP SSO!!!
I was able to get farm based SSO to work after installing KB953760. But after installing RDC 7 it went back to requiring double logins! :(. If I uninstall RDC 7 for XP SP3, the SSO to a ts farm works again.
Does anyone know how to get RDC 7.0 to work with RemoteApp SSO?
Using RDC 6.1.7600.16385 (from update KB969084) on XP SP3 connecting to W2003 SP2 R2 TS, local drive mapping no longer works.
I assume Microsoft is aware of the issue(s) with running the updated RDP client on XP SP3 (drive mapping being one of them) because it appears that update KB969084 for XP has been pulled from the Windows Update site as of today.
You seem to have removed one of the most useful display resolutions - 1152 x 864. I used this all the time. It is in version 6x but not in 7. This res means I can have it a Window which is larger and more comfortable than 1024 x 768, yet I can see all of the remote desktop without having to maximize the Window area totally obscureing my desktop at 1280 x 1024. This is my preferred way of working - and I suspect I am not the only one. Please add back in to the choice of display resolutons!!!
@ Mike H - Mike, you can launch your remote desktop sessions in this resolution via:
mstsc.exe /w:1152 /h:864 /v:ServerName
I hope this helps.
Microsoft MVP - RDS
Is a separate client for Windows Embedded going to be provided? Birectional audio on a thin client would be awesome.
We too have problems with Windows XP machiens connecting to our 2008 Server via a TS gateway with error "Your computer can't connect to the remote computer because an error occured on the remote computer that you want to connect to. Contact your network administrator for assistance." Removing the update resolves the issue.
I just require to remove rdc from an XP sp3 installation because it just doesnt work ..... how?
Any ideas when the drop down issue will be fixed from KB968358? Unfortanatly RDC 7.0 installed on 300+ of our computers and and this broke the previous KB968358 fix which alows Axapta 3.0 to work properly with Drop Downs from a 2008 Terminal Server.
Still wondering about a client for 64 bit Windows XP... we have a number of remote users with that configuration. Status? Alternative?
I have to second Mike H's comment, 1152 x 864 is a very convenient resolution for those of us with 1280 x 1024 monitors (ie, most server monitors), and I'd very much like it back.
Patrick Rouse commented on a way to obtain that resolution via the command line, but that doesn't help folks who use .RDP file settings or who use the MMC Remote Console add-in.