Experience Needed

By David Strom  |  Posted 2010-02-04 Print this article Print

The idea of running some of your desktops inside a secure data center has a lot of appeal, but the costs for building the right infrastructure can consume the savings that VDI promises to generate. Here are some guidelines for dealing with these challenges.

See also: Best Practices for Desktop Virtualization

Experience Needed

How much experience should I have with virtual machine image management and deployment tools?

If you’ve never used virtualization, now is the time to gain some experience, because a successful VDI rollout will need to build on this experience. The major VM vendors offer tools that make it easier to make wholesale changes across your desktop images, so you can avoid patching individual desktops one at a time.

VMware offers vSphere and vComposer, and Microsoft’s System Center has various plug-ins to work with Hyper-V and its various VDI elements. There are also third-party tools, including LiquidWareLabs.com and VDIworks.com.

Do I have to beef up my network or storage infrastructure to handle the additional traffic demands of virtual desktops?

You need to plan for worst-case scenarios, such as the beginning of a workday when everyone boots up their virtual desktop. That’s when you have to ensure that there’s enough network capacity to send all these bits down the wire. Some VDI solutions, such as Ericom and Synchron, don’t require storage area networks (SANs) right away for smaller deployments.

With the right deployment of SAN technologies, you can save storage costs by deduplicating the virtual images that are stored on them. This is what J&B Group ended up doing with their NetApp arrays, which saved them a lot of storage capacity since most of the VDI images use similar data structures.

What remote control protocol will I use between the virtual desktop and the client device?

Part of this decision is in understanding your network and the tools that are called “connection brokers,” which determine how to marry a particular remote protocol and a desktop host machine. These tools include Citrix Desktop Broker for Presentation Server, LeoStream Virtual Desktop Connection Broker, Ericom and Quest Software’s Virtual Access Suite.

At the University of Rennes, in northern France, they use the Leostream broker to connect more than 500 virtual desktops across the campus. They deploy a variety of operating systems, including both Windows XP and Linux desktops, and these can boot in a minute because of the way they’ve designed the network. The Leostream broker can also quickly scale up as demand for more connections increases, and it integrates with the university’s single sign-on system. “Our users have to authenticate only once when they connect to our portal,” says Humberto Duarte, the IT department co-director.

Will my users be able to access certain legacy hardware that they are accustomed to using from their PCs?

VDI solutions are notorious in their spotty support for these kinds of applications, and only now are we seeing some improvements that will provide the same rich experience that standard PC users take for granted. “For audio and video using Windows Media Player, our VDI solution works fine,” says Duarte. “But if you are playing a Flash video or using another player, it isn’t that good from either our remote desktops or the thin clients.”

Sometimes, a single application can create deployment problems. Jeff Keith, senior network engineer with Redlands Community Hospital in California, says they “initially went with a thin-client device at the desktop to reduce support costs, but ran into a performance issue with a fetal monitoring application. The driver and connection broker client needed on the virtual machine caused high CPU utilization with this application, so we replaced several thin clients with desktop PCs running this app.”

Since then, the hospital has migrated its VDI solution to a high-performance SAN and will replace its PCs with thin clients. “We don’t anticipate any further performance issues,” Keith adds. “We will continue to evaluate new thin clients and technologies as we move forward with our VDI plan.”

If your plans call for supporting these applications, make sure whatever VDI solution you evaluate can address this issue.

Do I understand all the moving parts of my solution?

Finally, make sure you have scoped out your project and detailed all the parts that will make up your VDI implementation. For example, Microsoft’s VDI solution requires four different Remote Desktop servers: Virtualization Host server, Connection Broker, Remote Desktop server itself and Remote Desktop Web Access server. While these can run concurrently on a single piece of hardware, there’s a lot to keep track of.

Microsoft also requires special licensing, called the Windows Virtual Enterprise Centralized Desktop license, in addition to standard enterprise licenses. VMware’s VDI solution is just as complex because a number of different products must work together. That’s when having a VDI VAR can come in handy.

One alternative is to investigate a “starter kit,” which some vendors have assembled to make deploying VDI easier. These include products from HP, Ericom, Synchron and Quest.

“We looked at others, but Ericom’s ease of use, technical support and Microsoft integration were big reasons we went with them,” says Larry Pickard, director of IT for the San Francisco Theological Seminary. It’s using 80 VDI clients with HyperV, System Center and, eventually, Wyse thin clients.


Submit a Comment

Loading Comments...
eWeek eWeek

Have the latest technology news and resources emailed to you everyday.