1. Virtual Desktop Infrastructure (VDI) David G. Young Jr
Virtual Desktop Infrastructure (VDI) David G. Young Jr. Desktop Systems Engineer

2. Desktop Infrastructure Challenges
Distributed workforce
Mobile & remote workers
Outsourcing & off-shoring
Contract Workers
Limited control of PCs
Patch compliance
Security
Regulatory compliance
Management complexity
Deployment
Support
Security
Focus on PC hardware
Many makes & models
Refresh cycles
Increasingly we are seeing customers facing challenges of a distributed workforce. An increasing number of desktop systems connect to corporate resources from outside corporate offices. These are telecommuters, mobile workers, outsourcing partners and contractors.
<click>
The result is that PC’s are increasingly difficult to control because they are widely distributed and because physical hardware isn’t directly controlled; in particular, this makes it difficult to ensure patch compliance, security, and regulatory compliance such as Sarbanes Oxley, HIPPA patient record confidentiality, and others that require security and record retention
PC hardware considerations occupy an outsized role in desktop infrastructure management; because PC hardware continues to evolve rapidly, organizations are forced to deal with a variety of hardware models, face complicated PC refresh cycles, and handle support problems related to PC hardware variances.
The result is that deployment, support, and security of these varias desktop hardware profiles require inefficient processes, such as manual deployment of physical PC’s, multiple corporate images, extended testing cycles for patch deployments and multiple layers of complex software to ensure proper levels of security.
Reducing Cost
CAPX/OPX 2

3. Typical Corporate Desktops
The corporate desktop PC model has changed little in nearly 2 decades.
User Data
Applications
Operating System
Hardware

4. Typical Corporate Desktops
User Data
In most environments, the components are linked together in ways that are difficult to support and maintain.
Applications
Operating System
Hardware

5. Problems Can Start At Any Layer?
User Data
A problem at one layer often causes a chain reaction that can destroy the whole stack.
Applications
Operating System
Hardware

6. Local Failures Can Mean Data Loss
@%#!
This makes recovery difficult and threatens any locally stored user data and settings.
Most organizations just replace or re-image the whole PC.
User Data
Applications
Operating System
Hardware

7. There has to be a better way…
Could a Virtual Desktop be the answer?

8. VDI Enables Hardware Independence
User Data
Desktop OS Virtualization breaks the link
between the Operating System and any specific
hardware.
Applications
Operating System
Hardware

9. Virtual Desktops Leverage File Servers Effectively
VDI proximity to the data center also enables data isolation through file shares and profile management.
User Data
Applications
Operating System
Hardware

10. File Shares and User Profiles
Data
This allows users to access any VM and always get their data and their profile.
Apps OS
Apps OS
Apps OS
Virtualized Hardware

11. Virtual Machines with Everything
Data
We could install all of the applications that everyone needs in all of the machines. OS OS
Virtualized Hardware

12. Overall System Instability
Data
And the more applications you install, the less stable things tend to get. OS OS
Virtualized Hardware

13. What’s new with VMware View 3
ThinApp
Unified Access
Virtual Printing
Offline Desktop
(experimental)
View Composer
Reduce storage costs
Reduce app conflicts
Increase density
Reduce support costs
Increase laptop security and recovery

