Академический Документы
Профессиональный Документы
Культура Документы
Desktop Virtualization
Choosing whats right for your organization
With Compliments
freeformdynamics.com
Desktop Virtualization
Choosing whats right for your organization
Terms of Use
This document is Copyright 2011 Freeform Dynamics Ltd. It may be freely duplicated and distributed in its entirety on an individual one to one basis, either electronically or in hard copy form. It may not, however, be disassembled or modified in any way as part of the duplication process. Hosting of the document for download on the web and/or mass distribution of the document by any means is prohibited unless express permission is obtained from Freeform Dynamics Ltd. This Smart Guide is provided for your general information and use only. Neither Freeform Dynamics Ltd nor any third parties provide any warranty or guarantee as to the suitability of the information provided within it for any particular purpose.
The Microsoft logo is a registered trademark of Microsoft and is used under license.
Contents
Introduction Who is this book for? Why is this topic important? Meeting todays desktop computing needs What is desktop virtualization? Desktop virtualization models So how does any of this help? Benefits of centralized management Benefits of minimizing dependencies Unlocking the benefits Analyzing your requirements Selecting the right options Mapping options to needs Infrastructure considerations Management considerations Tips for success Closing advice Further reading 4 4 4 6 8 10 13 13 13 14 14 17 20 22 23 25 26 28
Introduction
Welcome to the Freeform Dynamics Smart Guide to Desktop Virtualization. This book provides some pointers to help you decide whether desktop virtualization is right for your organization, which options are appropriate and, depending on your needs, how you can prepare for a successful implementation. Desktop virtualization is more straightforward than you might think. After reading this book, we hope youll feel comfortable working out your organizations needs and be in a position to understand which options will be most suitable for meeting them.
PC, laptop, or other type of device such as a netbook, tablet or slate, the desktop client represents the primary point of access for users into business systems and information. How well the desktop environment performs, and the richness and quality of the experience it delivers, has a big impact on user productivity. It also has a disproportionately high influence on business users perception of how well IT is being managed. Furthermore, allowing the desktop environment to drift out of date has tangible cost and risk implications, as well as increasing the workload on IT staff. These are some of the reasons why desktop modernization is now back on the mainstream agenda following a period of investment deferral. Putting normal refresh cycles on hold because of difficult economic conditions and perception issues around Windows Vista was understandable, but inaction can only be sustained for so long before costs, risks and productivity issues start to sneak up on you. Against this background, the release and widespread acceptance of Windows 7 has acted as an important catalyst to get things moving again. But as you put your plans in place to move forward, it is important to take a step back and consider how user and business needs have been evolving.
Ensuring that business requirements around security and compliance (where relevant) are met. Key here is the centralization of management, application execution and/or data storage in a way that enhances visibility and control, but without undermining the user experience or unduly constraining user flexibility. Reducing the overhead on IT staff and enhancing their ability to maximize quality of service to users. Important keys here are the simplification of application development, deployment, and maintenance, and the efficiency gains that stem from a more centralized and streamlined management approach. Sound too good to be true? Well the truth is that there is not a single technology magic bullet that delivers against all these needs. The first lesson to take on board is, therefore, that desktop virtualization is about blending a mix of technologies and approaches to achieve the optimum result for each type of user. With this in mind, the remainder of this Smart Guide helps you think about the desktop needs of your own organization, and sets out the options so you can decide whether desktop virtualization principles in general, and specific delivery approaches in particular, are appropriate in your environment. To keep things simple during our discussion, we use the term desktop client to refer to desktops, laptops, notebooks, netbooks and tablet computers. We use the term server to refer to a computer that sits in a computer room or data center and is accessed remotely, by desktop clients.
So, lets start out with a quick primer on the basic principles and approaches.
Display User Data and Settings Settings Application Operating System App Hardware Traditional Desktop Model
Display Data
Server or Client OS
Virtualized Model
Figure 1: Breaking the traditional bindings between layers. As shown in this graphic, while the display will always run on the desktop client (otherwise it would be quite hard for users to see what theyre doing!), you have a choice about whether the operating system and applications are run and/or managed on the desktop or from the server. A similar choice exists about where user information such as application data and configuration settings are stored. Fortunately, its not necessary to make decisions in this area from first principles as a number of proven approaches or models have emerged to cater for frequently occurring requirements and objectives. Lets take a look at these.
10
in a self-contained manner so they run in their own protected environment. They can still make use of local resources and interoperate with other applications (through cut and paste, dynamic links, etc.), but dependencies and, therefore, conflict-related issues are minimized. Server-hosted desktop: Session virtualization approach Session virtualization is derived from the thin client or terminal services architecture model popularized by Citrix in the 1990s. Multiple desktop clients log onto a single multi-user instance of an operating system running on the server. Applications or entire desktops run on the same server, and the display graphics are transmitted to desktop clients. The client can be thin because it only needs to handle the display; indeed ultra-thin clients contain little more than a network port and a graphics card. However, session virtualization can also be implemented using software-based thin clients, allowing it to be mixed with the traditional approach e.g. running some applications locally and others remotely through a thin client window. Server-hosted desktop: VDI approach Virtual desktop infrastructure (VDI), is a variation on the thin client idea. The difference is that while one server is used to service the processing needs of multiple users, each user has a dedicated operating system instance running on that server as a discrete virtual machine, within which their applications are executed. In effect, server hardware resources are shared, but each
11
users environment is maintained separately from a software and configuration point of view. This VDI model is often whats being referred to when the term desktop virtualization is used generically, but in reality it relates to just one specific approach. Server-hosted desktop: Dedicated blade-based Blades are standardized server computers designed to slide into a specially designed rack (like books on a bookshelf) to minimize space and power requirements. Like session virtualization or VDI, the blade-based virtualization model means that processing is done on a server and the display is transmitted to the users desktop. In this case, however, each blade runs just a single instance of the operating system, which is allocated to an individual user on demand at runtime. While the user is logged in, they therefore have hardware resources dedicated to them. Client-hosted desktop virtual machine For completeness, we need to give a mention to the model in which multiple virtual machines are run on a single physical desktop (sometimes known as client partitioning). The difference between this and other models we have discussed is that the virtualization software runs on the desktop computer itself rather than on the server. The model was originally popularized by IT engineers to create multiple operating system installations for different development, testing and troubleshooting purposes on the same machine. Today, the approach is also used in migration scenarios, e.g. to run an XP instance behind a Windows 7 installation to support older applications. It is also used in the context of consumerization, e.g. to run a managed corporate partition alongside an unmanaged personal one, or a Windows installation alongside OS X on a Mac.
12
13
applications more quickly, and can even benefit from self-service application provisioning. Separating applications from each other minimizes conflicts, which means fewer interruptions because of crashes and machine instability. Business continuity in general is also enhanced, e.g. if a local desktop or even the entire office fails, users can access their work from other (appropriately configured) machines, including from home.
applications in use is very high. Profiling exercises dont have to be onerous, however, as you can focus initially on a subset of users in a specific department and/or use automated discovery tools that interrogate user machines over the network to speed up data gathering. In practice, its important to identify all applications that users currently have installed, exactly as you would in preparation for a traditional desktop migration project. Just as with a migration, its then useful to distinguish between critical applications and those that are less important or even totally unnecessary. If there is rationalization or consolidation to be done, then its best to identify which applications are going or staying before getting into any virtualization activity. Questions to consider during analysis include: Which applications are important to the user? Is this application set relatively static or frequently changing? Are any applications ever operated on slow or less reliable networks, or even in disconnected mode? Are there any special security or compliance concerns? Does the user rely on any applications that are particularly compute- and/or graphics-intensive? Do any applications need to be configured or managed by the user as opposed to by the IT department? Where you end up once you have gone through your analysis will depend on the nature of your workforce and their working patterns (or the ways of working you want to enable). To provide a flavor of
15
what might emerge, we have listed some examples of typical user groups in Table 1. Table 1: Commonly defined user categories User Category Examples IT development Software developers, architects and testers staff requiring access to a frequently changing set of applications. IT operations/ support staff General professional users Transaction workers Other (non-IT) technical and creative staff Office-based power users Mobile/remote professional users Technical and admin staff routinely using a core set of applications, but who may, on occasion, require access to a broader application set. Senior management and administrative business users making relatively light and predictable use of email, office tools and so on. Business users in fixed roles, mostly using enterprise applications in a routine, prescriptive manner. Research and development staff, engineers, technical designers/architects, graphics designers requiring access to specific and/or more graphics-intensive applications. A subset of business users with more complex application needs; for example finance staff, marketing teams and business analysts. Similar to power users but also requiring access when on the road or from remote locations, such as sales executives, roaming managers and service engineers.
16
At the end of the profiling exercise, for each user category you should have a good feel for: Applications used by the individual categories. The required level of management control. The required level of user flexibility. Additional benefits youre hoping to achieve, such as improved security and availability. You can then move on to look at where the different forms of desktop virtualization are going to be useful.
also improves availability because user data and configuration information are stored on a central server. There are no significant downsides to this option for users, the business or IT. Pros and cons: Application virtualization One benefit of application virtualization is user flexibility, as applications are linked to users independently of specific machines. This approach also offers application stability and reliability, given that each virtualized application has its own protected configuration. IT managers can build and deploy cleaner operating system images and reduce the time they spend on application interoperability testing, packaging, deploying, updating and troubleshooting. Where application vendor terms permit, there may also be scope to reduce licensing costs by providing access to certain applications only when needed. The downside of application virtualization is arguably more up-front work to package applications, but this pays dividends down the line for both users and IT staff. Pros and cons: Session virtualization The main benefits of session virtualization stem from the centralization of control and data storage, along with standardization of the desktop environment. A degree of flexibility is provided in that multiple configurations can be created to meet the needs of individual user categories, but there is a limit to how much users can tailor their own desktops. The other big constraint is the dependency on a good network connection, limiting usefulness for mobile users and in locations with poor or intermittent connectivity. Pros and cons: Virtual desktop infrastructure (VDI) As with session virtualization, the main benefit of VDI is centralized control, but the model also enables considerable flexibility when
18
it comes to offering different options for different user categories; indeed it can even handle individual user differences. This model also has availability benefits because virtual machine images can be more easily copied or moved than a physical machine. However, based on a virtual machine per user, VDI requires more server and storage resources than session virtualization. With a similar dependency on the network, VDI has the same constraints as session virtualization in this area. Pros and cons: Dedicated blade-based virtual desktops This model is applicable to users requiring heavy processing and graphics applications such as computer-aided design or where low latency and resource availability need to be guaranteed. However, the one-blade-per-user model is relatively expensive in hardware terms compared to deploying session virtualization or VDI, and still relies on network connectivity. Pros and cons: Client-hosted desktop virtual machine The single-desktop model offers flexibility to individual users, particularly where its necessary to separate business from non-core working; for example, to run a business environment on personal equipment, or to keep multiple client environments separate. This is also a popular approach for software developers to create separate environments on the same machine, e.g. for development and testing. There are potential management-related benefits arising from central control and distribution of virtual machines, but this is dependent on having the appropriate tools in place.
19
20
requirements, and how they are going to be met, simply and clearly, as in these examples from a few different organization types: Academic institution: Full flexibility for researchers; tightly controlled desktops for admin staff; mixed desktops separating tightly controlled faculty apps and data from the personal environment for students. Financial institution: Full flexibility but with rigorous data management for front-office staff; tightly controlled fixed desktops for back-office and customer service users; controlled environment for sales reps, but with an ability to work offline in the field. Mainstream enterprise: Minimalist and highly controlled desktops as standard, with an emphasis on accessing Web apps and a pre-defined set of productivity tools; locked down mobile environment for blue collar field workers; more flexible mobile desktop for roaming professionals; powerful but fixed-function desktops for finance staff. These examples are clearly not exhaustive we have not attempted to cover all types of organization and, even within the ones we have touched on, there may be more user types than those we have mentioned. Furthermore, requirements for similar looking user segments may vary between organizations based on culture, politics, compliance requirements and so on; hence the importance of analysis. The point is that it should be possible to summarize requirements in non-technical terms, which will enable the review and refinement of needs with managers and users.
21
Infrastructure considerations
From an infrastructure perspective, its important not to underestimate how much network bandwidth is required for remote displays in the case of session virtualization, or to misjudge how many users can work in parallel on a single server in the case of VDI. Making sure that central storage platforms can meet expected peak demands without impacting user response times, e.g. as virtual machines are booted at the beginning of the day, is something else that must be considered. Ideally, the virtualized desktop experience will be as good as, if not better than the user has traditionally experienced, and this can only be achieved if the infrastructure is up to the job. Suppliers can often help with analysis and sizing exercises if you are not comfortable doing this yourself. Either way, to maximize the chances of success, it is important to thoroughly test the proposed configuration, and preferably run a pilot with a select group, to ensure the setup delivers the expected service levels. And beyond the technology, dont overlook user training. While the differences in user experience between the old and the new may appear to be small, during training you can ease the transition and also identify any last-minute gotchas, such as missing applications and shortcuts.
22
Management considerations
Desktop management isnt straightforward at the best of times, and while desktop virtualization will usually help with many operational requirements, its worth thinking through some specifics up-front, including things like: Asset management: Desktop virtualization should make configuring individual desktops simpler, but you still need to maintain an accurate knowledge of devices, users, software deployments, usage, and so on. License management: Ensure that the licensing regimes and agreements with software vendors are appropriate for your virtualized environment. Software distribution and patch management: Both of these should be more straightforward with desktop virtualization, depending on the option you choose, but operational processes may need to be adapted. Help desk: As well as expecting a larger than usual influx of calls during the transition period, make sure that your support processes are geared up to the specifics of virtualized desktops and applications, and that your help desk staff have been trained with the new solutions in mind. Health monitoring: Ensure that desktop clients, physical and virtual, run efficiently and deliver the required services to their users.
23
Backup and recovery: User data as well as application and configuration settings need appropriate backup and recovery, as, of course, does the server and storage infrastructure that drives everything behind the scenes. Management and operations of the virtualized desktop environment should be more straightforward than administering an equivalent number of traditional desktops. However, therell also be management best practices specific to the virtualized desktop environment for example, how to minimize the number of images you need to support. Again, seek help from suppliers where necessary. Lastly, you probably wont end up with an entirely virtualized desktop estate youll be managing both physical and virtual machines in parallel. By considering the management and operation of both physical and virtual resources from the start, you avoid the possibility of uncovering hidden costs and problems later on. With this in mind, implementing management tools and associated processes that work across both physical and virtual environments, or upgrading your existing toolset and operating procedures as necessary, will also help to manage overall service levels, overheads and costs.
24
25
Build in continuity, data protection and security: Its critical to make sure that the risk management element is an integral part of your up-front analysis, making sure that the needs to do with protecting user data and countering security threats are understood. Be inclusive when considering the cost: Implementing desktop virtualization will almost certainly require investment in server hardware, software, management tools and implementation effort. Upgrades to your network and storage infrastructure may also be required. Be inclusive when considering the benefit: Some benefits may translate to direct quantifiable savings, e.g. prolonging the life of desktop hardware, streamlining of the application lifecycle, and reduction in support and operational overhead. Other savings may be less quantifiable, such as the removal of downtime, the boosting of user productivity, or the enablement of new ways of working.
Closing advice
We have talked about some very compelling ideas and technologies, and its easy to get drawn into the visions of ultimate efficiency and flexibility often painted by IT vendors and pundits. As we highlighted right at the beginning, however, changes to the desktop can have a direct impact on employee productivity and the relationship between IT and the business. Its a highly sensitive area. With this in mind, the worst thing you can do is force-fit desktop virtualization options into situations where they dont really belong. Any tactical gains in terms of IT control and efficiency could be
26
more than undermined by user disruption and political fallout, making life more difficult for everyone. So, if you take nothing else away from this book, at least remember the importance of understanding your users and their requirements before taking any action in this area. Thats the place to start before getting bogged down in technology capabilities and implementation practicalities. With that, we hope our Smart Guide has provided some helpful insights into where and how desktop virtualization might be relevant in your organization, and we wish you luck in plotting the appropriate course to success.
27
Further reading
User Virtualization (Smart Guide Mini-Book)
Beyond device-centric computing
28
About Microsoft
Founded in 1975, Microsoft (Nasdaq MSFT) is the worldwide leader in software, services and solutions that help people and businesses realize their full potential. See here for more information on Microsoft desktop virtualization solutions: www.microsoft.com/DV
This book was written independently by Freeform Dynamics and sponsored by Microsoft.
Desktop virtualization has progressed from a niche way of handling exceptional user requirements to a mainstream IT delivery approach. Technology has matured to provide options ranging from terminal services through application and user virtualization to a full-blown virtual desktop infrastructure. All in all, there have never been more ways to optimize desktop service delivery. But where do you start and whats the best way forward? With these questions in mind, and against the backdrop of increasing workforce mobility and consumerization, this Smart Guide walks you through the options available and how to blend them optimally to meet different user needs. The rewards for IT and the business are better cost and risk management, while for users, its all about enabling flexible and efficient working. Get it right, and everyone benefits!
FD 12 11 www.freeformdynamics.com