10 ways to save with desktop virtualization

8/7/2019 10 Ways to Save with Desktop Virtualization

1/16

Expert Reference Series of White Papers

1-800-COURSES www.globalknowledge.com

10 Ways To Save withDesktop Virtualization


2/16

Copyright 2011 Global Knowledge Training LLC. All rights reserved. 2

10 Ways To Save with Desktop

Virtualization

John Hales, Global Knowledge VMware instructor,A+, Network+, MCSE, MCDBA, MCT, VCP, VCI, EMCSA

IntroductionServer virtualization is a mature technology that has been deployed in many companies of all sizes and has

proved its value time and time again. Using the same concepts and thinking, a few years ago people started

considering desktop virtualization, expecting the same kind of benefits. Desktop virtualization and server virtual-

ization are two different use cases with different costs and benefits, though they may use the same technology

to accomplish the actual virtualization of desktops or servers.

The purpose of this white paper is not to discuss what desktop virtualization is (in much detail anyway), how it

differs from server virtualization, the pros and cons of it, etc. Rather, this paper is designed to review how desk-

top virtualization can save you money. Some of these points will be more applicable to one situation, company,

etc., than another, but the idea is to stimulate and encourage thought about the technology and its use.

For the purposes of this white paper, desktop virtualization is discussed in the context of VMware vSphere and

VMware View, though many of the concepts apply to other desktop and/or server virtualization platforms as

well.

Using vSpherevSphere is VMwares bare-metal hypervisor and consists of two platform choices as follows:

ESX, which has been around for many years and includes a service console for command line access at

the server, but which VMware has announced is being discontinued (version 4.1 is the last version).

ESXi, which was introduced with ESX 3.5 and does away with the Linux-based command line on the

server (though command line access is still provided remotely and a minimalist command line is provided

for troubleshooting issues on the server) and represents the future.

Neither product will be discussed in detail here, but as vSphere provides the foundation for View, some of the key

features and functions will be provided to create a frame of reference.

The review of key functions and components is based on the diagram below.


3/16


vSphere was built to be used with an internal cloud (servers, storage, and networking all on-site at the customers

location) and/or with an external cloud (servers, storage, and networking all provided by companies on the

Internet that may or may not integrate with any local infrastructure). Both ESX and ESXi, hereafter denoted

generically as ESX(i), provide the same feature set when licensed and managed by vCenter. vCenter is VMwares

management product that provides simple graphical, command line, and/or API (Application Programming Inter-

face) access to functionality, some of which ESX(i) provides and some of which vCenter provides.

Entire books are written and many classes exist that go into the capabilities in great detail, but for our purposes,some of the keys ones are:

VMFS:This is the native file system in ESX, similar to NTFS for Windows or ext2 for Linux. It is a clustered

file system, meaning that it was designed to be shared by multiple servers at the same time. It was

designed to store and access VMs efficiently. It also supports thin provisioning, where the VM sees the

entire space allocated to it, but only consumes as much space as it needs. This functionality will be impor-

tant when linked clones are discussed later in this paper.

StandardSwitch:This virtual switch is the virtual link between the virtual NICs in the VMs and the physi-

cal NICs (and thus the outside world). It is basically a software implementation of a physical switch. They

have been used since the start of VMware and still exist today.

DistributedSwitches:Introduced with vSphere, they centralize configuration and management of the

switch in vCenter and the specific configuration is then pushed out to all servers that are associated with

the switch. This provides much greater scalability and simplifies management, but is only available in the

Enterprise Plus version of ESX(i) and vCenter.


4/16


HotAdd:This functionality is similar to the functionality in the physical world and allows components,

such as network cards and hard drives to be plugged in while the VM is running (assuming the underly-

ing OS can dynamically see and use the changes). Some operating systems also support the ability to hot

add RAM and even CPUs. Note that the capability exists only to add, not to remove, components. To

remove a component, the VM must be powered off first.

vMotion:A pioneering achievement from VMware is that it allows a live, running VM to be physically

migrated from one physical server to another with virtually no down time. This capability is key to the

functionality provided by DRS. It allows administrators to do maintenance during the day, take a server

out for patching, etc., without causing down time to applications. It also provides the ability to scale out

to new nodes in the cluster as more VMs come online.

StoragevMotion:This is similar to vMotion, but the VM changes from one storage location to another

