TS connection experience improvements based on RDP 6.0 client customer feedback

TS connection experience improvements based on RDP 6.0 client customer feedback

Many users have downloaded the RDP 6.0 TS client through Windows update since it was released. We have received significant feedback on the RDP 6.0 client -- both on what you liked and what you disliked. In this post we want to let you know that we heard you and show you how your continued feedback helped us to improve the TS client connection experience for all of our users.

The improvements discussed in the post will be available to the public as part of the next planned TS client update. I will update this blog with a link to the new beta client download page once it is released. In the meantime, I thought I would provide an update to our TS user community that we heard your feedback, and we have made improvements in the next beta of the RDP client.

The improvements we made in the beta RDP client are discussed and organized by feedback topics. I have grouped your most common feedback into one of these seven buckets. Of course, additional comments/feedback is appreciated.

Feedback #1:  When using Remote Desktop Client 6.0 to connect to a computer running Windows 2003 Windows 2000, some users are forced to enter credentials (user name and password) twice in a row - once at the TS client, and again at TS server.

This blog post provides details on cause for these problems and possible workarounds.  To better address the problems mitigated by these workarounds, we changed the design for the next version as summarized by the following table:

Client OS with RDP 6.1

Target TS Server OS

Prompt for credentials

Windows Vista and Windows Longhorn

Windows Longhorn and Windows Vista

Always at TS client side

Windows XP, Windows 2003, and Windows 2000

Windows Longhorn and Windows Vista

Always at TS Server side

Windows Vista, Windows XP, Windows 2003, and Windows 2000

Windows XP, Windows 2003, and Windows 2000

Always at TS server side

With this design change, users will not be prompted for credentials twice anymore, provided they have installed the latest RDP client.

Feedback #2:  Saved credentials (user name, password) do not work. I don't know how to edit or delete my saved credentials.

This blog post provides details on the cause of these problems and possible workarounds.  In the new beta RDP client, we have bubbled up the "save" and "edit" options to the top-level UI by showing the logon settings on the TS client UI as shown below. If you need to edit or delete the saved credentials, you can do it directly from this UI instead of clicking the "Options" button and then editing them at the TS client expanded UI.  Remember that saved credentials are per target computer name. This means whenever you select a different computer name, it will tell you which user name and credentials it is going to use for the remote connection.

Whenever you or your administrator enable group policy (GP) settings to use the currently logged on Windows credentials to provide a single sign-on experience for a given terminal server, you will see this status as shown below.

When TS client has no saved credentials for the selected target computer, it will show the appropriate status as shown below.

Feedback #3: RDP 6.0 client provides no easy way to save credentials for the target server similar to what we had in RDP 5.0 client.

In the RDP 6.0 client, we removed the option to save credentials (user name and password) in the RDP file. If you need your RDP 6.0 client to remember your logon credentials, when you connect to Windows Longhorn TS server or Windows Vista, select the "Remember my credentials" checkbox in the credential prompt UI shown below.

 

This will store the credentials in Windows credential manager. Next time, when you connect to the same TS server, your saved credentials will be used automatically, and you will not be prompted for credentials. 

 

What about storing credentials for Windows Server 2003 or Windows 2000 Server TS connections?  In the new beta RDP client, we have provided an "Allow me to save credentials" checkbox at the TS client for pre-Longhorn terminal servers. This checkbox will be visible to you only when the TS client doesn't have saved credentials for the target computer. When you select this checkbox, you will be prompted for credentials at the TS client side once, even though your target computer is Windows 2000 or 2003 server, but when you enter the credentials, it will automatically save the credentials for you at the TS client computer. Next time, when you connect to a Windows 2000 or 2003 server, your saved credentials will be used automatically.

 

To see this checkbox, you need to click on the "Options" buttons in the TS client. Here is the expanded TS client UI with the "Allow me to save credentials" checkbox.

