Windows 7 with RDP7: Best OS for VDI

Windows 7 with RDP7: Best OS for VDI

  • Comments 20

In the minds of IT admins looking to enable a virtual desktop infrastructure (VDI) environment, Windows XP has by far been the preferred OS running in the VMs. However, with the arrival of Windows 7, IT admins have several important reasons, as outlined in this blog, to reconsider. In fact, an upcoming RDP Performance Whitepaper will provide a rich set of data to convince even the most skeptical critics that Windows 7, with its enhanced user experience, performance on the wire, and security outshines Windows XP as the virtualized guest OS of choice.

When users connect to a Windows 7 VM, the RDP7 protocol will be used to communicate between client and VM if RDP 7 or Remote Desktop Connection 7 (RDC7) client is used. RDC7 client is offered on variety of OSs, including XPSP3, Vista SP1 and Vista SP2 and the same client is part of the Windows 7 OS (see blog post for more details: Announcing the availability of Remote Desktop Connection 7.0 for Windows XP SP3, Windows Vista SP1, and Windows Vista SP2 ).

When an RDP 7 client connects to a Windows 7 VM, it can take advantage of all the new features implemented in Windows 7.  However, when the same RDP 7 client connects to a Windows XP VM, it will start talking the 9-year-old RDP 5.2 protocol.

User Experience

To test the user experience improvements that the RDP 7 client provides when connecting to a Windows 7 guest VM, we picked the following scenarios:

  1. Media(.wmv) playing in a remote session with Windows Media Player
    1. A Windows 7 VM will give you an experience that is close to watching the same video locally from your PC
    2. On Windows XP with RDP5.x , the video may degrade to become a “slide show” with audio sync behind
  2. Video playing from any popular site:
    1. You’ll find that with Windows 7 you can enjoy the video content
    2. With Windows XP, the experience is much worse. You may experience the same “slide show” effect as with media .wmv files
  3. Aero graphics (“Aero glass”)
    1. RDP7 with Windows 7 is able to remote Aero for your increased productivity and pleasure, so you don’t need to default to the green field of Windows XP Classic theme.
    2. Windows XP will not be able to provide Aero
  4. Audio chat experience
    1. Windows 7 will provide you with bi-directional audio, i.e. with the chance to reply, not only listen silently to the conversation. Using the microphone on your local device, you will be able to change a monologue to a dialogue
    2. With Windows XP, there will be no microphone input from your client computer
  5. Multimonitor sessions--here the difference is even more pronounced
    1. If you have more than a single monitor when connected to a Windows 7 VM, all of them will be available to your virtual desktop
    2. If you continue to work with Windows XP, only one of the monitors will be used, all others will sit on your table collecting dust
  6. Logon speed
    1. Window 7 Client boots faster; you can initiate logon before the whole OS is booted up.
    2. Windows XP boots slower; you have to wait for the entire OS to boot up before logging on.

Performance

Let’s examine the performance of the RDP 7 protocol compared to the RDP 5.2 protocol of the Windows XP era.

  1. Windows 7 introduced a new codec that compresses bitmaps very well and can also distinguish between text and images, applying different compression techniques with different levels of “lossiness” to text or images. The goal with text is to keep it readable, so lossy compression has to be avoided. With images, the human eye is more forgiving when we allow some lossiness, in order to save bandwidth. Windows XP is using RDP 5.2 bitmap compression, which requires twice as much bandwidth on the wire as the RDP 7 codec and does not have a good dynamic approach for different types of content.
  2. In addition to the bitmap compression improvement, the RDP 7 protocol supports a better byte compression technique that is 3 times more effective for all content from a VM to an RDP 7 client--graphics, print data, audio, clipboard, media, and so on. A Windows XP VM will use an older byte compression algorithm that will not be comparable to the modern compression technique available in RDP 7.
  3. IT admins can prioritize interactive traffic (graphics) higher than non-interactive traffic (print/files/clipboard) by assigning a ratio of available bandwidth to these two categories of traffic. By default in both Windows 7 and Windows XP, 70% of the available bandwidth is given to graphics/interactive data, and 30% to all other content. Only Windows 7 VMs allow admins to control this ratio based on their real needs.

Security

Windows 7 with RDP 7 takes remote session security to the next level. When connecting to a Windows XP VM, a connection will be created before security handshakes are finished:

  1. Windows XP VM does not support Kerberos for client/server and/or user authentication
  2. Windows XP VM does not support Network Layer Authentication (NLA): the remote session can be created even for a rogue user
  3. Windows XP VM, does not support Server Authentication, so this VM can be used by any RDP server to steal user credentials
  4. Windows XP VM does not support Transport Layer Security (TLS) / Secure Sockets Layer (SSL)