while remaining on the same host. It is not possible to change both host and storage at the same time

with the VM powered on; to do so, either the VM will need to be powered off or the two moves will

need to be made one after the other. It is storage type independent, so the VM can go from any type

of storage to any other type on the same or different array. It is also useful in array migration scenarios.It has the capability to move multiple virtual hard drives from any number of locations to any number of

locations.

HA: High Availability (HA) is a feature that will restart a crashed VM and/or all of the VMs on a crashed

server. This is a great way to make sure users desktops are virtually always available when they need

them.

FaultTolerance:This feature allows a VM to be run in lock step on two different physical servers so that

if one server crashes, the VM will run from the other with no loss of data. It probably wont be used

much in a View environment, but could be if you had a PC that performed an important function. Fault

Tolerance is a feature related to HA.

DRS:The Distributed Resource Scheduler (DRS) is a vCenter feature that will load balance across the

available servers to give the best performance possible. It makes it easy and simple to get good perfor-

mance in a dynamic environment where different desktop users may be placing varied loads on their

desktops at different times of the day.

DPM:Distributed Power Management (DPM) is a feature of DRS that powers off physical servers when

demand is low to save on electric and cooling costs. It does this by using DRS to migrate VMs onto a

subset of the available hosts and then it powers the host off. When demand picks up, DPM will power

the host on again then use DRS to load balance across the additional node.

Brief Overview of VMware ViewView is VMwares VDI (Virtual Desktop Infrastructure) tool that makes virtual Windows XP, Vista, and/or 7 desk-

top VMs accessible through a common interface, across the LAN or WAN. The purpose of this white paper is not


5/16


to describe all of the components and how they work, but rather to focus on the money saving aspects of VDI,

but a brief overview is helpful to put the rest of the paper in perspective.

The primary components of View are:

ESX(i)serversandvCenter:View is based on the foundation of ESX(i) servers and vCenter and can thus

take advantage of all of the features previously described (and many more not listed).

ActiveDirectory:View requires Active Directory (AD) for all user authentication, and as such, both thevirtual desktops and the View Manager PC must belong to the domain.

ViewManager:This component is the heart of View and provides user authentication (in conjunction

with AD), a secure access point to the desktop from the client, and the management user interface (UI).

ViewComposer:This feature allows linked clones to be created, and is not necessary if they are not

used. If installed, it is installed on each vCenter server that has VMs used by View.

LinkedClonesvs.FullClones: A full clone is a complete copy of a VM, in other words if the template

used to deploy a Windows 7 VM is 20 GB, then each copy will be 20 GB. This is how most server VMs areprovisioned today (if desired, they may be thin provisioned to reduce the actual space consumed). With

Linked Clones, a master copy of a VM is made and then each linked clone created starts with that image

and only stores the changes from that image, thus saving a lot of space. Linked Clones will be described

in greater detail later in this paper.


6/16


ThinApp:ThinApp takes virtualization to the next level by virtualizing individual applications separating

the application from the OS in much the same way the server and desktop virtualization separate the

OS from the underlying hardware. This provides a great deal of flexibility in deploying, updating, and

maintaining applications. Note that unlike the other features discussed here, ThinApp can be used with

physical and virtual OS deployments (though well concentrate on their virtual uses here). This can be

another great way to save money and will be discussed later in this paper.

UnifiedAccess:One of the great features of View is that the View Client can be used to connect to

many different types of desktops using the same UI in each case. Besides connecting to virtual desktops,

View can connect to:

o TerminalServers:The standard Windows Terminal Services feature is great when an entire

desktop is not needed, such as for call centers where a simple connection to a web page to fill

in order, customer, or other details is all that is needed. This is simpler and cheaper than a full

desktop deployment for those that dont need the full desktop.

o PhysicalPCsandBladePCs:For those applications that may not run well in a virtualized envi-

ronment, such as graphic intensive scenarios, physical PCs or blade PCs (like blade servers, but

aimed at desktop needs) may be connected to. This is especially great for expensive resourcesthat are shared by a team of people, such as graphic designers, architects, or CAD/CAM teams

that need the graphics capabilities to do their work, but also need regular apps to write reports,

check e-mail, etc. The company gets the common user interface to both systems while at the

same time needing to purchase fewer of the expensive desktop systems. It also allows those

who need access to these resources to access them remotely, such as from home or a customers

site, something that is difficult or impossible with traditional desktops.

