Expert Reference Series of White Papers

10 Ways To Save with Desktop Virtualization


but the idea is to stimulate and encourage thought about the technology and its use.10 Ways To Save with Desktop Virtualization John Hales. EMCSA Introduction Server virtualization is a mature technology that has been deployed in many companies of all sizes and has proved its value time and time again. the pros and cons of it.. 2 . MCSE. Global Knowledge VMware instructor. though many of the concepts apply to other desktop and/or server virtualization platforms as well. VCI.1 is the last version). • ESXi. company. how it differs from server virtualization. Network+. though they may use the same technology to accomplish the actual virtualization of desktops or servers. The review of key functions and components is based on the diagram below. than another. this paper is designed to review how desktop virtualization can save you money. Neither product will be discussed in detail here. MCDBA. MCT. Rather. some of the key features and functions will be provided to create a frame of reference. Copyright ©2011 Global Knowledge Training LLC. A+. a few years ago people started considering desktop virtualization. All rights reserved. Using vSphere vSphere is VMware’s bare-metal hypervisor and consists of two platform choices as follows: • ESX.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. Desktop virtualization and server virtualization are two different use cases with different costs and benefits. which was introduced with ESX 3. desktop virtualization is discussed in the context of VMware vSphere and VMware View. but as vSphere provides the foundation for View. 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. Using the same concepts and thinking. VCP. etc. For the purposes of this white paper. expecting the same kind of benefits. etc. The purpose of this white paper is not to discuss what desktop virtualization is (in much detail anyway). Some of these points will be more applicable to one situation.