Important note:  Whenever your saved credentials (user name and password) have expired for a target TS server running Windows 2003 or Windows 2000, the target TS server will prompt for credentials again using Winlogon UI but the TS client will not be automatically updated with your newly entered credentials. When this happens, you need to manually edit the saved credentials on the TS client. Note that this is the same behavior as when connecting to a Windows 2000 or Windows 2003 Server from a pre-RDP 6.0 client.

Feedback #4:  Credentials entered in TS client get rejected when connecting to Windows Server 2003.

With the design in the new beta RDP client, you will not see this problem anymore because when you connect to Windows Server 2003 or Windows 2000 Server, TS client will not ask for credentials. Refer to Feedback #1 section for more details.

Feedback #5: When connecting to Windows Server 2003 or Windows Server 2000 using RDP 6.0, I am seeing a new credential UI prompt which I don't like.

If you always connect to Windows Server 2003 or Windows Server 2000 using the new beta RDP client, you will not see the new credential prompt anymore, and you will see the typical remote TS server logon screen (Winlogon) as it was in RDP 5.0.

 

 

But if you are connecting to Windows Vista or Windows Longhorn Server using the new beta RDP client from Windows Vista, you will see the new credential prompt at the client side as shown below.

We are showing this new credential UI prompt at the client because we want to do network level authentication for all TS connections to Windows Vista or Windows Longhorn Server. The new CredSSP (Credential Security Service Provider) used in Longhorn TS server provides benefits like RDP data stream protection, RDP port attack surface reduction, and server authentication by default.

Feedback #6:  The pre-populated user name in the credentials dialog does not match the user name that is in the RDP file.

Most users make a TS connection in one of two ways:

  • Style #1 by double-clicking a custom RDP icon published by your admin or a custom RDP file authored by you.
  • Style #2 by launching the "Remote Desktop Connection" icon in the Accessories folder on the Windows Start menu and typing in the remote computer name and user name and then clicking the "Connect" button, or by typing mstsc.exe from a command prompt. Whenever you use this style, TS client uses the default.RDP file.

 

With the RDP 5.0 client, when you use a custom RDP file, it always reads the user name from the file. It is optimized for users following connection style #1. The downside with the RDP 5.0 client is that if your connection style is #2, and you connect to five different TS servers in a day, you will be required to enter the user name again and again because it shows only the most recently used computer name and user name.

 

In RDP 6.0 client, we have optimized it for connection style #2 users but we understand that this approach breaks the "TS Remote Admin" scenario with connection style #1 where two different RDP files with two different user names are used for the same TS server, or where you want to use a custom RDP file with the user name pre-filled for you by your administrator.

 