Clients:Users can connect to any of the above devices or virtual desktops using a variety of devices,

depending on what the company has available and the users needs. The three options are:

o Thick:Thick clients are standard desktops or laptops running Windows or a MAC OS. They

can be old computers as all of the processing runs on the remote system, so this is a potentialmoney savings, but there wont be any power savings from using them (in fact the total power

consumption will go up in the company because of the additional servers and storage required).

o Offline:This is a variant of the thick client, with the additional ability to check out a VM from

the server and run it locally (such as for a sales person on the road or others who travel and

need to have access to their virtual desktop while disconnected from the network). They can

check it back in when they are back in the office and can sync (incrementally) changes to the

datacenter VM so that it can be properly backed up.

o Thin:This is a simple client that uses very little power, potentially leading to overall power sav-

ings for the company. This feature will be discussed in more detail later in this paper.

10 Ways To Save with Desktop VirtualizationThe primary purpose of this document is to describe how a VDI implementation can save money for your com-

pany. As such, the bulk of the remainder of this paper will be a description of ten ways that VDI can be a cost

savings.


7/16


1. Looking for savings in the right place OpEx, not CapEx

One of the biggest mistakes that people often make when considering VDI is that they expect the same level

of savings they saw with server virtualization. That is not likely because you will not be reducing the number of

computers in your environment everyone who has one now will need one at the end of the implementation, as

well as additional servers and storage to host those new VMs. To use accounting lingo, look for savings in OpEx

(the Operational Expenditures, or in other words, the ongoing cost of doing business, which is usually the largercost in any IT project), not the short term CapEx (Capital Expenditures, or in other words the cost of buying new

equipment [capital]). In fact, CapEx is likely to rise in the short term as additional servers and storage are pur-

chased, and may go even higher as desktops are replaced with thin clients. Typically, however, thin clients will re-

place existing desktops either as the desktop comes up for replacement or when it fails and needs to be replaced.

The OpEx savings come from the following areas:

QuickProvisioning:Creating a new desktop VM, customized for each user, literally takes just a few

minutes instead of the hours typically consumed in imaging a corporate standard image, patching it, ap-

plying the appropriate updates, special software needed, etc. When this is multiplied by the number of

new desktops and/or laptops deployed per year (and often that is 1/3 of the company as each user gets

a new machine every 3 years), this can be a huge savings.

QuickandeasybackupandrestoreoftheOS,applications,and/ordata:Backup is generally well

understood and implemented on servers, but end users rarely if ever backup their machines, but often

store important work information on them. The cost of recreating or retrieving this data can be very

high. By storing them in the data center, the same backup principles applied to servers can be applied to

desktops as well. In many cases, the OS will not need to be backed up as it can be redeployed faster and

easier; this is especially true when Linked Clones with separate data drives are used.

Quickandeasyapplicationdeployment(standardplatform):One of the issues in deploying applica-

tions is that they run on a wide variety of hardware platforms which may cause incompatibilities or other

issues requiring administrator intervention. They may also take a long time to deploy and to configure

which user has access to which applications. This is simplified in a virtual environment, especially when

application virtualization is also deployed it may literally take just a few minutes to deploy the applica-

tions where they need to go to hundreds or thousands of machines. This will be described further later

in this document.

Easymechanismstopatchandupdateoperatingsystemsandapplications:Deploying updates is

much simpler because the VMs live in the datacenter and thus will reliably be patched, which they may

not when deployed in the field (or the updates may be done at inconvenient times to ensure that the

machine is running). In addition to the current mechanisms used in the physical world to deploy patches,

they can also be patched by VMware Update Manager (VUM) and if linked clones are used, they have a

very simple update mechanism that can be used to deploy the updates to hundreds or thousands of VMs

with just a few clicks and that is non-disruptive to user data (though the VM will be offline during the

update).


8/16


9/16


This is not an SRM white paper, so we wont discuss all of the components in detail, but at a high-level, the com-

ponents are as follows:

vCenter:Nothing special is required from vCenter other than you will need a separate vCenter on both

sides, so an extra license and an extra server or VM will be required on the recovery side.

SiteRecoveryManager:This server is also required on both sides (as a VM or a physical server) and

can be on the vCenter server for small deployments or on its own dedicated server for larger ones. This

server manages the entire process of protecting, testing, and failing over VMs.