It is basically a software implementation of a physical switch. This provides much greater scalability and simplifies management. provide the same feature set when licensed and managed by vCenter. storage. but for our purposes. hereafter denoted generically as ESX(i). some of which ESX(i) provides and some of which vCenter provides. Both ESX and ESXi. and networking all on-site at the customer’s location) and/or with an external cloud (servers.vSphere was built to be used with an internal cloud (servers. where the VM sees the entire space allocated to it. S • tandard Switch: This virtual switch is the virtual link between the virtual NICs in the VMs and the physical NICs (and thus the outside world). All rights reserved. Copyright ©2011 Global Knowledge Training LLC. Entire books are written and many classes exist that go into the capabilities in great detail. It also supports thin provisioning. They have been used since the start of VMware and still exist today. It is a clustered V file system. they centralize configuration and management of the D switch in vCenter and the specific configuration is then pushed out to all servers that are associated with the switch. and/or API (Application Programming Interface) access to functionality. some of the keys ones are: • MFS: This is the native file system in ESX. • istributed Switches: Introduced with vSphere. storage. vCenter is VMware’s management product that provides simple graphical. similar to NTFS for Windows or ext2 for Linux. but only consumes as much space as it needs. meaning that it was designed to be shared by multiple servers at the same time. 3 . It was designed to store and access VMs efficiently. command line. This functionality will be important when linked clones are discussed later in this paper. and networking all provided by companies on the Internet that may or may not integrate with any local infrastructure). but is only available in the Enterprise Plus version of ESX(i) and vCenter.

but the VM changes from one storage location to another S while remaining on the same host. so the VM can go from any type of storage to any other type on the same or different array. H such as network cards and hard drives to be plugged in while the VM is running (assuming the underlying OS can dynamically see and use the changes). When demand picks up. It also provides the ability to scale out to new nodes in the cluster as more VMs come online. It allows administrators to do maintenance during the day. It is also useful in array migration scenarios. This is a great way to make sure users’ desktops are virtually always available when they need them. All rights reserved. • Motion: A pioneering achievement from VMware is that it allows a live. and/or 7 desktop VMs accessible through a common interface. • torage vMotion: This is similar to vMotion. Fault Tolerance is a feature related to HA. to do so. To remove a component. the VM will run from the other with no loss of data. either the VM will need to be powered off or the two moves will need to be made one after the other. • RS: The Distributed Resource Scheduler (DRS) is a vCenter feature that will load balance across the D available servers to give the best performance possible. take a server out for patching. It does this by using DRS to migrate VMs onto a subset of the available hosts and then it powers the host off. not to remove. but could be if you had a PC that performed an important function. Note that the capability exists only to add. This capability is key to the functionality provided by DRS. running VM to be physically v migrated from one physical server to another with virtually no down time. across the LAN or WAN. the VM must be powered off first. • A: High Availability (HA) is a feature that will restart a crashed VM and/or all of the VMs on a crashed H server. The purpose of this white paper is not Copyright ©2011 Global Knowledge Training LLC. components. 4 . It is not possible to change both host and storage at the same time with the VM powered on. without causing down time to applications. It has the capability to move multiple virtual hard drives from any number of locations to any number of locations. Brief Overview of VMware View View is VMware’s VDI (Virtual Desktop Infrastructure) tool that makes virtual Windows XP.. Some operating systems also support the ability to hot add RAM and even CPUs. Vista. It is storage type independent. • PM: Distributed Power Management (DPM) is a feature of DRS that powers off physical servers when D demand is low to save on electric and cooling costs. etc. • ault Tolerance: This feature allows a VM to be run in lock step on two different physical servers so that F if one server crashes.• ot Add: This functionality is similar to the functionality in the physical world and allows components. It makes it easy and simple to get good performance in a dynamic environment where different desktop users may be placing varied loads on their desktops at different times of the day. It probably won’t be used much in a View environment. DPM will power the host on again then use DRS to load balance across the additional node.

both the A virtual desktops and the View Manager PC must belong to the domain. thus saving a lot of space. • iew Composer: This feature allows linked clones to be created. All rights reserved. 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. a secure access point to the desktop from the client. but rather to focus on the money saving aspects of VDI. in other words if the template L used to deploy a Windows 7 VM is 20 GB. Copyright ©2011 Global Knowledge Training LLC. This is how most server VMs are provisioned today (if desired. The primary components of View are: • SX(i) servers and vCenter: View is based on the foundation of ESX(i) servers and vCenter and can thus E take advantage of all of the features previously described (and many more not listed). With Linked Clones. 5 . • ctive Directory: View requires Active Directory (AD) for all user authentication. If installed. and the management user interface (UI). Linked Clones will be described in greater detail later in this paper. then each copy will be 20 describe all of the components and how they work. • inked Clones vs. and is not necessary if they are not V used. but a brief overview is helpful to put the rest of the paper in perspective. and as such. they may be thin provisioned to reduce the actual space consumed). it is installed on each vCenter server that has VMs used by View. • iew Manager: This component is the heart of View and provides user authentication (in conjunction V with AD). Full Clones: A full clone is a complete copy of a VM.

but also need regular apps to write reports. C depending on what the company has available and the users’ needs. This can be another great way to save money and will be discussed later in this paper. such as from home or a customer’s site. They can be old computers as all of the processing runs on the remote system. Copyright ©2011 Global Knowledge Training LLC. updating. or CAD/CAM teams that need the graphics capabilities to do their work. or other details is all that is needed. The company gets the common user interface to both systems while at the same time needing to purchase fewer of the expensive desktop systems. O ffline: This is a variant of the thick client. such as for call centers where a simple connection to a web page to fill in order.• hinApp: ThinApp takes virtualization to the next level by virtualizing individual applications separating T the application from the OS in much the same way the server and desktop virtualization separate the OS from the underlying hardware. ThinApp can be used with physical and virtual OS deployments (though we’ll concentrate on their virtual uses here). o • lients: Users can connect to any of the above devices or virtual desktops using a variety of devices. This is simpler and cheaper than a full desktop deployment for those that don’t need the full desktop. T hin: This is a simple client that uses very little power. Note that unlike the other features discussed here. the bulk of the remainder of this paper will be a description of ten ways that VDI can be a cost savings. but aimed at desktop needs) may be connected to. customer. 6 . It also allows those who need access to these resources to access them remotely. This feature will be discussed in more detail later in this paper. The three options are: o T hick: Thick clients are standard desktops or laptops running Windows or a MAC OS. something that is difficult or impossible with traditional desktops. As such. such as graphic designers. but there won’t 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). 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. U • nified Access: 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. and maintaining applications. This provides a great deal of flexibility in deploying. such as graphic intensive scenarios. 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). All rights reserved. so this is a potential money savings. physical PCs or blade PCs (like blade servers. Besides connecting to virtual desktops. potentially leading to overall power savings for the company. etc. View can connect to: o Terminal Servers: The standard Windows Terminal Services feature is great when an entire desktop is not needed. This is especially great for expensive resources that are shared by a team of people. o o 10 Ways To Save with Desktop Virtualization The primary purpose of this document is to describe how a VDI implementation can save money for your company. P hysical PCs and Blade PCs: For those applications that may not run well in a virtualized environment. check e-mail. architects.

In addition to the current mechanisms used in the physical world to deploy patches. the same backup principles applied to servers can be applied to desktops as well. as well as additional servers and storage to host those new VMs. By storing them in the data center. this can be a huge savings. especially when application virtualization is also deployed – it may literally take just a few minutes to deploy the applications where they need to go to hundreds or thousands of machines. customized for each user. 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). Looking for savings in the right place – OpEx. patching it. • uick and easy application deployment (standard platform): One of the issues in deploying applicaQ tions is that they run on a wide variety of hardware platforms which may cause incompatibilities or other issues requiring administrator intervention. they can also be patched by VMware Update Manager (VUM) and if linked clones are used. Typically. special software needed. not the short term CapEx (Capital Expenditures. 7 . They may also take a long time to deploy and to configure which user has access to which applications. Copyright ©2011 Global Knowledge Training LLC. 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. the ongoing cost of doing business. literally takes just a few Q minutes instead of the hours typically consumed in imaging a corporate standard image. but often store important work information on them. look for savings in OpEx (the Operational Expenditures. thin clients will replace existing desktops either as the desktop comes up for replacement or when it fails and needs to be replaced. This is simplified in a virtual environment. but end users rarely if ever backup their machines. 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. this is especially true when Linked Clones with separate data drives are used. or in other words the cost of buying new equipment [capital]). • uick and easy backup and restore of the OS. 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 fact. The cost of recreating or retrieving this data can be very high. applications. CapEx is likely to rise in the short term as additional servers and storage are purchased. and/or data: Backup is generally well Q understood and implemented on servers. which is usually the larger cost in any IT project). In many cases. The OpEx savings come from the following areas: • uick Provisioning: Creating a new desktop VM. This will be described further later in this document.1. etc. or in other words. the OS will not need to be backed up as it can be redeployed faster and easier. All rights reserved. however. • asy mechanisms to patch and update operating systems and applications: Deploying updates is E much simpler because the VMs live in the datacenter and thus will reliably be patched. applying the appropriate updates. 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). and may go even higher as desktops are replaced with thin clients. To use accounting lingo.