Here is a proposed new solution to address both these cases. Whenever the TS client uses the default RDP file (this is the case for connection style #2), it will always use the user name hint from the registry. Whenever you use a custom RDP file (this is the case for connection style #1), it will read from the RDP file if it is available, or else it will read the user name hint from the registry. With this proposed solution, we think we'll be able to address both connection styles that customers use and all possible edge scenarios supported by RDP 5.0 clients. Please let us know your feedback.

Feedback #7: How to suppress the ‘Remote Desktop cannot verify the identity of the computer you want to connect to..." security warning message?

This blog post provides details on cause for this problem and possible solution. We are investigating how to make this security warning message valuable while still making it easy for customers to suppress it when it is not needed. We are considering is to provide a checkbox called "Don't ask me again for remote connections to this computer."  If the user selects this checkbox, it will be remembered and will automatically ignore this warning the next time.

 

If the user clicks on this checkbox to suppress the security warning on server authentication failure, and one year later the TS server admin has changed the server certificate or a bad TS server sends an incorrect server certificate, we will show this security warning again until user click again to suppress it. This way, it is suppressed for the same server certificate error messages only. Here is the proposed UI mockup.

 

 

 

 

 

Leave a Comment
  • Please add 2 and 2 and type the answer here:
  • Post
  • both vRD and mRemote caught my eye.  Nice to know other people realize there are simple solutions, rather than having to over-engineer.

    thanx for the comparisons and post!

  • Good God!!!   I accidentally stumbled across RDP 6.1 client today after installing Vista SP1 RC.  

    I feel like I've just been released from prison. That abortion of a client called version 6.0.

    I have only been using it for a few hours but I now feel at least three times as productive as I connect to any of the hundreds of machines across multiple sites and domains that I manage.

    Thank you!  When can we have it stand alone install?

  • 6.1 from Vista SP1 RC seems to have broken the /console parameter in computer names via saved RDP files.  It seems to work from the command line.  Two steps forward, one step back.  Otherwise 6.1 looks nice.

  • Evidently this is by design.  Thanks.  I'll go edit a few dozen .RDP files.

    http://www.ditii.com/2007/12/18/windows-server-2008-remote-administration-changes/

  • You can read about /console parameter in this article:

    http://blogs.msdn.com/ts/archive/2007/12/17/changes-to-remote-administration-in-windows-server-2008.aspx

  • The users experience for Video or flash has always been poor with 5.0 and 6.0 over the internet. I understand this may be the cause of many factors but it would be nice to provide a near desktop experience for small videos and flash website. Will this goal be obtain in v6.1 or vX.XX?

  • There is no difference in video or flash experience between RDP 6.0 and RDP 6.1. It is certainly in our plans to greatly improve multimedia experience in V.next of RDP.

  • I have a secure website using SSL which allows authenticated users to click a link on the web page which returns an RDP file which launches their Remote Desktop Session.  However, the user is still prompted for their password despite the fact that I have included the password hash in the RDP file and I am using SSL with Terminal Services.  What I need is the ability to put user and password in the RDP file and to never be prompted for these items whether or not the user has ever connected to the Terminal Server before. Since the Terminal Servers are hosted in a data centre single sign is not an option. Will the proposed improvements work in this situation?

  • Does anyone know where to download the 6.1 client, and can you use it on XP?

    This usernamehint is killing me since I have some 20 different connections with diff username to the same server (hosting ASP users).

  • I installed windows 2008 server and tried TS connection through windows XP system. First i got error message like " install client active X control" .

    Then i installed Windows XP SP3 in my client system. Now its working fine. Actually we need RDC 6.1 version for TS web access. This one comes with XP SP3 and vista SP1.

  • - Nick

    You can add a deny permission to

    [HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client]

    Permissions... > Advanced > Add... >

    Name: "Everyone"

    Apply Onto: "This Key Only"

    Permissions: SetValue - Deny

    This will stop the app or yourself from permanently unpinning the connection bar.

    Cheers - Mick

  • This also stops any values being created in that key only so change permissions after you add the

    [HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client] "PinConnectionBar"=dword:00000001

    Value

    Cheers - Mick

  • When working with with customer support/setup scenarios it has been a great advantage to be able to script an rdp-file and execute this file WITH credentials in it.

    We have x persons working with y customers on z servers.

    We have a system that enables us to script these credentials into an rdp-file and use them across multiple servers.

    But not any more: TS 6.0 has no support for this.

    Every user has to enter credentials at least once per server - which is pretty stupid.

    Please at least try to make life a little easier for the people who ary trying to use your products professionally.

  • Upgrading from 6.0 to 6.1 made the "CTRL+ALT+RIGHT/LEFT ARROW" key combos be hard-wired to the mstsc and never transmitted.

    This killed apps that had actually use those keys for actually useful purposes.

    Is there any way to remap particular the key combos in mstsc.exe ?

  •   I recently upgraded to XP SP3, which installed RDC 6.1. Since the upgrade, I can no longer use the Full Screen option when connecting remotely using IE6.0 to my desktop via SBS Remote Web Workplace. The remote connection works in Largest Screen (1600x1200)mode, but the Full screen produces a script error on the page. My screen size is 1680x1050.

     Is this a planned reduction in the functionality? Has anyone else experienced this?

Page 6 of 8 (112 items) «45678