Storage: At this point, the storage must be from the same vendor on both sides and array-based replica-

tion must be configured between the arrays (which may require extra software or licensing from the

array vendor). Ultimately, VMware wants to be able to do the replication at the host level, but that is

not possible today.

VMs(Protectedsite):TheseVMswillfailovertotheprotectedsiteincaseofadisaster.Theystayrunning

during a test but will also run (isolated) on the recovery site for testing purposes for the duration of the

test.

VMs(Recoverysite):These VMs can be powered off if necessary to make more resources available for

the VMs that are failing over. It is not required that they be suspended, but they can be if needed.

Testing can be done non-disruptively as often as desired. Failover is a matter of just a few clicks and can be donewhether or not the protected site is online.


10/16


3. Legal discovery and compliance savings

Depending on your organization and how work is done, stored, retained, and backed up, legal discovery can be

a very expensive proposition and one that may be difficult to manage in a cost-effective manner as users may

delete files from their hard drives, data is spread all over the place, etc. In a VDI implementation, many of these

challenges dont exist. First, all data is located in the datacenter and can be backed up, so compliance standards

can be enforced more easily. Second, legal discovery is faster and easier because all of the data is in the data-center and not stored locally on many PCs. It is thus easier to find, but also far less expensive as there isnt the

cost of getting the users desktops or laptops and returning it to them, plus the lost productivity of the user not

having their computer and/or the extra expense of building a temporary one for them while their device is going

through the process.

4. Secure access to the users own desktop from anywhere at any time from a wide

variety of devices, from netbooks to laptops to desktops

One of the great advantages to a VDI is that the user can access his or her own virtual desktop from almost any

device, increasing productivity and access wherever the user may be. Today, access is possible and supported from

the following devices: thin clients, desktops, laptops (including offline access when the network is not available),

Macintosh-based computers, and Web browser access from PCs and MACs. In addition, access is possible butnot supported from the following devices: Linux (via VMware View Open Client open source product), Android

and iOS (iPOD/iPAD/iPhone] devices (via WYSE PocketCloud), etc. This makes access possible virtually anytime,

anywhere, as long as there is a network connection.

5. Thin clients

Weve mentioned thin clients several times in this paper, but we havent described them in much detail up to this

point. A thin client is a simple device with few (if any) moving parts. It usually consists of ports for the keyboard

and mouse (usually via USB), video (either a port for an LCD screen or many models consist of the screen and the

other parts are internal to it), power, and a network connection. Many dont have a hard drive, just firmware

in a flashable BIOS with View API support, while those that have a hard drive usually have a very small one with

Windows XP Embedded or Linux and the View Client.

Another benefit of thin clients is that no data is stored locally, so if anything breaks, simply replace it with a new

one and the user can go back to work. This saves a lot of time and money in terms of provisioning a new ma-

chine and configuring it.

Thin clients are often a couple of hundred dollars or so (depending on what is included and how it is configured),

but this cost is much below a full PC or laptop, adding to the savings as PCs are replaced with thin clients. Spare

clients also cost less than their fat (or thick) counterparts.

6. Potential for power savings

Power savings are widely debated in VDI circles, with some saying that huge power savings are possible (IBM

stated up to 40% power savings in one article), with others saying there will actually be more power consumed (if

thick clients are used along with the added cost of the power consumed by the servers and storage as well as the

cooling for them). This will depend on many factors, including consolidation density, whether or not thick clients

are used, etc. In general, however, a typical desktop PC uses about 115 watts on average (accounting for period


11/16


of both peak and idle activity), while a typical thin client uses less than 15 watts (active) and less than 0.5 watts in

standby. The power consumption depends on the model, with some consuming less than 7 watts (active), while

others dont go into standby, so the power drain is the same as long as unit is on. The key is to figure the power

consumption on each device plus the cost of the storage and the servers to determine the potential for power

savings.

To get even greater accuracy on power savings, consider the additional cost of air conditioning. The rule of

thumb is that each watt of power consumed by a device also typically costs 0.3 watts to cool it. Thus all of the

desktop PCs at 115 watts will cost a lot more to cool than the thin clients at 15 watts or less.

7. Infrastructure longevity an average of 6 to 8 years for a thin client vs. 3 to 4 for a

fat client

Another great area of cost savings is in the average life span for the connecting device. Thin clients typically have