2. look at VMware Site Recovery Manager (SRM). pay for travel and entertainment T&E) expenses while they are gone (possibly for an extended period of time).S. downtime in the event of a disaster Two related issues that are being explored by more and more companies are DR (Disaster Recovery) and BC (Business Continuity). This is a good thing – according to the National Records Administration in the U.. etc.• o need for master images for every desktop and laptop used in the company - the VM image is hardN ware independent: One of the great advantages of virtualization is that it is hardware independent. For those using offline mode. Many companies have plans in place to protect themselves from these issues. The role of SRM in failing over the desktops is shown in the figure below. as long as there is sufficient RAM to run the machine and any other apps that may be running at the same time on the local box. some of which may also overlap those discussed here. it doesn’t matter what kind of laptop. so hardware images for every type of desktop and laptop isn’t needed. By virtualizing the desktops. eliminating the need to transport people somewhere else. the DR/BC plan isn’t worth very much. BC and DR possibilities vs. In any case. and/or employees get access to those servers? Without that. However. All rights reserved. customers. nor what the configuration is. If you need help in this area. This also makes it great for those who work from home. nor is there any issue with changing hardware vendors for the servers or the client devices. Copyright ©2011 Global Knowledge Training LLC. a good DR/BC plan will usually describe how to bring all the servers back online and how to failback when the problem that caused the failover is rectified. as they will connect and work the same way. but that still leaves the big underlying question that often isn’t asked – how will your clients. remember that the BC/DR plan will need to be updated to deal with how the virtual desktops will failover and failback as well as your existing servers. which may need to be updated or require extra hardware if utilization goes up dramatically during the outage). people can use their own home computers to login and access their desktops just as if they were at work. and how people will access their desktops remotely (often over a web connection. half of all companies that lose their datacenter for 10 days or more file for bankruptcy immediately and 93% do within 10 years. Additional savings may be realized in the other nine areas discussed in this paper as well. 8 .

Copyright ©2011 Global Knowledge Training LLC. but they can be if needed. • ite Recovery Manager: This server is also required on both sides (as a VM or a physical server) and S can be on the vCenter server for small deployments or on its own dedicated server for larger ones. • Ms (Protected site): These VMs will failover to the protected site in case of a disaster. This server manages the entire process of protecting. but that is not possible today. so an extra license and an extra server or VM will be required on the recovery side. but at a high-level. • torage: At this point. • Ms (Recovery site): These VMs can be powered off if necessary to make more resources available for V the VMs that are failing over. 9 . All rights reserved. VMware wants to be able to do the replication at the host level. Ultimately. They stay running V during a test but will also run (isolated) on the recovery site for testing purposes for the duration of the test. so we won’t discuss all of the components in detail. It is not required that they be suspended. Failover is a matter of just a few clicks and can be done whether or not the protected site is online. and failing over VMs. the storage must be from the same vendor on both sides and array-based replicaS tion must be configured between the arrays (which may require extra software or licensing from the array vendor). the components are as follows: • Center: Nothing special is required from vCenter other than you will need a separate vCenter on both v sides. Testing can be done non-disruptively as often as desired. testing.This is not an SRM white paper.

video (either a port for an LCD screen or many models consist of the screen and the other parts are internal to it). It usually consists of ports for the keyboard and mouse (usually via USB). power. Spare clients also cost less than their fat (or thick) counterparts. Android and iOS (iPOD/iPAD/iPhone] devices (via WYSE PocketCloud). 4. including consolidation density. but we haven’t described them in much detail up to this point. as long as there is a network connection. Another benefit of thin clients is that no data is stored locally. adding to the savings as PCs are replaced with thin clients. In general. In a VDI implementation. access is possible and supported from the following devices: thin clients. data is spread all over the place. Secure access to the user’s own desktop from anywhere at any time from a wide variety of devices. etc. a typical desktop PC uses about 115 watts on average (accounting for period Copyright ©2011 Global Knowledge Training LLC. First. so compliance standards can be enforced more easily. and backed up. but also far less expensive as there isn’t the cost of getting the users’ desktops or laptops and returning it to them. A thin client is a simple device with few (if any) moving parts. All rights reserved. Potential for power savings Power savings are widely debated in VDI circles. but this cost is much below a full PC or laptop. This makes access possible virtually anytime. retained. Second. stored. Macintosh-based computers. whether or not thick clients are used. legal discovery is faster and easier because all of the data is in the datacenter and not stored locally on many PCs. so if anything breaks. just firmware in a flashable BIOS with View API support. and Web browser access from PCs and MACs. This saves a lot of time and money in terms of provisioning a new machine and configuring it. all data is located in the datacenter and can be backed up. Today. anywhere. etc. and a network connection. This will depend on many factors. It is thus easier to find. 6. desktops. In addition. access is possible but not supported from the following devices: Linux (via VMware View Open Client open source product). 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. Thin clients are often a couple of hundred dollars or so (depending on what is included and how it is configured). 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. Thin clients We’ve mentioned thin clients several times in this paper. laptops (including offline access when the network is not available). etc. with some saying that huge power savings are possible (IBM stated up to 40% power savings in one article).3. however. 5. 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). while those that have a hard drive usually have a very small one with Windows XP Embedded or Linux and the View Client. increasing productivity and access wherever the user may be. Many don’t have a hard drive. 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. 10 . simply replace it with a new one and the user can go back to work. many of these challenges don’t exist. Legal discovery and compliance savings Depending on your organization and how work is done.

however. businesses can use traditional software inventorying solutions (such as Microsoft’s SCCM [System Center Configuration Manager]. Infrastructure longevity – an average of 6 to 8 years for a thin client vs. as mentioned previously. 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. Novell’s Zen Works. while a typical thin client uses less than 15 watts (active) and less than 0. It’s not that licensing was that different than the physical world. Thin clients typically have a lifecycle of about eight years. 3 to 4 for a fat client Another great area of cost savings is in the average life span for the connecting device. with some consuming less than 7 watts (active). there are no moving parts which are often what breaks on a standard PC. As for license compliance.3 watts to cool it. 9. First. is the next logical step in virtualization and separates the application from the OS. they don’t 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. for several reasons. However.5 watts in standby. etc.of both peak and idle activity).) and accurate results will always be returned as the desktops are located in the datacenter and thus are always online. doubling licensing costs. 2010. To get even greater accuracy on power savings. Using Application Virtualization. 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. Second. Most applications can be virtualized and will run the same way that they do in the physical world. The rule of thumb is that each watt of power consumed by a device also typically costs 0. All rights reserved. but they required a license for the accessing device and the virtual desktop. One of the things that was a big impediment to VDI was Microsoft’s licensing policy for virtual desktop machines. 8. consider the additional cost of air conditioning. 11 . but virtualization techniques such as memory sharing and only allocating the memory actually needed may mitigate some of that. that more resources may be needed on the servers if the virtual desktop OS is upgraded. preventing application incompatibilities Application virtualization. The power consumption depends on the model. 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. 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 allow access to VDI installations of Windows and Office without a separate license for the accessing device as long as the customer has either Software Assurance (SA) or a Virtual Desktop Access License (VDAL). 7. they changed their licensing policy on July 1. so the power drain is the same as long as unit is on. Note. Copyright ©2011 Global Knowledge Training LLC. while others don’t go into standby. This technique allows the same application to be packaged and run on multiple operating systems without any modifications.

