Remote Desktop Connection 6.0 client

Last month, the Remote Desktop Connection 6.0 client was released.  It has some nice new features in it, which I've listed below.  Being able to log into a machine on a private network without having to use a VPN sounds really cool (TS Gateway servers), but I haven't been able to try that out.  I found an internal page where folks could sign up for access, but unfortunately the list was full.  Being able to span multiple monitors (mstsc /span) is really nice too.

The change that I like the most right now, though, is a really simple one.  It now uses the same credentials dialog that you see in IE and elsewhere in Windows that lets you save and managed your credentials.  It's a small change, but I've found it really handy.

Remote Desktop Connection 6.0 client

Monitor spanning

Remote Desktop Connection supports high-resolution displays that can be spanned across multiple monitors. However, the total resolution on all monitors must be under 4096 x 2048 pixels. The monitors must have the same resolution. Additionally, the monitors must be aligned side-by-side.

To have the desktop of the remote computer span multiple monitors, type Mstsc /span at a command prompt.

Visual improvements

Remote Desktop Connection now supports 32-bit color and font smoothing.

TS Gateway servers

A TS Gateway server is a type of gateway that enables authorized users to connect to remote computers on a corporate network. These authorized users can connect from any computer by using an Internet connection. TS Gateway uses the Remote Desktop Protocol (RDP) together with the HTTPS protocol to help create a more secure, encrypted connection.

However, earlier versions of Remote Desktop Connection cannot connect to remote computers across firewalls and network address translators. This behavior occurs because port 3389 is typically blocked to enhance network security. Port 3389 is the port that is used for Remote Desktop connections. However, a TS Gateway server uses port 443. Port 443 transmits data through a Secure Sockets Layer (SSL) tunnel.

The advantages of a TS Gateway server are as follows:

  • It enables Remote Desktop connections to a corporate network from the Internet without setting up a virtual private network (VPN) connection.
  • It enables connections to remote computers across firewalls.
  • It helps you share a network connection with other programs that are running on the computer. This enables you to use the Internet service provider (ISP) connection instead of the corporate network to send and receive data over the remote connection.
Network Level Authentication

Network Level Authentication is a new authentication method that finishes user authentication before you establish a full Remote Desktop Connection and the logon screen appears.
The advantages of Network Level Authentication are as follows:

  • It requires fewer remote computer resources at first because remote computer uses a limited number of resources before it authenticates the user. In earlier versions, the remote computer starts a full Remote Desktop Connection.
  • It can help provide better security by reducing the risk of denial of service attacks (a denial of service attack attempts to limit or prevent access to the Internet).
  • It uses remote computer authentication. This helps protect users from connecting to remote computers that are set up for malicious purposes.

Server authentication

In Remote Desktop Connection, server authentication verifies that you are connecting to the correct remote computer or server. This security measure helps prevent you from connecting to a different computer or server than you intend to connect to. This also prevents you from unintentionally exposing confidential information.

Resource redirection

The Remote Desktop Connection 6.0 client update helps you redirect Plug and Play devices that support redirection.

Terminal Services Remote Programs

Remote Programs are a feature of Windows Server Terminal Services that lets client computers connect to a remote computer and use programs that are installed on it. For example, a workplace may have a remote computer to which employees can connect and run Microsoft Word. An administrator must first publish the programs for end-users to access them. The experience is the same as running a program that is installed on the computer.

tags: , , ,

Comments (11)

  1. Buck Hodges says:

    Shortly after I wrote about Remote Desktop Connection 6.0 client , Blake Handler sent me email about

  2. tzagotta says:

    Does Microsoft plan to update the RDC server for Windows Server 2003 R2 so that, when connecting with Vista, the security warning is suppressed?

  3. buckh says:

    tzagotta, the Terminal Server team blog has posted how to give feedback:


  4. Ben says:


    Is there a cmd line switch for RDC where as not to boot a current remote connection when another user tries to connect to the same remote computer?

    We all remote the same server at my work and people will remotely connect and boot you while working. Looking for a way to stop this


  5. buckh says:

    Unfortunately, I don’t know of any such option with mstsc.  The closest thing would be the terminal service managers in Win 2k3 Server where you can specify a remote computer and see the current terminal sessions and their state.


  6. Michelle K says:

    Are there any known issues with RDC 6.0 and the Checkpoint SecuRemote VPN client?

  7. buckh says:

    Unfortunately, I don’t know the answer to that.


  8. Selder says:

    I’ve been searching to get Seamless Windows working with RDC6, would you know if that would be possible?

  9. buckh says:

    I’m not familiar with that, so I looked up seamless windows.  Is this the sort of thing you had in mind?


  10. Anjan says:

    Hi Buck,

           Right now I am using TFS VSTS2010, For making test automation of the application.My software application has the provision to log in into the access gateway. when i recorded all the steps into the TFS. when i play back the action it fails when it just try to open the application by click on the RUN button.

  11. buckh says:

    Anjan, I asked and received the following response from Gautam:

    The three possible matrix –

    a. Test Tool and application UI both on remote machine.  This is completely supported.

    b. Test Tool on host machine and application UI on remote machine.  In this configuration, playback is supported via remote test agent that are running on remote machine but recording is not supported in 2010.

    c. The remote app scenario – this is not supported in VS 2010.

    From his question, I think his scenario is C) which is not supported.


Skip to main content