Remote Desktop Protocol 8.0 Update for Windows 7 SP1: Enabling a great WAN user experience for Windows 7 SP1 virtual desktops

Remote Desktop Protocol 8.0 Update for Windows 7 SP1: Enabling a great WAN user experience for Windows 7 SP1 virtual desktops

Rate This
  • Comments 25

Hello everyone…

I’m Shanmugam Kulandaivel, a Senior Program Manager in the Remote Desktop Virtualization team. Today, on the Windows For Your Business Blog, Karri Alexion-Tiernan announced additional information on the Remote Desktop Protocol 8.0 Update for Windows 7 SP1. This is exciting news and I’d like to talk about some of the functionality you will see when it is available for download in late Q4 CY2012.

As many of you already know, a salient feature of Windows Server 2012 and Windows 8 is the ability to deliver a rich user experience for remote desktop users on corporate LAN and WAN networks. Thanks to RemoteFX and Remote Desktop Protocol 8.0 (RDP 8.0) in Windows 8, customers can deploy Windows 8 virtual desktops using Windows Server 2012 Remote Desktop Virtualization Host and support users on low bandwidth, high latency networks such as work from home users and branch office users.

Can customers deploy Windows 7 as the VDI guest operating system on Windows Server 2012 and deliver a great experience to users on WAN networks? Absolutely yes! Read on to learn how.

The RDP 8.0 update will enable RDP 8.0 (including all the RemoteFX enhancements in Windows 8 that make RDP 8.0 the protocol of choice for VDI) on Windows 7 Service Pack 1. Specifically, the update will provide the following capabilities.

Client access devices running Windows 7 SP1 and Windows Server 2008 R2 will benefit from:

  • Remote Desktop Connection 8.0 Client: Remote Desktop Connection 8.0 client that is compatible with RDP 8.0 and allows users to use new features in RDP 8.0.
  • Dynamic In-Session USB Redirection: Enables users to select USB devices for redirection even in the middle of a remote session.
  • Improved single sign on experience for Remote Desktop Web Access: Simplifies and significantly enhances end user experience by enabling users to provide their user name and password just once when connecting to IT published apps and desktops. Users are not asked to provide their username and password for subsequent connections.
  • Reconnect for RemoteApp and Desktop Connections: Enables end users to easily disconnect and reconnect to IT published apps and desktops.
  • Support for Lync 2013 in VDI : Enables end users to have a fast and fluid video conferencing experience with Lync 2013 in their virtual desktops.
  • Support for Nested Sessions :Support for running a Remote Desktop Connection session within another Remote Desktop Connection session

Windows 7 SP1 virtual desktops running in the datacenter will benefit from:

  • RemoteFX for WAN: Enables end users even on WAN to have a fast and fluid experience by employing advanced techniques such as intelligent and adaptive UDP transports, network loss tolerance and recovery, etc.
  • RemoteFX Network Auto Detect: Automatically detects network characteristics and optimizes user experience accordingly.
  • RemoteFX Adaptive Graphics: Delivers a rich graphics experience that dynamically adapts to server load, client access device load and network characteristics.
  • RemoteFX Media Streaming: Enables end users to get a smooth media experience even on WAN networks for all media content formats.
  • RemoteFX USB Redirection for non VGPU Virtual desktops: Enables users to use their USB devices with IT provided RemoteApp applications and remote desktops.
  • Support for Nested Sessions: Support for running a Remote Desktop Connection session within another Remote Desktop Connection session.
  • Performance counters for monitoring user experience. Watch out for a blog post on this topic with more details.

Also, the support for following features on Windows 7 virtual desktops is natively built into Windows Server 2012 (Remote Desktop Services “What’s New” in Windows Server 2012 Release Candidate):

· User Profile Disks: Simplifies storing and managing user’s personal documents, settings, and configurations for a virtual desktop collection.

· Simplified Administration: Allows creation, patching and other management of Windows 7 virtual desktop collection.

In summary, this update makes Windows 7 SP1 a first class client access device operating system and guest operating system on Windows Server 2012 VDI deployments with WAN support. The following table summarizes the key features and compatibility for Windows 7 SP1 and Windows 8 guests.


Windows 7 SP1 with RDP 8.0 Update virtual desktops

Windows 8 virtual desktops

WAN support: RemoteFX for WAN

Graphics and Multimedia Experience:

RemoteFX Adaptive Graphics and RemoteFX Media Streaming


RemoteFX USB Redirection

Single Sign On (SSO)

User Profile Disks

Simplified administration

Lync 2013 in VDI

Some questions that you might have…

When will the update be made available? The update will be available sometime in the fourth quarter of calendar year 2012. We recognize the excitement and are working hard on releasing the update to web.

