Remote Desktop Services (Terminal Services) Team Blog

Will there be a new client package for Windows Server 2003?

In previous comment it should say "About" not "Anout". Sorry.

I second the question raised by Patric... If this is RDC 7.0 - why is the shell version listed as 6.1.7100?

Please support 64-bit Windows XP TS team.

What's the status of RDP 7 on Windows XP Professional x64 Edition?

Removing RDC 7.0 resolves the issues that I reported above.  

To answer the question about how to uninstall RDC 7.0, from Add/Remove programs, click Show updates, find Hotfix for Windows XP (KB969084), click remove.

Client -> XP+SP3+all fixes

Serwer -> 2003+all fixes

When I try remote control (tsadmin.exe) I have strange errors. When downgrade to Kb925876 everything works again.

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.

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.

@Gopikrishna

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...).

Thanks,

Ross

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.

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.

@Ross

The SSO describe by KB 951608 is using "Saved credential method"

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.

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.

Cheers.

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.

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?

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.

@ 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.

Patrick Rouse

Microsoft MVP - RDS

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.  

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.

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.

Has anyone got an update on this issue, were experiencing similar symptoms. Even with credssp on we are having difficulty opening RemoteApps , perhaps a 20% to 30% sucess rate with RD v6.1 has no problems

Problem with Windows XP Home edition retail build updated to SP3 with latest updates 11/01/10.

The problem is that when connecting through a Windows 2008 R2 RD Gateway to a Windows 2008 R2 RD Broker to the Windows 2008 R2 RDHS servers the Windows XP Home edition client  we are not able to save the credentials at logon to the RD Gateway Server and RDHS so that the user only gets prompted once for security credentials and not twice.

We have upgrade the RDP client from 6.1 in SP3 to the one listed here RDP 7.0, this caused the tick box normally to enable or disable saving credentials to disappear. After reading some of the posts we added the registry keys for credssp.dll and tspkg which restored the tick box.

Now however if you try to tick the box when and entering your credential at the authentication dialog box simply causes the dialog to re present itself with your username and blank password. This loops until you decided not to tick “save credentials” which moves you onto the next “second” authentication dialog box for the RDHS server, also with the ability to save the credentials again which if you tick also goes in a loop until you untick. Once unticked it you login as expected.

Summary:

--Windows XP Home Edition SP3, RDP 7.0, Credssp.dll & tspkg reg keys

--2 authentication dialog boxes with option to save credential

--Authentication loops unless save credentials unticked

--Logs in successfully.

Windows XP Pro Sp2+ and Vsita Sp1+ and Windows 7 works fine without issue

It's really easy to install the RDP 7.0 client on Windows server 2003.

Extract the WindowsXP-KB969084-x86-enu.exe with winrar.

Open update.inf with notepad and edit

MinNtServicePackVersion   = 768

and

ThisServicePackVersion    = 768

to value 512 and save.

Then you run update.exe and save the update.inf with the restored values of 768 before you get the error message "setup could not verify the integrity of the update.inf." Depending on your machine you might need to be quick.

After saving you can click next and hey there you have RDP 7.0 ready to use in Windows server 2003.