14. VMware VDI Solution Overview - Current
Windows XP
Windows Vista
Integrated solution including:
VMware VI3 Enterprise
Virtual Center
Virtual Desktop Manager
Automated provisioning and desktop management
RDP
RDP/
HTTPS
The diagram is a simplified picture of what VMware VDI looks like today, excluding ACE.
There are often people in the audience who are not familiar with our VDM product. If so, take some time to describe the picture.… People often refer to our VDM product as a connection broker. It certainly provides that capability but it provides a number of other powerful features. VDM stands for Virtual Desktop Manager; over time we expect to add additional management capabilities into the product. The four main components of VDM today are (from left to right):
The Windows agent, that provides additional capabilities on Win32 client devices. Today we support access from a range of client devices: PCs, thin clients, Linux machines and Macs. Access from Linux and Mac devices is via a browser; thin clients such as the Wyse S10 are supported natively depending on the device; and, for Win32 clients, we offer a native Windows client. The client incorporates a number of extended features such as USB device support. The USB device support capability is generic so, while we haven’t tested and certified all devices, we are fairly confident most devices will work or can be made to work relatively easily. USB devices that we have tested include USB drives, printers, smart card readers, Blackberries etc; we have also tried it with isochronous devices such as webcams although obviously the performance of such devices is heavily dependent on the network.
The VDM security server. This provides the ability to tunnel traffic (currently VDM only supports RDP) over HTTPS allowing you to access remote desktops securely over insecure networks such as the Internet. You don’t have to use this capability – the product will work over existing SSL VPNs such as those from Cisco or Juniper networks – but it is a useful feature if you don’t have an SSL VPN or wish to roll-out remote access to a wider group of remote users such as people working from home.
The VDM connection server. This establishes and manages connections between end users and virtual desktops. It supports one to one and one to many and many to many scenarios. It is tightly integrated with Virtual Center to provide capabilities such as pool management, suspend and resume.
The VDM agent. The agent runs within the virtual desktops and communicates with the Connection Server. Currently VDM is only qualified for access to desktops on VI3 but we expect to extend this.
Extended Win32 client
DMZ deployment option
Direct from thin clients
Browser on Linux, Mac
Optional integration with RSA SecurID 14 14

15. vClone Direct Storage Cost Savings
Dramatically (90%+) reduce the amount of storage consumed
Increase overall performance due to better storage controller / cache utilization.
25 MB Clone
Ratio
% Savings
25 MB Clone
1:50
85%+
1:100
90%+
25 MB Clone
1:1000
95%+
10 GB OS 15

16. Create Conflict Free Applications
Problem:
Tightly coupled relationships between OS, Applications and Data
Symptoms:
Application Conflicts
Complex Compatibility Test Matrices
Diminished Time to Deployment
Loss of User Productivity
Solution: VMware ThinApp
Agentless application virtualization decouples applications and data from the OS

17. How ThinApp Works:
VMware ThinApp links the application, Virtual Operating System (VOS), file system and registry into a single EXE/MSI file
Application Encapsulation & Isolation
Intercepts file and system calls
Process Loading- start exe from VOS, Launch from host OS (Virtual/Physical).  
DLL Loading. loads DLL dependencies the EXE/DLL/OCX files from archive
Thread & Process Management. VOS tracks all processes and threads inside virtual registry (COM & Utility)
Applications are encapsulated in their own container
Each application is separated from other applications and the operating system
Application virtualization intercepts file and system calls between the application and the OS
Process Loading. The VOS loads a starting EXE file from the Virtual File System and allows it to execute any other EXE directly from the Virtual File System or from the local file system.  
DLL Loading. The VOS loads any DLL dependencies the EXE/DLL/OCX files may have directly from archive when instructed.
Thread & Process Management. The VOS is responsible for keeping track of all processes and threads created inside the virtual machine including out-of-process COM and utility applications. 17

18. Simplify Desktop Delivery & Costs with VDI & ThinApp
Reduce Storage
Reuse templates
Install VM without apps
Simplify Software Delivery (no agents/infrastructure)
Multiple versions of same app installed on VDI image
Many ways to deliver shortcut
Plugs into existing App Mgmt tools w/o infrastructure
Streamline Patch Updates
Modify 1 app for whole environment
In place upgrades
Talk about stages
Generically: integrate, stage, deploy
Specifically: each service could have its own stages, rules re: how to move between them AND the number of “service instances” at each stage to support the process
Lots of duplication of a complex configuration ---- often it is a pain to do all this duplication, so people test on production – BAD !!! This makes it easy and cost-effective to replicate on demand
At the “integrate” step, may have several test configurations being worked on by multiple IT users
Note: there is application development (dev/QA) and then there is the dev/test work that is done in IT to support: operations/configuration management/putting services into production
Talk about the ability to have different stage definitions on a per-service basis
Talk about the “service template” 18 18 18

