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.
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:
Let’s examine the performance of the RDP 7 protocol compared to the RDP 5.2 protocol of the Windows XP era.
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:
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.
Windows 7 VMs are easier to deploy and administrate than Windows XP VMs.
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.
What if a cheap nettop computer (like an Asus eee) was loaded up with Windows 7 starter edition. Could this be the killer thin client? Having all of the needed goodness (WMP 11, RDP 7, etc., but not Aero), it seems that this would interface nicely with RDS and actually be cheaper for SMB users than traditional thin clients from the likes of HP and Wyse.
You are right. Couple with ThinServer Win7 on the server and u have a killer combination
re:Does the new client support seamless integration with the Win7 desktop for pubished applications? (eg: thumbnail previews, flip 3d etc?)
You are talking about Aero specific features. This functionality is supported from Win7 RDP7 client connected to Win7 desktop or Windows 2008 R2 server.
Still no RDP 7.0 (or 6.1 for that matter) for XP x64 or Server 2003 (x86 or x64, although 6.1 for x86 works via compatiblility mode install).
hyper-v on server 2008 r2 with windows 7 vm.
For me, using rdp, WMP 12 won't play a wmv with mstsc some.rdp /multimonitor. It only plays audio, not video. It also won't play if desktop composition is checked. This took me a while to trial and error, so I'm noting it here. It works ok without multimon or desktop composition.
Does everyone have the same problem? Anybody got a fix?