Tue, August 04, 2009 — CIO —

Despite client virtualization becoming increasingly popular, there is still much confusion about the different technologies and how they will play out in the enterprise. Many firms still believe that client virtualization is a security risk or that a single technology will help them improve manageability, empower remote workers, and virtualize all their applications.

Client virtualization includes four technologies: local desktop virtualization; hosted desktop virtualization; local application virtualization; and hosted application virtualization. Together these technologies provide IT ops professionals better manageability; data and device security; more tools to comply with regulations; and business continuity in the event of disaster, loss, or workforce interruption.

[ For timely virtualization news and expert advice on strategy, see CIO.com's Virtualization Drilldown section. ]

However, in their quest for a shorter sales cycle, vendors often ignore these benefits and make false claims about potential cost savings. As a result, some users fear that client virtualization isn't all it was cracked up to be.

Based on our conversations with IT ops professionals, there are five common misunderstandings about client virtualization:

Myth No. 1: A single technology will meet all of my needs.

Users still expect that a single client virtualization technology will solve all of their problems, from lowering the cost of managing the desktop environment, to providing better remote access, to insuring business continuity. The reality? To meet these objectives, a variety of client virtualization technologies is needed. At a high level, local application virtualization lowers the cost of supporting traditionally installed applications. Hosted application virtualization enables problematic legacy applications to be separated from other applications. Local desktop virtualization allows IT to run a managed desktop environment on an unmanaged machine. Hosted desktop virtualization enables anyone with network connectivity to access a corporate desktop. However, these technologies become much more interesting when you combine them. For example, combining hosted desktop and application virtualization provides the benefits listed above at a lower cost than implementing only one of the technologies.

Myth No. 2: Desktop virtualization is a security risk.

Perhaps you've been told that desktop virtualization is less secure than a physical desktop—in reality, it actually enables a more secure client environment. Most importantly, hosted desktop virtualization removes all of the applications and data from the endpoint device. This means that your data security is immediately improved because you no longer need to worry about devices with sensitive data being lost or stolen. Furthermore, local desktop virtualization allows your IT staffers extensive control of the desktop environment by locking it down more than was possible before. This is made possible by giving the worker access to the host OS, where he or she can install software that is not allowed in the virtualized corporate environment. However, what's most interesting is how desktop virtualization is bringing consumerization to life by making employee-owned devices a secure option in the enterprise. More on this with executives from Google and Citrix at Forrester's Security Forum next month.

Myth No. 3: Virtualizing applications is just another way to package applications.

Many companies think that application virtualization is just another format to package your applications in. Think again. Local application virtualization isolates applications so that, generally speaking, they can't natively interact with other applications. This is a great feature because it prevents application conflicts. On the other hand, it also means that your IT staff responsible for application packaging must understand application interdependencies to get them functional in this format. Because applications run in isolated bubbles, you must explicitly define when applications are permitted to communicate across these boundaries. Most organizations will see hundreds of dependencies that must be defined to assure applications will work in this environment.