a lifecycle of about eight years, for several reasons. First, there are no moving parts which are often what breaks

on a standard PC. Second, they dont need more memory or CPU power for a new OS on the clients as it is just

a display protocol resource utilization is independent of the virtual desktop being used. Note, however, that

more resources may be needed on the servers if the virtual desktop OS is upgraded, but virtualization techniquessuch as memory sharing and only allocating the memory actually needed may mitigate some of that.

8. Easier and simpler license compliance

License compliance may be easier and simpler in the virtual world than the physical world this is an area that

may or may not prove to be true in any given environment.

One of the things that was a big impediment to VDI was Microsofts licensing policy for virtual desktop machines.

Its not that licensing was that different than the physical world, but they required a license for the accessing

device and the virtual desktop, doubling licensing costs. However, they changed their licensing policy on July 1,

2010, to allow access to VDI installations of Windows and Office without a separate license for the accessingdevice as long as the customer has either Software Assurance (SA) or a Virtual Desktop Access License (VDAL).

As for license compliance, businesses can use traditional software inventorying solutions (such as Microsofts

SCCM [System Center Configuration Manager], Novells Zen Works, etc.) and accurate results will always be

returned as the desktops are located in the datacenter and thus are always online.

Another method that can help control licensing costs and encourage greater compliance is the use of Application

Virtualization technologies which can further control who has what software installed.

9. Using Application Virtualization, preventing application incompatibilitiesApplication virtualization, as mentioned previously, is the next logical step in virtualization and separates the ap-

plication from the OS. This technique allows the same application to be packaged and run on multiple operating

systems without any modifications. Most applications can be virtualized and will run the same way that they do

in the physical world.


12/16


The basic diagram of how this technology works is illustrated below.

This technology can be used with either physical or virtual computers, or any combination of the two. The dia-

gram shows how the OS has the system files, user profile, registry, etc., like any other application, but does not

contain anything other than a single file for the entire application (and that file can be located on a file share, on

a web site, or copied locally). The file is represented by the blue box labeled ThinApp Virtualization and contains

the virtualization layer (common to all applications), as well as any application files and registry settings that the

application needs.

As illustrated in the purple box, the view from within the application looks like it is natively installed. If the app

needs to read a registry entry, it can do so from the applications version (inside the file) or from the systems

registry (depending on what it is looking for). Any writes to the registry go to the sandbox, a directory where

all writes for the application are stored (there is one directory per ThinApp application that is used). The same

principle is used for files you can read from within the application or from the OS locations, and can write to

your user profile location and some normal system locations, with all other writes going to the sandbox. The net

result is that the application is unaware that it is virtualized, just as a virtualized desktop OS doesnt know that it

is virtualized.

10. Minimize time in testing by having just a few (or only one) OS image with the

ability to test and revert to previous images easily

One of the advantages of using a VDI is that you dont need many different OS images in fact, you can have as

few as one with applications installed as needed (or even not installed at all via ThinApp, as previously described).

Application testing, patching, etc., also become much simpler in this environment. There are several reasons for


13/16


this. First, linked clones make it simple to create and manage OS images, which will be discussed shortly. Second,

linked clones can be used with ThinApp to reduce the number of OS images by deploying applications as needed,

which will also be discussed later in this document. In addition, there is no need for images for different hardware

platforms they all are VMware VMs and thus the hardware platform is abstracted. Finally, you can use VMware

snapshots before deploying any patches, new applications, etc., to simplify roll back when issues arise during test-

ing to revert to the original state of the VM. On the other hand, if the application or patch works successfully, it

takes just a few clicks to put them in the image itself.

Desktopmanagementoperations

Both full and linked clones provide many options to deploy the operating system, applications, etc., but linked

clones make application image updating and maintenance quite a bit simpler. As illustrated in the diagram

below, it is just a few clicks to deploy either type of clone, though linked clones will consume a lot less disk space

than a full clone, as previously described. The extra functionality that linked clones offer are twofold; first, they

can be refreshed and second, they can be recomposed.

When refresh is chosen, the OS drive (but not any user data) is reverted back to the master image and any

changes or updates will be lost. This means any Windows Updates, new applications, etc., will be removed aswell, but the space the changes consumed will be made available again. In fact, this is the primary reason that

this option exists to control the disk space utilization. One quick note here: If ThinApp applications are used,

they will be unaffected by this operation as the application can just be a shortcut to a file on a file server and all

