Virtualization: The Emerging Desktop
After acquiring Zen Source, Citrix immediately announced the Zen Desktop. VMware recently announced its VDM 2.0 infrastructure technology for virtualized desktops. With the acquisition of Neoware, HP is steering its efforts towards thin client devices that work with virtualized server environments.
Virtualized desktop technology holds more promise than server-based computing because users are able to experience fully integrated desktop environments. Personalization is relatively easy to set up. This is why Citrix is now in the game. Server-based computing, including Microsoft Terminal Services, is a dying technology.
The full desktop experience has never been fully captured within server-based computing. Virtualized desktops do a better job at making users feel that they are in a more normal environment and users have more control over work environments. By contrast, server-based computing provides a highly controlled and locked-down experience. Users only get access to what administrators deem necessary.
With virtualization, users do not need to have costly, full-power PC systems on their desks. Since the working experience is coming off a virtual environment, users can have inexpensive thin clients and still have the same experience. Thin client devices even provide more access to remote software installations.
Also, no moving parts means more durability. Thin clients are more durable and consume less energy. Thin client technology can also save money in licensing because desktop OSes are not duplicated. Currently, banks and companies with many remote offices are deploying virtual desktop environments because they are cheaper to maintain at remote locations.
"Companies are finding out that virtual desktops are a logical solution for remote locations," said Tom Cecchini, president of Async Associates, Wixom, Mich. He added that technologies like video streaming, Reader Rabbit (in the educational community) and CAD systems have never been able to work on server-based computing. Thin client is changing the old perception by allowing users to have that power at remote sites.
In addition to capacity planning of SANs, solution providers must understand that virtual desktops require more IT management than virtual servers. Application servers rarely are reconfigured or change applications. Therefore, servers are more controllable items for administrators than desktops.
Next: Methodology Methodology
To test whether desktop virtualization can truly match the ordinary PC, CRNtech engineers put together a small virtualized environment and connected it to a thin client.
Neoware's e140 thin client was selected to test the virtualized desktop environment because it comes with ports to access local devices. The device is extremely flexible and works with most virtual OSes on the market. The ports come in handy when users at remote offices need local connectivity to stand-alone peripherals.
Engineers created a virtualized desktop environment using VMware's Virtual Infrastructure (VI) Server 3.0.2 (aka ESX Server) because most thin client devices can connect to it. While PCs and thin client devices can work as virtualized desktops, lightweight thin clients require fewer resources so they are more attractive. Thin clients also are easier to manage because they require no maintenance.
Engineers used Remote Desktop Protocol (RDP) to establish connection between the thin client and server. VMware's internal broker controlled communication between the virtualized OS and the thin client hardware.
Engineers used an HP notebook to create the virtual images and a PC to connect via VMware's Virtual Infrastructure client software to manage connections on the VI Server. Here's how we virtualized the HP notebook:
Setting up the virtual environment
The easiest way to set up a virtual desktop environment is by using a straight RDP connection into a VMware ESX Server. Engineers used an HP DL360 G5 server with 1.66 Intel Quad Core, 2 Gbytes of memory and 70 Gbytes of storage. Local storage was used for installing the virtual server and the guest OS.
VMware's VI Server 3.0.2 was installed on the HP server. VMware provided a starter license for server and VI client software. The default installation took minutes to complete. We did not create any special partitions. We recommend using static IPs and following the naming convention recommended by the installation for the server name. Using DHCP or deviating from the recommendations can cause connection problems.
Preparing to install a virtual OS
After trying an original Windows 2003, the installation failed. Engineers tried using virtual floppies on the remote PC manager running the VI client software. However, the virtual floppy drives did not activate and driver files could not be installed. Engineers do not recommend installing OSes into a virtualized environment. It is easier to use an OS image.
Engineers used VMware's VI client to manage the server from a PC. The VI client uses domain names, so a line was added to the Windows' host file on the PC, so that the VI client could point to the physical IP of the server. Engineers virtualized Windows XP installed on an HP notebook.
Installing XP using VMware Converter
VMware's Converter tool created the virtual image of Windows XP and transferred it to the server. The Converter tool uses a simple wizard to transfer OSes. Engineers decided on a laptop with a clean OS because of the limited storage used in the test server. The XP virtual client was set up to run using two virtual processors and all the storage was dedicated to a single OS image.
Setting up the thin client device
From a hardware standpoint, Neoware's e140 thin client is maintenance free. No setup is required. Everything comes sealed in a box. Most of the e140's upgradable components should be configured before shipping to customers. The e140 comes with upgradable memory slots that support up to 1GB DDR2 flash memory and comes with a powerful Intel VIA processor.
The flash memory allows users to install drivers and even local applications. The flash space comes in handy when companies require VPN or security software running on clients.
The e140 supports DVI at a 1,280x1,024 resolution at 32 bits. Analog video is also supported. The client comes with two serial ports, a parallel port and two USB 2.0 ports. The e140 uses PS/2 for mouse and keyboard. In addition to Ethernet, the e140 provides a PCI expansion slot. Users can install G3 cards via PCI or USB.
The e140 comes with XP embedded, so it has more responsive power when working with multimedia applications. At peak load conditions, the e140 provides better connectivity so that mouse clicks, keyboard strikes, video and sound can keep up with graphical and multimedia applications.
Next: Setting up communication with the server Setting up communication with the server
Nothing is offloaded into the client. The server still does all the processing, since it's a virtual environment. To achieve better performance and responsiveness, thin clients must have enough memory and processing power to react to high RDP-based I/O.
Engineers connected the e140 and the HP server through a small switch and a router. The connection was kept simple to maximize performance.
Because the virtual thin client technology is relatively new, solution providers should develop pilot programs to demonstrate the pros and cons of using this environment. This simple deployment installation works well in small remote offices serving less than 15 users.
Installing and configuring the thin client
Installation of Neoware's e140 is extremely simple and only takes a few minutes. A basic RDP connection is the only connection needed into a virtual server. After turning the e140 on, solution providers need to follow similar steps when activating XP's Remote Desktop Connection.
By navigating to Start, Programs, Accessories and Communications, engineers found the Remote Desktop client connection. The name or the IP address of the virtualized XP Pro is all that's required to establish a connection.
Engineers chose to use the IP of the XP instance running on the ESX Server. The thin client immediately connected to the XP Pro and started working. The ESX Server automatically creates new IP addresses, so solution providers only need to know the new IPs to establish connections.
By clicking the options button in the Remote Desktop Connection, solution providers can configure the thin client environment. On the local resources tab, engineers were able to map local resources with the virtualized desktop. All local resources such as sound, serial ports and USB devices can be sent from the XP instance over to the e140 client.
Working with the thin client
Users can get a nice experience with Neoware's e140. However, engineers suspect that network throughput goes up immediately if local sound is turned on. Sound can only be streamed in native form. Turning on other options such as password configuration are useful when rebooting.
Solution providers can configure user name and password, so that when users turn the client on the system automatically authenticates them. Solution providers can also turn off the local rebooting option so that virtualized clients are never shut down. Turning the thin client off will not shut off the OS.
Overall, the experience was identical to using a local PC. This technology has come a long way since the days of Citrix's ICA. Engineers were able to use local USB external drives to load applications and data into the virtualized environment.
Streamlining thin client deployment
Communication on large-scale thin client deployments is usually segmented in a way that most of the I/O occurs between virtual hosts and SAN environments. Network traffic between hosts and SANs have little effect on thin clients communicating to servers.
Companies should see less traffic on corporate networks when using virtual thin client environments, since the peak network traffic occurs mostly inside data centers. Nonetheless, CRNtech engineers recommend installing 30 to 50 clients in a pilot program to study load on a network before moving forward with a large-scale deployment.
Neoware recommends using VMware tools to extrapolate large-scale network requirements based on pilot programs. More importantly, solution providers need to have adequate experience deploying corporate-wide VMware server solutions.
Neoware also sells a less capable c50, which is a Linux-based thin client with less flash memory. Local thin client devices do not play an important role in this infrastructure.
Migrating software to thin client environments
Application and data migration must be factored in when transitioning users into thin client environments. Solution providers working as virtualized domain managers have to put in place steps to image old desktops or re-deploy applications.
While imaging old machines is the easiest way to migrate users, it is actually harder for solution providers to configure every user after transferring images so that they can conform to new policies in a virtualized environment. Standardizing software on every desktop machine before creating images is the easiest method of migrating software.
Since engineers did not image a system, software was installed via the VI client software and a local USB drive through the e140. Engineers used local access from a management desktop to run CDs. Engineers also used Web connections to download applications. This method is slow and repetitive, so it is only recommended when re-installing software at small remote offices.
Next: Tracking Software Licenses And Scanning Ports Tracking software licenses and scanning ports
Keeping up with licenses is a lot easier in virtualized environments because changes to clients are highly controlled. However, scanning for licenses might not work on virtualized desktops. Make sure that scanning software supports the environment before recommending it to clients.
Neoware sells an image manager utility to stream down full operating systems to devices. The utility eliminates duplication of virtual XP images in a SAN environment. For instance, if 20 users can use a standard XP desktop configuration, copies of the same image do not need to exist on 20 separate spots in a SAN. Only what users create as data needs to be maintained in separate storage locations. The utility can save companies a lot of money on SAN space.
Receiving support for the thin client device
At this time, Neoware works with large consultancies that have a significant amount of experience deploying virtualized environments. With the HP deal, Neoware will be able to provide extensive training services and other packages for partners, but for now the company recommends using large VMware partners.
Neoware recommends that solution providers with little or no experience deploying multitier virtualized servers should subcontract more experienced Neoware partners because large-scale thin client installations on virtual servers are complex and expensive.
Before making recommendations to clients, solution providers should develop simple pilots using straight RDP connections into ESX to showcase the thin client technology, just like the one in this review. In addition, solution providers need to find out if a client's infrastructure can support a large-scale deployment. Neoware sells a Virtual Desktop Infrastructure (VDI) edition of its e140 thin client. The VDI client arrives with an integrated thin client broker with them. In addition to VMware connection brokers, Neoware's VDI technology can connect to the Citrix Dynamic Desktop technology. The company is now testing VMware's Desktop Manager (VDM) solution and plans to support it in the near future.
Beyond RDP, deploying virtualized desktops in the enterprise
Under the hood, brokers make the RDP protocol more functional for virtual environments. Connection brokers provide the connection between virtualized OS instances and thin-client devices. Brokers also manage resources needed to stabilize virtual server connections.
Connection brokers are analogous to software APIs, in the way APIs manage communication between internal software services and end-user applications. In a virtualized environment, brokers provide connectivity between virtual host solutions and specific resources such as guest OSes.
Typically, brokers will generate the resources in a SAN environment that are necessary to have a full XP Pro experience, regardless of the storage needed for each user. Storage requirements for virtualized desktops are more flexible than server-based computing configurations. End-user needs and local applications dictate virtual desktop configurations, so administrators do not have to follow a strict deployment configuration plan.
Connection brokers play an important role in managing connectivity between virtualized environments and physical clients. In addition, connection brokers provide scalability by managing connections on separate servers. Brokers also can make static virtual images more dynamic by providing failover and redundant connectivity.
Because redundancy is crucial in the enterprise, connection broker vendors generally provide their own techniques. On most implementations, however, clients connect to one or more brokers in a failover list, while the brokers have their own failover lists that they can access. Essentially, the brokers extend a lot of the redundancies built inside VMware into the end-user space.
Connection broker space is evolving rapidly due to the crucial role the technology plays in desktop virtualization. VMware and Citrix, for instance, compete with independent software broker vendors such as Leostream and Provision Networks.
While most brokers are usually deployed inside virtualized domains, they are separated by a physical tier. The Leostream solution, for instance, is sold as a VMware virtual appliance. Solution providers can use the appliance or install the Leostream software as a VMware host on a server and turn it into a broker. There is little distinction between brokers and virtual hosts. It is simply a matter of function that distinguishes the two.