Last November I staffed the HP RemoteFX booth demo at Microsoft TechEd in Berlin (Germany), in which we made a technology demonstration of our upcoming products and solutions for RemoteFX. I had the chance to talk with customers, partners and even competitors about the role of this new technology in the Desktop/Client Virtualization arena. There is definitely a lot of excitement in the market around this new technology that is finally being released today.
I had a professor who would often refer to the “Law of Conservation of Misery”, which simply stated means “the total amount of misery in a system is constant. This implies if something good happens, something equally bad will compensate it. And this strange law had proved true (and burdensome) in client virtualization environments where in order to deliver an anytime, anywhere, reliable, best managed desktop, it came at the expense of a relatively poor graphics experience. The graphics used to be compensated by using protocols that could do “multimedia redirection”: a technique where multimedia elements are sent in native formats to the client devices and then played locally. However the “misery” required that the thin client had the right features to render the multimedia which drove the requirements for a not-too-thin client.
Another way to do it is to render the graphics on the host side, compress them and send them down to the client, but the “misery” here is that this consumes additional computing power, therefore reducing the number of supported users per host in a desktop virtualization environment.
The law of conservation of misery that used to apply to client virtualization is now challenged with the Microsoft RemoteFX technology. It allows you to virtualize the GPU on the host side and also use the GPU’s computing power to do the rendering and compression of the graphics that are sent down to the client as fast as possible. But, what type of client? Any type of client able to run the new version of RDP 7.1, which means that even low-end ones will be able to do it. The end result? Client virtualization users will have the opportunity to access rich media content and enjoy Windows in Aero mode, as well as to do VDI with high resolution, and with single, dual displays …and beyond. This explains why there is a lot of excitement in the market.
Obviously the GPU capabilities must exist on the server side, and HP has a very mature product that supports this feature since it was first introduced in 2008: the HP Workstation Blade. This is the HP flagship platform for RemoteFX. It is the only server system in the industry that supports desktop and server operating systems/hypervisors and that offers a broad range of factory-integrated and supported NVIDIA GPUs. It can be used in traditional dedicated-remote workstation environments and now as a host in graphics accelerated VDI environments.
In order to simplify the recipe to implement this cool technology, we are announcing the HP-Microsoft Client Virtualization Reference Architecture for up to 1000 users featuring RemoteFX. This is true client virtualization reference architecture in the sense that it incorporates not only VDI, but another very popular computing model: Session Virtualization (aka Server Based Computing). This architecture details two different solutions: one based on the HP ProLiant Workstation Blade ws460c G6, and another one based on the HP ProLiant DL370 G6
So, what does this mean? Basically, the “law of conservation of misery” does not apply to desktop virtualization anymore. Users can enjoy a rich graphics experience, and IT organizations are now able to satisfy the needs of the so-called desktop power users with VDI. And last, but not least important, HP is further differentiating itself from its competitors by paving the way for our customers willing to implement RemoteFX with our Reference Architectures, that take the cost, complexity and risk out of the equation.
Want to learn more? Visit our web page at www.hp.com/go/remotefx
We encourage you to share your comments on this post. Comments are moderated and will be reviewed and posted as promptly as possible during regular business hours.
To ensure your comment is published, please follow our community guidelines.