of the registry entries and files are contained either within the file or in the sand box which will be stored on the

users data drives.

The recompose option allows an administrator to update the master image, test it to make sure it works prop-

erly, then deploy the changes (including Windows Updates, other application patches, new applications, and any

other files or documents the administrator wants to distribute) with just a few clicks, making application mainte-

nance quick, easy, with the additional benefit of space and bandwidth savings (vs. deploying the same changes

hundreds or thousands of times).

Note that both refresh and recompose options are disruptive, meaning that no users can be using the image

when the operation is begun and for the duration of the update; any user who is currently connected will typi-

cally be given a warning then automatically logged out if they dont do so before the warning interval expires.


14/16


Linked clones require View Composer to be installed on the vCenter server to be created, maintained, and de-

leted.

ApplicationdeploymentusingViewandThinApp

Application deployment with View 4.5 (or later) and ThinApp is quite simple. The administrator defines as many

applications as he or she wants (one at a time), then places the file that contains the application either on each

computer or on a central file server or web server and deploys a shortcut to each computer that needs it. In

fact, View Administrator, the management interface for View, can be used to deploy the application to only the

desired computers. ThinApp also allows restrictions based on the Active Directory groups the user belongs to,

making it simpler to deploy the applications and control licensing. By controlling who can run the application,

licensing costs can be reduced.

In the diagram below, three applications have been created and placed on a file server. The administrator then

determines who will get each application. App 1 is needed by everyone, so it can be placed in the OS image. App

2 is used only by sales and marketing personnel, so is distributed to only their computers, while App 3 is only used

by the accounting department and thus only distributed to them.


15/16


SummaryThere are many ways that a VDI infrastructure can save a company a lot of money as long as it is properly imple-

mented and savings are looked for in the right places. That is not to discount the upfront costs, but simply to

take a longer and more inclusive view in determining ROI (Return on Investment).

VMware ESX(i) servers managed by vCenter provide a very strong foundation for a VDI implementation. View

makes management and deployment of Windows XP, Vista, and 7 machines easy and saves a lot of administratortime and optimizes resource utilization. Using ThinApp (which is bundled in the Premier Edition of View along

with View Composer for Linked Clone functionality) can lead to even greater savings. Finally, using thin clients

instead of the traditional thick (or fat) clients can lead to even greater savings in administration, capital (over the

medium to long term), power, and cooling.

Related VMware CertificationsVMware has just introduced a series of desktop certifications similar to those available for vSphere (with the

exception of the VCA, which does not have an equivalent vSphere certification). These certifications are indepen-

dent of the vSphere certifications. The View 4.5 ICM class supports the objectives for all three exams. The avail-

able certifications are:

VMwareCertifiedAssociate4Desktop(VCA4-DT)

VMwareCertifiedProfessional4Desktop(VCP4-DT)

VMwareCertifiedAdvancedProfessionalDesktop(VCAP-DT)


16/16


Learn MoreLearn more about how you can improve productivity, enhance efficiency, and sharpen your competitive edge.

Check out the following Global Knowledge courses:

VMware vSphere: Install, Configure, Manage [V4.1]

VMware View: Install, Configure, Manage [V4.5]

For more information or to register, visit www.globalknowledge.com or call 1-800-COURSES(1-800-268-7737)

to speak with a sales representative.

Our courses and enhanced, hands-on labs and exercises offer practical skills and tips that you can immediately

put to use. Our expert instructors draw upon their experiences to help you understand key concepts and how to

apply them to your specific work situation. Choose from our more than 1,200 courses, delivered through Class-

rooms, e-Learning, and On-site sessions, to meet your IT and business training needs.

About the AuthorJohn Hales, VCP, VCI, is a VMware instructor at Global Knowledge, teaching all of the vSphere classes that GlobalKnowledge offers, including the new View classes. John is also the author of many books, from involved techni-

cal books from Sybex to exam preparation books, to many quick reference guides from BarCharts, in addition to

custom courseware for individual customers. John has various certifications, including the VMware VCP and VCI,

the Microsoft MCSE, MCDBA, MOUS, and MCT, the EMC EMCSA (Storage Administrator for EMC Clariion SANs),

and the CompTIA A+, Network+, and CTT+. John lives with his wife and children in Sunrise, Florida.

10 ways to save with desktop virtualization

Documents