The basic diagram of how this technology works is illustrated below.. 10. patching. with all other writes going to the sandbox. 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 don’t need many different OS images – in fact. it can do so from the application’s version (inside the file) or from the system’s registry (depending on what it is looking for). and can write to your user profile location and some normal system locations. you can have as few as one with applications installed as needed (or even not installed at all via ThinApp. If the app needs to read a registry entry. The file is represented by the blue box labeled ThinApp Virtualization and contains the virtualization layer (common to all applications). etc. user profile. 12 . but does not contain anything other than a single file for the entire application (and that file can be located on a file share. as previously described). Application testing. or any combination of the two. Any writes to the registry go to the sandbox. This technology can be used with either physical or virtual computers. The net result is that the application is unaware that it is virtualized. The same principle is used for files – you can read from within the application or from the OS locations. the view from within the application looks like it is natively installed. As illustrated in the purple box. just as a virtualized desktop OS doesn’t know that it is virtualized. All rights reserved.. as well as any application files and registry settings that the application needs. or copied locally). a directory where all writes for the application are stored (there is one directory per ThinApp application that is used). also become much simpler in this environment. There are several reasons for Copyright ©2011 Global Knowledge Training LLC. The diagram shows how the OS has the system files. registry. etc. on a web site. like any other application.

though linked clones will consume a lot less disk space than a full clone. making application maintenance quick. but linked clones make application image updating and maintenance quite a bit simpler. with the additional benefit of space and bandwidth savings (vs. All rights reserved.. it is just a few clicks to deploy either type of clone. it takes just a few clicks to put them in the image itself. then deploy the changes (including Windows Updates. 13 . you can use VMware snapshots before deploying any patches. Second. The extra functionality that linked clones offer are twofold. etc. deploying the same changes hundreds or thousands of times). In fact. there is no need for images for different hardware platforms – they all are VMware VMs and thus the hardware platform is abstracted. test it to make sure it works properly. This means any Windows Updates. etc. linked clones make it simple to create and manage OS images. which will be discussed shortly. Finally. the OS drive (but not any user data) is reverted back to the master image and any changes or updates will be lost. which will also be discussed later in this document. One quick note here: If ThinApp applications are used. this is the primary reason that this option exists – to control the disk space utilization. to simplify roll back when issues arise during testing to revert to the original state of the VM. will be removed as well. When refresh is chosen. As illustrated in the diagram below. First. In addition. and any other files or documents the administrator wants to distribute) with just a few clicks. any user who is currently connected will typically be given a warning then automatically logged out if they don’t do so before the warning interval expires. linked clones can be used with ThinApp to reduce the number of OS images by deploying applications as needed. they can be refreshed and second.this. new applications. other application patches. first. Copyright ©2011 Global Knowledge Training LLC. Note that both refresh and recompose options are disruptive. new applications. as previously described. Desktop management operations Both full and linked clones provide many options to deploy the operating system. etc. easy. they can be recomposed. On the other hand. but the space the changes consumed will be made available again. meaning that no users can be using the image when the operation is begun and for the duration of the update.. applications.. The recompose option allows an administrator to update the master image. 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. new applications. if the application or patch works successfully.

