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.
Please release the RDP 7.0 Client also for Windows Server 2003!!!!
Please give us back Console Access. Things don't quite work the same with the new /admin switch, and it breaks some installation routines among other things. It also makes remote troubleshooting difficult. Without this, hundreds of companies will lose the ability to properly troubleshoot issues, and in some cases, even the ability to perform remote server patching, etc. which used to work just fine.
How can you tell wich version is RDC 7.0?
RDC 7.0 on XP/Vista version is 6.1.7600. "7600" is the RTM windows 7 build. Additionally, It would also say that RDP 7.0 protocol is supported.
Connectivity through RDG fails on the first attempt:
Folks, this happens when CredSSP is not turned-OFF. We are working on this issue. In the meanwhile, please work-around with CredSSP turned-ON. I shall post an update to the KB on this issue.
remote control (tsadmin.exe) gives strange errors:
Its unclear. Can you tell us the issues you are seeing?
Yep, you're right, after upgrading RDC 7.0 you MUST enable CredSSP through the registry hack which is awful. I am going to have to build an executable to edit these registry settings for our clients running XP SP3.
Although in the KB article which tells you how to do this (http://support.microsoft.com/default.aspx/kb/951608) there is also a section at the bottom which tells you how to configure Single-Sign On for XP SP3. Does this mean it uses the web credentials or the current logged on user credentials (it makes no reference to Web Access so I presume the latter, but then that would be credential delegation rather than default credentials, confusing!? - will test now...).
Hi, sorry me again. One thing I noticed you may be able to help with is why the MSI deployed RDP files work perfectly but when clicking on the icon when logged into RD Web Access you get the same error?
- It is as though going through the Web Access route seems to somehow ignore CredSSP (or at least the registry changes) and gives exactly the same error.
At least with 6.1 we could install on Server 2003 by using Compatibility Mode to emulate XP. Now that the installer requires XP SP3, this trick no longer works.
It is a very common configuration for us to have a Server 2003 machine exposed for remote admin and to then run MSTSC to remote to resources within the client network.
Even an unofficial work-around as with 6.1 would be greatly appreciated.
I'm receiving the 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.
After I install RDC 7.0 on a Windows Vista machine. I'm testing remote access to our environment, so the Vista machine is unmanaged / not joined to my domain.
Obviously CredSSP is enabled in Windows Vista, so I'm not sure what else to really do. Can anyone else confirm this behavior?
Forgot to mention that I receive the above error when clicking on a RemoteApp in RDS Web Access on Server 2008 R2.
I'm executing the one-time password (OTP) scenario with ISA 2006 SP1. I'm going through RDS Gateway and Session Broker as well.
The following script allows you to configure CredSSP on the client.
Please note this is a sample script. Hence, test this script before usage.
The SSO describe by KB 951608 is using "Saved credential method"
This is a bit off-topic for this post, but I am wondering if you could provide more information as to why you are looking for the console access! Windows Server 2008 onwards, there is no special session for the console (unlike server 2003, where session 0 was always console session and you could positively identify the session you want to connect to using /console).
If you could provide more information about "break in some installation routines" or provide scenario, where remote troubleshooting is difficult without physically logging onto console, that would help us understand the concern better.
Any update on...
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.
I have an app which is shared via TS RemoteApp. Before TS RemoteApp, I used remote desktop to connect to server 2003 and run the app. Now I've moved the app to Server2008 with TS RemoteApp, the print alignment is off again. Took me a while to get the app printing with correct print drivers (alignment). Can anyone share how to correctly setup printers (network) to have TS RemoteApp print correctly.