Virtual Desktop Infrastructure (VDI) Overview

An architectural overview of VDI, what problems it addresses and caveats to look out for.

Introduction

In the past few years there has been and continues to be a lot industry buzz around virtualization. At this point most are familiar with the concept of server virtualization and consolidation using VMware ESX or Microsoft Virtual Server. Additionally, many have been successful using application virtualization and streaming technologies like Microsoft Softricity Softgrid to address application compatibility, version control and deployment issues. 

VDI is VMware’s designation for the hosting and virtualization of a individual Client OS like Windows XP Professional, Windows Vista or Linux on VMware ESX. The intent is to be able to deploy, secure and manage enterprise desktops in the data center.

For those used to managing server based computing environments, consisting of Windows Terminal Servers and Citrix, managing VDI is definitely similar task. The difference is that instead of managing numerous centralized, multi-user server operating systems, one would be managing potentially hundreds, or thousands of centralized, virtualized single user operating systems.

Architectural Overview

VDI is not one product, but rather a technology consisting of five separate components:

  • Thin Client Computer
    • Most leading thin client manufacturers are coming out with new devices geared toward VDI. The only differences between these devices and their standard thin client device offerings is one or more built-in 3rd Party Connection Brokers. Some are also offering local graphics acceleration where MPEG1 & MPEG2 are rendered locally using the thin client’s display adapter, while others are offering VOIP Soft Phone Support. Although any computer could act as a thin client device, true thin client terminal are more often the choice for VDI and companies don’t want to continue to manage the client OS. Some examples of thin client devices geared towards VDI are:
    • Computer Lab International  MT1500g and MT3500x – Include Provision Networks Remote Desktop Broker Client
    • NEC US100 Palm-Sized Desktop Thin Client Terminal (includes built-in support for NEC’s VOIP Telephony Offering)
    • Neoware e140 – Includes Leostream Virtual Desktop Connection Broker Client
    • Wyse S10-VDI Edition – Includes Leostream Virtual Desktop Connection Broker Client
  • 3rd Party Connection Broker
    • The Connection Broker is the brains of the architecture that determines which Remote Desktop Host (XP Pro or Vista) a user is assigned or connected to. The broker is often a full-blown management product allowing for the automatic deployment and provisioning of Remote Desktop Hosts. There are several vendors offering connection brokers, including the following:
      • ChipPC Virtual Desktop Center
      • Citrix Desktop Broker for Presentation Server
      • Dunes Virtual Desktop Orchestrator (VD-O) and Virtual Service Orchestrator (VS-O)
      • LeoStream Virtual Desktop Connection Broker
      • Propero workSpace
      • Provision Networks Virtual Access Suite (VAS)
  • Virtualized Remote Desktop Host
    • Single User Windows XP Pro, Windows Vista or Linux Client OS Hosts, Virtualized on VMware. Client computers connect to these hosts via remote display protocols like Microsoft RDP, Citrix ICA or NX.
  • VMware Infrastructure 3 Server (VI3)
    • VMware ESX Server software allows for hosting of hardware agnostic Virtual Machines. In the case of VDI, ESX is used to host many Virtual Machines of the Remote Desktop Host Operating Systems.
  • VMware VirtualCenter
    • Software component for managing ESX Server and libraries of Virtual Machines

    Usage Scenarios

    There are many advantages and some disadvantages to any VDI Solution, but some common usage scenarios are:

    • Enterprise Desktop Consolidation – many organizations struggle with management of their client computers. Tasks like procurement of desktop computer hardware, deploying or patching desktop operating systems, updating antivirus signature, securing data, and desktop support become more and more challenging as the size of an organization grows, and the disbursement of employees across multiple locations increases. Replacing all or a bulk of an organization’s computer workstations with expendable thin client terminals and managing the client OS and applications in a centralized location is something most CIOs would love to be able to do.
    • Remote Developer Support – as companies have outsourced all or some of their development efforts, some problems have arisen. How does one provide a remote application developer with a powerful, secure working environment, while protecting the parent organization’s source code and intellectual property. VDI addresses these issues by providing a remote developer with one or a group of virtual machines that can be used, rebooted, destroyed and easily rebuilt. Since the working environment is contained in the corporate data center, source code remains in the hands of the owners.