Are the RemoteFX and RDP 8.0 enhancements available for Windows Server 2008 R2 Remote Desktop Session Host? No, the RemoteFX and RDP 8.0 enhancements are not available for Windows Server 2008 R2 Session Host. However, a Windows Server 2008 R2 computer acting as a client access device will still get the Remote Desktop Connection 8.0 client and thereby get the benefits listed in the ‘client access devices’ section earlier.

Will Windows Embedded Standard 7 SP1 based thin client devices get the RDP 8.0 Update as well? We are working with thin client OEMs and they will make specific information available when they have more information to share.

What is the level of support for Windows XP SP3 Clients? The RDP 8.0 Update will not be available for computers running Windows XP SP3. Customers can instead deploy Remote Desktop Connection 7.0 update for Windows XP (RDC 7.0 Update), and users on such clients will be able to connect to Windows Server 2012 session-based desktops and virtual machine-based desktops. The user experience will be at the same level as that of using a Windows XP SP3 with RDC 7.0 Update client to connect to an RD Session Host server running Windows Server 2008 R2 or a computer running Windows 7 SP1.

I want to summarize by saying that the RDP 8.0 Update for Windows 7 SP1 completes our goal for Windows Server 2012 Remote Desktop Services: WAN ready VDI option for Windows Server customers. Thanks for reading.

To enable RDP 8.0 and experience all the new WAN improvements when connecting to Windows 7, you need to set the Enable RDP 8.0 Group Policy setting after installing the required update packages. For more information, see the “Installation instructions” section of

NOTE: Questions and comments are welcome. For all technical questions and troubleshooting, please post a new thread in the RDS & TS Forum.

Leave a Comment
  • Please add 8 and 1 and type the answer here:
  • Post
  • I run a few remote desktop sessions host servers for some WAN offices using remote desktop gateway, with RDP 7.1 as the connecting client, the servers at head office run Windows 2008R2 SP1 on Hyper-V hosts and RAM is not an issue.  The constant issue I have with the WAN offices are terrible audio/video play back, terrible website viewing & viewing / scrolling PDF's, this is regardless of their internet connection.  I set the experience tab fo the RDP protocol with many different options which none help.  Any thoughts to improve WAN offices remote desktop experience?

  • Is there any support for this on Windows 2008 Server on a TS Gateway?  No not R2 just 2008.  We have clients that are updating their machines and not able to access the gateway any longer.

  • Why the loss of some functionality - Aero Glass support (features such as a Flip-3D, the live task bar preview) and shadowing?

  • Does Remote Desktop Access Software Really Work That Well. Inquiring minds want to know. :-)

    <a href=>Remote Desktop Windows 7</a>

    How hard is configuring. Is It easy or do you need a PHD in I.T. to get it to function properly.

  • I've found that copying and pasting from Windows 2008 TS now only works sporadically with this update.  Has anyone else run into this issue?

  • Does an update still need to be installed for a  Windows Server 2008 R2 computer acting as a client access device ?

  • All the Jazzy Stuff Latter , Please solve the importan thing first.

    A lot of users are suffering from this "Windows 2012 Terminal Server not accepting keyboard input

    " try solving this first.

  • RDP protcol 8.x in Win7, 8, W2k12 - why not W2k8 Session host? This doesn't make sense at all... please add the ability to force 8.x. Win7 to Win7 ok but not connecting to W2k8??? Madness :(

  • Hmm.. RDP is good. But as far as i know it can only be used for remotely accessing computers between computers over same network. For remotely accessing computers over internet, you need to use 3rd party services such as RHUB, Bomgar, Logmein etc.

  • OK Scenario:

    Host : a Windows 7 Enterprise with SP1, configured as a VM on a 2012R2 Virtualization host with RemoteFX d3d adapter component AND RDP8.0 installed and configured per this article:

    Client : a Windows 7 Professional SP1 with an updated client (Shell Version 6.3.9600, Control Version 6.3.9600, Remote Desktop Protocol 8.1 Suppoerted)


    1.the windows 7 host used to add log entries into the RemoteDesktop-TSCore log Admin section upon clients connecting, per this article:

    but it is not doing it anymore after upgrading the RDP to 8. no signs of Event ID 2 in the Microsoft-Windows-RemoteDesktopServices-RdpCoreTS/Admin

    2.the client is unable to RDP into the host if the "speed" of the client (the "experience" tab) is set to anything but the "LAN 10MB". it used to work with "Automatically Detect" settings before, unless I manually changed it per the above technet article to activate RemoteFX (read the square at the middle-bottom of the article).now, even if I switch it back to automatic speed detection or some other speed, it goes just up to the "Estimating speed and quality" connection phase and then suddenly quits. the only way to get to the remote desktop is to set it back to "LAN 10" manually.

    the Remote host just has some "warnings" regarding the previous (non-LAN) attempts, saying that the client is not capable of RemoteFX so RDP Graphic module will be used; no "errors". but as I told you, the client simply quits after the speed estimation.

Page 2 of 2 (25 items) 12