19. Unified Access Terminal Server Blade PCs Physical PCs Broader USB
Support other platforms accessible by RDP
Terminal Server
Blade PCs
Physical PCs
Increase in device support
Broader USB
Smart Card and CAC
Universal Printer
Blade PCs
Physical
PCs
Terminal
Servers

20. Virtual Printing
Driver Free Printing: No Installation and Maintenance of printer drivers on Virtual Desktops
All necessary printers automatically available
Minimize network utilization up to 98% with advanced print stream compression
High quality printing even over WAN connections
Use of client printer driver rather than complicated server installations
RDP
RDP
No data center installation required
Little to no administrative effort required when creating new Virtual Machines with ThinPrint Output Gateway (ThinPrint’s virtualized printer driver)
No Installation and Maintenance of printer drivers on Virtual Desktops with DRIVER FREE PRINTING
Use of the client printer driver rather than complicated server installations
All necessary printers automatically available with AutoConnect
Minimize network utilization up to 98% with ADVANCED ADAPTIVE COMPRESSION
Supports Windows 2000, XP, Vista – 32bit and x64
Supported Printer Features: Color or B/W, Resolution, Duplex, Trays, Paper Sizes
View Client
View Client 20

21. Offline Desktop Offline VDI
End-users can check-in and check-out their virtual desktops
Administrators can extend security policies to the local computer
Near approximate of the full local experience
Offline VDI

22. Let’s bring it all together…
Unified Access
SVI
Offline
VDM
Linux / Partner Clients VC AD
Clients

23. Don’t Make Big Virtual Machines
Data
So instead of installing everything into huge cumbersome VM’s. OS OS
Virtualized Hardware

24. Create the Smallest VM Possible
Data OS OS OS
We install nothing but the OS from a single template.
Virtualized Hardware

25. Deliver Apps and Data on DemandOS OS OS
And deliver applications on demand from a file server.
Virtualized Hardware

26. Deliver Apps and Data on DemandOS OS OS
Based on what the user actually needs or has permission to use.
Virtualized Hardware

27. A Single Location for Applications
Creating a software repository.
Data
Data V1 OS OS OS
Virtualized Hardware

28. No Distribution Needed
Eliminating the need for software distribution.
Data
Data V2 OS OS OS
Virtualized Hardware

29. Thinapp Blocks System Changes
And we store the sandbox in the profile where it can follow the user.
Thinapp
System Content
Sandbox
User Space
System
Files
Registry

30. Deploying Updates…
User data disks are “connected” to the new master at next login or user prompt.
IE7
IE6

31. Creating vClones
Create a baseline Windows virtual machine on your Virtual Infrastructure. V1 OS

32. Building Desktops with vClonesOS
This replica will then create a set of small linked clones and join them to the domain. V1 OS

33. Building Desktops with vClonesOS
Profiles are stored as user personality disks, created on first logon if necessary. VM OS V1 OS

34. Building Desktops with vClonesOS
User data is stored on virtualized file servers. V1 OS

35. Building Desktops with vClonesOS V1 OS
Thinapps are launched from network shares

36. Building Desktops with vClonesOS
The user’s PC is the resulting combination. V1 OS

37. Building Desktops with vClonesOS
Update the baseline Windows VM with a patch. V2 OS

38. Building Desktops with vClonesOS
Publish the new SVI source VM. V2 OS V2 OS

39. Building Desktops with vClonesX V2 OS
As users log out, the clones are deleted… V2 OS

40. Building Desktops with vClonesOS
…and attached to the new master replica. V2 OS

41. Q&A David G. Young Jr. Desktop Systems Engineer

42. Next Generation Concepts David G. Young Jr. Desktop Systems Engineer

44. VMware Desktop Strategy
Total Cost Reduction A G I L T Y R E L I A B T Y S E C U R T Y D E N S I T Y S T O R A G E A P C O N F L I T S