Download
1 / 28
280 likes | 410 Vues
Desktop Virtualization: Key Implementation Considerations. See the Impact Report “Desktop Virtualization: Assessing Organizational Appropriateness” to determine organizational fit. Executive Summary. Research Method.
E N D
See the Impact Report “Desktop Virtualization: Assessing Organizational Appropriateness” to determine organizational fit. Executive Summary
Research Method The desktop virtualization Impact Reports are based on results from 204 surveyed IT managers and in-depth interviews with 30 IT leaders. All major industry segments, sizes of organizations, and revenue brackets were represented. Organizations at all stages of implementation or consideration of desktop virtualization were represented. Research Method
“Overall I would rate the implementation successful. The most pleasing thing to me is that customers are happy. When they are happy, I am happy.” IT Director, State Government Success of Desktop Virtualization Challenges of Desktop Virtualization Majority of stakeholders satisfied with desktop virtualization implementation • The majority of stakeholders achieved satisfactory success with their desktop virtualization implementation. • Ideally, end users should see a slight improvement in performance of their desktops, or no change at all.
Desktop virtualization costs less than traditional desktops Success of Desktop Virtualization • Desktop virtualization was found to cost less than traditional deployment more than 75% of the time. • In terms of cost savings and efficiency improvements, desktop virtualization has a greater potential in longer term desktop management operations (desk side support reduction, apps delivery and maintenance, upgrade deployment and management). • Pitch desktop virtualization as a small savings now, but a larger savings later.
Implementations meet the planned budget. Most projects met their budget. One variable that impacts the cost per virtual machine is the density of VMs that could be stored per server. If this turned out to be less than what was promised by the vendor, the budget was impacted. Few budget and schedule surprises in DV projects Success of Desktop Virtualization • Most projects were completed on time. Implementers hadoften spent time piloting small installations of virtual desktops. By piloting a small virtualization deployment, organizations were better prepared for the full implementation. • Experience plays a role in meeting budget and time estimations. Users who had implemented server virtualization were far more likely to select the same vendor for desktop virtualization. In these cases, the organization can leverage the skills, experience, and tools developed in managing virtual infrastructure for servers for the deployment and management of virtual desktops. This ability increases the accuracy of budget and time estimations.
The implementation plan needs to include steps to address the most common DV implementation challenges A good implementation plan will take into account key potential challenges that have been identified by other organizations. For more about the main challenges to virtualization, refer to the Impact Research Report, “Desktop Virtualization: Assessing Organizational Appropriateness.” Success of Desktop Virtualization
Implementing Desktop Virtualization Step 2: Network & Broker Connection Project Planning & Piloting Step 3: Access Devices Step 1: Server Considerations Communication Strategy
Proof of concept pilot a valuable first step Project Planning & Piloting • Conducting a proof of concept pilot provides the organization with the IT and end-user experience and executive buy-in necessary for successful deployment. • Piloting with a small group of users was rated as the most important activity to ensuring project success. One organization deliberately choose users needing performance for their pilot based on the premise that this was the group that had to become regular users of VDI for it to be successful.
Look for low hanging fruit for pilot project For early stage pilot projects, look for low hanging fruit scenarios. These will provide proof of concept while also achieving short-term cost savings. Some of these scenarios include: “The 15 people for the pilot were folks who were due for a new computer, so some of their PCs were considerably old. The performance boost that they felt on the VDI was enough for them to buy in. The feedback was, ‘sign me up.’” IT Director, Financial Services Project Planning & Piloting • Virtual Test Lab.Create a test lab of server-hosted virtual PCs to test a new application or an operating system upgrade. By doing so, a separate set of test PCs is not required. This is especially useful if the test requires memory and processing capacity greater than that of the testers' machines. • Alternative for Laptops for Remote Desktop Deployment.Instead of deploying company laptops to secure remote computing end points, provide remote users access to virtual desktops from their own device, such as a home PC • Pilot with Users Ready for a Hardware Refresh. These users will likely be more willing to participate in the pilot, and may see a performance boost which will increase user buy-in.
Other key planning steps include gaining support, training, third-party help, ROI analysis, and testing Project Planning & Piloting
Build the desktop virtualization deployment back to front Traditional desktop implementation begins with what hardware and software will be required on the desktop followed by what network services the desktop will require for accessing additional back end services (e.g. an e-mail server and shared network storage). Desktop virtualization deployment begins at the server. The required desktop OS and software are implemented on virtual machines hosted on the server. Next up is the network assets and the brokering software that will connect the end user to their desktop computing environment. Finally there is the access device. This could be a desktop computer, laptop, or thin client device. 1 2 3 Server Considerations Access Device Server and Virtualization Network and Broker
Server considerations: provision generously Server requirements will include a virtualization hypervisor (e.g. VMware ESX, Microsoft Hyper-V, Citrix XenServer). Multicore and multiprocessor (two or more) servers are best. Plan for five or six VMs per processor core. Mileage will vary greatly depending on VM usage. Don’t skimp on memory. At least 512 MB of RAM allocated per active virtual PC. For example, 16 VMs on a host at 512 MB each would require 8 Gigabytes of memory. Storage (e.g. DAS or SAN) is also a critical consideration. However total storage impact is being mitigated by changes in DV software. 1 Server Considerations Server and Virtualization Plan 5 to 6 VMs per Processor Core The number of VMs that will run on a server will vary greatly depending on applications and workload. VMware, for example, estimates up to 42 “light duty” VMs can be hosted on a dual processor dual core system (10.5 per core). Info-Tech finds that for planning, a more conservative estimate of 5 or 6 per core is more realistic. Using a dual processor dual core server, a 6 per core estimate yields a VM density of 24 VMs on the server. 6 VMs X 4 Cores = 24 Desktops The majority of DV evaluators and implementers are leveraging previous experience in server virtualization for virtual desktops.
Make the connection: brokers, protocols, bandwidth The desktop virtualization solution will use a remote connection protocol to link the end user to the hosted virtual desktop over the network link – typically Remote Desktop Protocol (RDP) or Citrix ICS. Connection broker software authenticates the user and establishes the connection. Connection brokers are normally included with desktop virtualization solutions. Broker software typically can connect users not just to virtual desktops but also to blade PCs, server hosted applications, and virtualized applications. For network bandwidth, plan for 25Kbps of dedicated bandwidth for each virtual desktop. So, for example, for 16 virtual desktops per server, 400Kbps of dedicated bandwidth would be required. 2 Network & Broker Connection Remote Connection:It’s All the Same A remote access connection differs little whether the user is being connected to a Virtual PC, a server based application, or a blade PC or workstation. If usability of an application is affected by remote access issues (e.g. latency in graphic refresh), the problem will be the same regardless of where it sits. In other words, you won’t fix these kinds of problems by moving the application from, for example, a Terminal Services server to a virtual desktop. Network and Broker
VMware and Citrix lead the vendor pack by a large margin Over 75% of organizations don’t consider vendors outside of VMware and Citrix. Most of these implementers don’t consider other vendors because they find it a natural progression to go with the vendor they use on the server virtualization side. Network & Broker Connection
? Visit VMware for more product information. Network & Broker Connection VMware: leveraging server virtualization to the desktop In 2009, VMware launched an updated product called VMware View, which combines the former VMware Virtual Desktop Infrastructure (VDI), Virtual Desktop Manager (VDM), and elements of VMware ACE for offline “checking out” of VMs to disconnected laptops and desktops. In addition to virtual desktop management and connection brokering, the Premier edition of VMware View also includes VMware ThinApp for access to application virtualization. View can also connect users to remote PCs and blade workstations. • VMware Positive Solid pricing, improved management, new innovations like offline desktops (though not yet ready for prime time). • VMware Negative Rapid development making it somewhat of a moving target for implementers. VMware View Brochure
? Visit Citrix for more product information. Network & Broker Connection Citrix: taking application delivery to new territory Citrix has expanded on its history of “application delivery” to the desktop (via Terminal Services and Thin Clients) to hosting full virtual desktops. XenDesktop manages virtual desktops on Citrix’s XenServer hypervisor but also on VMware ESX Server or Microsoft Hyper-V. XenDesktop integrates with Citrix’s application presentation and virtualization (XenApp) and a provisioning server for dynamic assembly of user desktop (e.g. OS, applications, settings) for lower storage requirements and a “new desktop” at each connection. Citrix Positive Dynamic provisioning, Hypervisor agnostic.Low entry price. Citrix Negative.. Cost concerns from implementers. Deluxe editions include XenApp licensing.
Network & Broker Connection There are other emerging desktop virtualization vendors
The access device: multiple options available The end user access device is the last consideration in the desktop virtualization roll-out. The desktop equipment is essentially an access point for the centrally hosted desktop service. It can be a thin client device but it can also be a re-purposed PC or laptop. Desktop virtualization and thin client hardware are not synonymous. There are a number of scenarios where real benefit can be gained from accessing virtual desktops from regular PCs and laptops. Fully 91% of implementers plan to use some thin client hardware though only 7% plan to use all thin clients – the rest use a combination of thin clients with fat clients and/or laptops. 3 Access Devices Access Device • Using DV to delay PC refresh. Where clients receive a workstation upgrade via virtual machine but continue to use legacy hardware. This approach is used when the organization wants to save money on hardware and are able to extend the life of the hardware by using VDI. • Providing Offsite Access to Full Desktops. As noted earlier, desktop virtualization can enable off-site access (e.g. from a user’s home PC) to secure desktops via VPN connection. • Bring Your Own Laptop (BYOL) programs. Where employees bring their own laptop to work and use it to access a secured virtual desktop separate from their own personal desktop.
Where appropriate, thin clients have benefits Reduced costs of electricity per desktop as there is no longer a disk and cooling fan to spin. Deskside support costs are driven down. No moving parts means less maintenance. Less wear and tear means lifecycles can also be extended further than PCs. Improved user experience. If the user is accessing a virtual desktop from legacy hardware, thin client hardware with better media handling (e.g. sound, graphics) will improve the end user experience. Reduced hardware costs for desktop refresh. Thin clients could provide 5 to 10% overall per desktop cost reduction when a refresh becomes necessary. “Because of the economy right now, we’ve been buying clearance stuff. We go to the CDW Outlet, or if they have a return, we just buy them up, and we've been getting thin clients under $100 each.” IT Executive, Non-Profit Organization Access Devices
HP and Wyse clear leaders in thin client selection HP and Wyse are clear market leaders among those evaluating and selecting thin client solutions. Others contenders include: iGel, ChipPC, ClearCube, PanoLogic. Access Devices
There are many viable thin client options to choose from Access Devices
Focus on service delivery in your communication strategy Communication Strategy There is only one question that really matters in any IT communication strategy: How will this initiative impact service? Key Messages For DV Project Success How Not To Communicate DV • Desktop Virtualization will make life much easier for IT. More important is how it will impact the work of end-users. • This will save the company money.Good news to be sure but will the true cost be borne in a poor use experience and reduced service? • This initiative will user proof tech assets. Suggests that primary goal is protecting assets from users. Speaks to an asset service rather than end user service focus. • We’re coming for your PC this week. • DV provides a full Windows desktop. Will not require a change from familiar desktop environment regardless of access hardware. • Less downtime, faster application loading, and improved performance. This is particularly true of data-intensive applications. • Desktop performance will not degrade over time. A virtual desktop generated from a master template does not accumulate system junk over time. • Rapid deployment for new applications and upgrades. Such as an upgrade to Office 7 or Windows 7 without desktop hardware replacement. • Access your desktop from multiple points. Also . . . • Develop and communicate contingency plans for candidates that are not a good fit. How will those who find that DV does not perform well enough be served? • Be clear about implementation glitches that might occur. For example, pilots where an “it might be slow at first” message was communicated had better success than where end users were left to make snap first impression judgements.
“We implemented it with Wyse clients and I was shocked how well the products ran – performance is great, no blue screen of death and stability is great.” “I’ll be the first to admit it, but I’m actually surprised by how well Microsoft products run when you remove hardware from the factor.” Case Studies Happier end users were the result for a manufacturing organization’s implementation
“We're very happy with the VDI environment. We have drank the VMware Kool-Aid and we're certainly on side with that product. Working with the consultant as well as with VMware, has just been a fantastic relationship and they've done a wonderful job.” Case Studies Consultant used for implementation to resolve peripheral device issues and ROI calculation
