Virtualization: The Emerging Desktop

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