Advantages of VDI

    • Reduced cost in purchasing desktop computers, as thin clients often last two to three times longer than a desktop computer
    • Centralized Client OS Management
    • Rapid Client Deployment
    • Reduction in desktop support costs
    • Reduction in electricity costs, as thin client computers use only a fraction of amount of energy that is used by a desktop computer. 
    • Improved Data Security
    • Secure Remote Access, as most connection brokers offer an SSL VPN Component and Web Portal
    • Compliance with HIPAA and Sarbanes Oxley (SOX)
    • Fewer Application Compatibility Problems than with Terminal Server and Citrix, as users have their own, single user OS.

Disadvantages of VDI

    • Many items that are problematic in Terminal Server and Citrix environments exist in VDI, i.e.:
      • Printing often requires a 3rd party add-on
      • PDA Sync not supported
      • Scanning is not natively supported
      • Bi-Directional Audio is not natively supported
      • Display protocols not suitable for Graphics Design
      • Requires low-latency connection between the client and virtual infrastructure
    • Requires Enterprise Class Server Hardware and Storage Area Network
    • For VMs permanently assigned to specific users, these machines need to be patched just like a physical client computer.
    • Requires IT Staff skilled with VMware and terminal server. These are usually different staff, as the people using VMware are historically using it for consolidating servers, whereas those skilled with terminal server or Citrix are used to dealing with end user applications and devices. Although talk of VDI does not typically mention terminal server, every XP Pro or Vista Remote Desktop Host is a single user terminal server.
    • Does not scale as well as terminal server, which often can host 25 to 100 users per dual CPU server. VDI will likely scale from 10 to 20 VMs per dual CPU server, depending on how each VM is configured.

    Conclusion

    Virtual Desktop Infrastructure acceptance is becoming more widespread every day. This was evident by the number of VDI sessions at the 2006 VMWORLD Conference, and the percentage of the 7000 attendees that flooded them. There is also no lacking in the number of vendors offering VDI solutions that work with VMware. The question will be which solution to choose, and which solutions still exist a few years from now. As usually happens, new technology causes a lot of companies to jump on the bandwagon. It usually takes a few years to weed out those with solid product and strategy that will continue to grow with the needs of their customers.

    References

    VMware Virtual Desktop Infrastructure

    VMware Virtual Infrastructure 3

    VMware Discussion Forums

    ChipPC Xcalibur Global Management Suite

    Citrix Desktop Broker for Presentation Server

    Dunes VD-O and VS-O

    Leostream Virtual Desktop Connection Broker

    Propero workSpace

    Provision Networks Virtual Access Suite

    Computer Lab International Thin Client Computers

    NEC Thin Client Computers

    Neoware Thin Client Computers

    Wyse WinTerm Thin Client Computers

About Patrick Rouse

Patrick is the West Coast Sales Engineer for Quest Software, Provision Networks Division, and is based out of San Diego, California. He is the author of www.sessioncomputing.com and has been working with Windows Terminal Services since 2000. Patrick has received the Microsoft Most Valuable Professional (MVP) Award for Windows Server – Terminal Server in each year since 2003 and was a presenter at BriForum - Europe in 2006. In 2006 and 2007 Patrick served as an active member of the Citrix Technology Professional Program, until he tendered his resignation when he accepted his current position at Quest Software.

Receive all the latest articles by email!

Get all articles delivered directly to your mailbox as and when they are released on VirtualizationAdmin.com! Choose between receiving instant updates with the Real-Time Article Update, or a monthly summary with the Monthly Article Update. Sign up to the VirtualizationAdmin.com Monthly Newsletter, written by VCP David Davis, containing news, tips, links of the month and much more. Subscribe today and don't miss a thing!



Receive all the latest articles by email!

Receive Real-Time & Monthly VirtualizationAdmin.com article updates in your mailbox. Enter your email below!
Click for Real-Time sample & Monthly sample

Become a VirtualizationAdmin.com member!

Discuss all your Virtualization issues with other experts. Click here to join!

Readers' Choice

What is your preferred Monitoring, Management and Performance solution?

Follow TechGenix on Twitter