while App 3 is only used by the accounting department and thus only distributed to them. App 1 is needed by everyone. By controlling who can run the application.Linked clones require View Composer to be installed on the vCenter server to be created. making it simpler to deploy the applications and control licensing. 14 . so is distributed to only their computers. so it can be placed in the OS image. ThinApp also allows restrictions based on the Active Directory groups the user belongs to. View Administrator. The administrator then determines who will get each application. 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. maintained. Application deployment using View and ThinApp Application deployment with View 4. the management interface for View. can be used to deploy the application to only the desired computers. In fact. App 2 is used only by sales and marketing personnel.5 (or later) and ThinApp is quite simple. All rights reserved. licensing costs can be reduced. In the diagram below. and deleted. Copyright ©2011 Global Knowledge Training LLC. three applications have been created and placed on a file server. The administrator defines as many applications as he or she wants (one at a time).

VMware ESX(i) servers managed by vCenter provide a very strong foundation for a VDI implementation. capital (over the medium to long term).Summary There are many ways that a VDI infrastructure can save a company a lot of money as long as it is properly implemented and savings are looked for in the right places. Finally. using thin clients instead of the traditional thick (or fat) clients can lead to even greater savings in administration. and 7 machines easy and saves a lot of administrator time and optimizes resource utilization. which does not have an equivalent vSphere certification). Related VMware Certifications VMware has just introduced a series of desktop certifications similar to those available for vSphere (with the exception of the VCA. Vista. That is not to discount the upfront costs. The available certifications are: • VMware Certified Associate 4 – Desktop (VCA4-DT) • VMware Certified Professional 4 – Desktop (VCP4-DT) • VMware Certified Advanced Professional – Desktop (VCAP-DT) Copyright ©2011 Global Knowledge Training LLC. and cooling. The View 4. but simply to take a longer and more inclusive view in determining ROI (Return on Investment).5 ICM class supports the objectives for all three exams. 15 . View makes management and deployment of Windows XP. power. These certifications are independent of the vSphere certifications. 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. All rights reserved.

in addition to custom courseware for individual customers. delivered through Classrooms. and On-site sessions. John lives with his wife and children in Sunrise. Manage [V4. John is also the author of many books. Our expert instructors draw upon their experiences to help you understand key concepts and how to apply them to your specific work situation. and MCT. hands-on labs and exercises offer practical skills and tips that you can immediately put to use.Learn More Learn more about how you can improve productivity. MOUS. All rights reserved. visit www.5] For more information or to register. Configure. VCI. and the CompTIA A+. Copyright ©2011 Global Knowledge Training LLC. the Microsoft MCSE. from involved technical books from Sybex to exam preparation books. is a VMware instructor at Global or call 1-800-COURSES (1-800-268-7737) to speak with a sales representative. the EMC EMCSA (Storage Administrator for EMC Clariion SANs). e-Learning. including the VMware VCP and VCI. including the new View classes.200 courses. teaching all of the vSphere classes that Global Knowledge offers. Check out the following Global Knowledge courses: VMware vSphere: Install. Manage [V4. MCDBA. enhance efficiency. Florida. Choose from our more than 1. to many quick reference guides from BarCharts.1] VMware View: Install. John has various certifications.globalknowledge. and CTT+. About the Author John Hales. Network+. Configure. to meet your IT and business training needs. VCP. Our courses and enhanced. 16 . and sharpen your competitive edge.

Sign up to vote on this title
UsefulNot useful