Windows 7 VM with RDP 7 supports all of the functionality you need to keep your system more secure: user-server authentication, Single Sign On, and Network Layer Authentication.

Administration

Windows 7 VMs are easier to deploy and administrate than Windows XP VMs.

  1. On Windows 7, there is no need to install an enlightenment package or to reboot VMs after a VDI configuration. On Windows XP, the administrator needs to install the enlightenment package and reboot the VMs before the OS can be accessed by the user
  2. Windows 7 supports offline domain join, which makes the process of joining a VDI VM to a domain faster and less error-prone
  3. Windows 7 has a newer version of sysprep, which enables the administrators to create Windows 7 VMs faster

The take-home message from this blog is simple: if you are considering deploying a VDI environment and you're after the best user experience, performance, security, and administration support, I recommend you use a device running the new RDC7 client connecting to Windows 7 as the desktop OS running in the virtual machines.

Leave a Comment
  • Please add 4 and 5 and type the answer here:
  • Post
  • Hello,

    although Aero Glass remoting look really cool, it requires the client OS to support Aero as well.

    But VDI enables customers to use thin clients. Since there is no Windows Embedded Standard with Aero support (yet), the scenario hardly makes sense. Using a fat client for VDI is way too expensive.

    Nevertheless, Aero Glass remoting will be awesome as soon as thin client support it and customers start adopting them. If a user get Aero at home, he will ask for it at work - simply because it looks cool. That's how consumers work.

    I wrote about this stuff here: http://blogs.sepago.de/nicholas/2009/07/29/who-needs-aero-glass-remoting-although-its-cool/

    Regards,

    Nicholas

  • Thanks for the feedback Nicholas. Calista will help bring Aero Glass remoting from Windows 7 based VDI VMs to Windows Embedded based thin clients - http://blogs.msdn.com/rds/archive/2009/02/10/more-details-about-calista-technologies.aspx.

    The key point of this post is that irrespective of the client - rich clients now or thin clients with Calista - Windows 7 as your VDI VM is needed to get enhanced user experience features like Aero Glass remoting. Windows XP VDI VMs cannot provide Aero Glass.

    Thank you

    Gaurav

  • Citrix XenDesktop can be purchased for as low as $95 per user. But VECD is purchased for $110/yr per desktop. Over 3 years, that's $95 for Citrix and $330 for Microsoft. That's a huge discrepancy.

    Also, VECD is per device while XenDesktop is per user. That will cause additional licensing complexity.

    Any plans to fix VECD? Maybe take the Citrix approach where the RDS CAL and the VECD can be combined into one license.

  • Thanks for not publishing my comments that are critical in nature. That's the problem with MS

  • Any plans to port to port RDP 7 to Server 2003 as a client OS? C'mon MS.

  • thanks for censoring my comment...NOT

  • What's the use having a blog when censoring all the comments??

  • Is there any chance to upgrade terminal services in XP SP3 to support RDP7 ? I am connecting to my XP machine from home to office using built-in remote desktop. However any bitmaps (even when watching colorful web sites) in the screen make it unusable...

  • Comments with offensive language may be deleted.  Please re-post your comment bearing this in mind.

  • There are RDP7 clients for >= XP SP3, but to get the features you must be connecting to hosted or remote desktop running Win7 or 2008 R2.

  • To Patrick: OK, i get it, but is there some kind of a hack possible to make XP SP3 act as RDP7 server ? There is some RDP services built in already in XP, so can we upgrade it to version 7? I especially need the bitmaps compression for low bandwidth network and this seems to be improved in RDP7

  • To Patrick: OK, i get it, but is there some kind of a hack possible to make XP SP3 act as RDP7 server ? There is some RDP services built in already in XP, so can we upgrade it to version 7? I especially need the bitmaps compression for low bandwidth network and this seems to be improved in RDP7

  • No, the RDP7 stack is a feature of Win7 & 2008 R2.  One could no more add these to downlevel OS than they could add SQL Server 2008 features to an older version of SQL Server.

  • Please make RDS for Windows XP Professional x64 Edition and Windows Server 2003.

  • Does the new client support seamless integration with the Win7 desktop for pubished applications? (eg: thumbnail previews, flip 3d etc?)

Page 1 of 2 (20 items) 12