Tuesday, June 16, 2015
VDI solutions
- The dominant virtual desktop applications are VMware Inc.’s VMware View and Citrix Systems Inc.’s XenDesktop.
XenDesktop can run on Citrix’s server virtualization platform, XenServer, vSphere or Microsoft’s Windows Server 2012 Hyper-V platform.
Microsoft also offers a virtual desktop product called Microsoft Windows Server 2012 Remote Desktop Services, and Dell Inc. has its own VDI offering called vWorkspace.
Persistent vs. stateless desktops
A persistent desktop contains everything the user needs within the virtual desktop image and the individual VM.
All of the applications, documents, settings and profiles are tied to the individual desktop and VM.
A stateless desktop uses one master image for all users (also referred to as a “golden image”), and the profiles, settings and applications are streamed to the thin client
A stateless environment uses a single image for all virtual desktops, eliminating the need to store individual images for each user.
Instead of updating each virtual desktop individually, an update or patch to the one image updates every virtual desktop.
you can begin your deployment with a persistent setup and migrate to a stateless environment later.
http://searchvirtualstorage.techtarget.com/feature/Control-VDI-costs-for-storage-by-careful-configuration-planning
- Citrix XenDesktop 4.0 Platinum
judgment: "Suitable for departmental-level deployments and for SME-class organizations."
Strengths:
Flexible delivery
Supports multiple virtualization servers
Strong user-experience feature set
Diverse endpoint OS support
Strong WAN performance
Rich supporting ecosystem
Weaknesses:
Security logging and auditing of administrative actions
3 year support for entire product portfolio
VMware View 4.01 Premier Edition
Judgment: "Not...an enterprise-class SHVD platform"
Note: "Upcoming VMware View 4.5 (in beta) release satisfies the required feature shortcomings."
Strengths:
Rich integration with VMware vSphere
Solid but incomplete core feature base
PC-over-IP performance better than expected
Simple deployment
Active directory integration
Enterprise management
Weaknesses:
Role-based access control or security hardening guidelines
Enterprise management integration
No user application self service
Low-bandwidth WAN support
Supports only VMware backend
Management console scalability limited
Win7 Guest OS support
http://www.cio.com/article/2417986/virtualization/desktop-virtualization--top-vendors-still-miss-the-mark.html?page=2
- SHVD (Server Hosted Virtual Desktops) Infrastructure Costs: VMware View 4 vs. Citrix XenDesktop 4
vendors have developed unique virtual infrastructure platforms.There are many variables involved in determining implementation expenses, but they principally fall into three distinct categories: server, storage, and software
All three of these cost elements should be carefully evaluated prior to investing in a SHVD solution to ensure value is achieved in deploying a solution that best meets organizational requirements
Comparable implementations have been established based on recommended configurations derived from publicly available sources
The configurations have been developed to include the minimum number of components necessary to support small (800 VMs), medium (3000 VMs), and large (10,000 VMs) infrastructures
The resulting configuration profiles were submitted to their respective vendors for independent review and their comments have been incorporated to ensure a fair and accurate comparison
It should be noted that this analysis did not include a full functional comparison as the feature sets of the two products are not completely identical
Each organization should perform product evaluations based on its own unique requirements. The data provided here is intended to help indicate a starting point for that process
1Server Components
All SHVD implementations require physical servers for hosting, managing and delivering virtual desktop instances.
These hardware components are typically deployed in data centers and supported by acentralized IT operations team.
Although a total cost of ownership (TCO) evaluation would involve all infrastructure expenses including those for
power consumption
HVAC
backup and disaster recovery(BDR)
maintenance
support staff compensation for all managed components
this evaluation will assume such secondary costs to be roughly equivalent between the two solutions and only focus on the areas where the primary cost factors differ
Virtual desktops in a VMware View implementation are maintained on a series of physical Desktop Servers.
Each Desktop Server requires a minimum of 48 GB in memory to host up to 142 virtual machine (VM) instances.
A VMware View Connection Server is also required for every 1000 VMs supported for brokering desktops and controlling user access.
Centralized virtual image management of the environment is performed by VMware View Composer software which can be installed on vCenter Servers that also provide storage management functionality.
These combined management platforms can support up to 1000 VMs each, but can be consolidated through server virtualization so that a single physical vCenter Server can support up to five such implementations.
Similarly, SQL servers necessary for hosting the vCenter and View Manager databases can also be consolidated through server virtualization at a ratio of 5:1
VMware recommends the SQL Server and vCenter Server be combined into a single system on implementations of less than 1000 VMs
With Citrix XenDesktop, 125 VMs can be supported on each XenServer with a minimum of 72GB of memory.
A cluster of Provisioning Servers, which is utilized for managing and delivering virtual images, can each reliably support 2000 VMs with one additional server added for fault tolerance (as recommended by Citrix).
Functionality for managing, maintaining and optimizing virtual desktop connections is provided by Desktop Delivery Controllers (DDCs).
For DDC’s, Citrix advises that a single physical server can provide the resources necessary to reliably support 10,000 VM
A XenDesktop infrastructure also commonly includes 2 Web Interfaces that allow users to access their published resources through a standard web browser
VMware, however, demonstrated roughly 60% greater efficiencies in memory utilization which contributed to the VMware View solution requiring 19% fewer servers than Citrix XenDesktop in order to host 10,000 users
2Storage Requirements
both VMware and Citrix utilize shared storage solutions for desktop images and software requirements.
For sizing purposes, an average of 3 images per desktop has been assumed, each with a size of 20 GB
VMware View Premier is able to significantly reduce storage requirements through the use of linked
clones, which is a process that allows a master replica to be created to which dependent VMs can be
linked so that only the differences from the master (the delta) need to be stored.
For Citrix XenDesktop, an average temporary storage requirement of 5 GB for each supported desktop has been calculated for this environment
This storage is used to accommodate the transient write caches associated with Provisioning Server virtual disks
Additionally, each provisioning server needs 20 GB for its application requirements and a fixed 100 GB needs to be collectively available to all
provisioning servers as a caching area for live images.
Desktop Delivery Controllers (DDCs). and Web Interfaces each require 5 GB for application installation
3Software Costs
VMware offers two editions of its View solution
The Enterprise Edition offers all software components necessary for full SHVD deployment,including high availability and dynamic provision capabilities
The Premier Edition also adds application virtualization and enables offline desktops
Citrix offers three versions of its XenDesktop solution
The standalone VDI Edition provides basic virtual desktop functionality and is sold with either a cost per individual user or concurrent user license model
More advanced virtualization management capabilities and application virtualization are added with the Enterprise Edition
the Platinum Edition offer the complete breadth of XenDesktop’s SHVD feature set, including advanced access control and server level monitoring
SHVD server memory utilization, density of VM per server, and level of concurrency.
All three of these factors are influenced by the operational conditions of the enterprise in which the implementation will be utilized
http://www.vmware.com/files/pdf/view/VMware-View-vs-Citrix-XenDesktop-EMA.pdf
- Comparing VDI solutions: VMware View and Citrix XenDesktop
XenDesktop is compatible with ESX, and that might be of interest to existing VMware shops
http://www.computerweekly.com/news/1391338/Comparing-VDI-solutions-VMware-View-and-Citrix-XenDesktop
- Desktop virtual infrastructure now includes new cloud-based options
Whereas on-premise data center-hosted VDI represented a known model that has been tested and refined over the years, cloud-based VDI is the new kid on the block
With many VDI solutions, the active desktop state can be preserved, enabling users to pick up right where they left off.
open-source solutions from StackVDI, QVD, and others.
*VDI delivery methods
Historically, solutions first began with the typical on-premise server-hosted virtual desktop model, focusing on the data center
As VDI and cloud computing have matured, a second software-as-a-service(SaaS) model of desktop computing has been reborn in the form as DaaS
In its simplest form, DaaS is VDI in the cloud
as with all cloud-based solutions, the customer must rely upon the cloud service provider (CSP) to deliver critical infrastructure that is no longer under the control of the IT organization
DaaS solutions are marketed as being able to handle the challenges of traditional VDI, such as complexity and cost.
In DaaS, customers pay a monthly flat fee and are able to obtain a VDI infrastructure without the initial investment.
The third option consists of a hybrid approach that leverages both the on-premise and cloud-based models
*AWS
AWS offers Amazon Workspaces as its VDI solution.
Workspaces represents a cloud-based managed desktop computing service, Amazon's DaaS model for VDI
Amazon WorkSpaces enables customers to choose from a range of Amazon WorkSpace bundles that provide options for CPU, memory, storage and applications.
In conjunction with AWS Directory Services,
Amazon WorkSpaces can integrate with a company's existing Active Directory infrastructure
Users also have the flexibility to install their own applications or use applications available through Amazon WorkSpaces
Amazon Workspaces supports desktop state persistence that provides a desktop anywhere model.
The WorkSpaces Sync client also enables users to synchronize documents between their Amazon WorkSpace and other computers.
Workspaces also provides support for USB devices, with the exception of printing.
Citrix
Citrix provides two options for customers seeking VDI: VDI-in-a-Box and XenDesktop.
http://www.networkcomputing.com/applications/guide-to-vdi-evaluating-top-vendors/d/d-id/1319116?page_number=1
- View planner is a workload simulator for VMware View environments that can be used to simulate a number of desktop workers, to verify the sizing of a given VMware View environment.
i.e. what is the impact of adding 512mb RAM to all your desktops, adding an additional vCPU or ramping up the number of desktops?
View Planner 2.0 is the natural successor to RAWC, meaning that RAWC is now EOL.
http://www.vpeeling.com/?p=252
- VMware Horizon View is a virtual desktop infrastructure (VDI) platform based on VMware vSphere virtualization
Step one: Research VMware View features
VMware ThinApp for application virtualization and vShield Endpoint for antivirus integration
Step three: VDI management
One of VDI's selling points is how it enables bring your own device (BYOD) within an organization
Employees purchase smartphones and tablets -- and apps that run on these devices
VMware offers security features in View 5 and newer versions that help admins deal with BYOD situations and other security considerations.
VMware updated View from version 5.1 to VMware Horizon View 5.2 in 2013,
http://searchvmware.techtarget.com/feature/VMware-View-best-practices-for-every-stage-of-VDI-implementation
- VMware View implementations architectures
- Citrix XenDestop implementations
- Smart client
Smart client is a term describing a computer application environment which
delivers applications over a web Hypertext Transfer Protocol (HTTP) connection
does not require installation (or provide automated installation and updates)
automatically updates without user action
has the look and feel of desktop applications
The term "smart client" was chosen to refer to simultaneously capturing the benefits of a "thin client" (zero-install, auto-update) and a "fat client" (high performance, high productivity).
https://en.wikipedia.org/wiki/Smart_client
- Smart Clients
http://www.chippc.com/products/smart-clients
- Evaluating Your Options for Desktop Virtualization (Part 1)
VDI, or Virtual Desktop Infrastructure, is a technology in which a server is used to host desktop operating systems. This technology is similar to what is used for server virtualization, except that there is usually a mechanism in place to link users to individual virtual desktops so that each user is connected to a different virtual desktop.
http://www.virtualizationadmin.com/articles-tutorials/vdi-articles/general/evaluating-options-desktop-virtualization-part1.html
- Microsoft Virtual Desktop Infrastructure (VDI) Explained
A centralized desktop delivery solution, Microsoft Virtual Desktop Infrastructure (VDI) is. The concept of VDI is to store and run desktop workloads including a Windows client operating system, applications, and data in a server-based virtual machine (VM) in a data center and allow a user to interact with the desktop presented onto a user device via Remote Desktop Protocol (RDP)
http://blogs.technet.com/b/yungchou/archive/2010/01/06/microsoft-virtual-desktop-infrastructure-vdi-explained.aspx
VDI vs RDS
VDI vs RDS
An Overview of Virtual Desktop Infrastructure (VDI)
This flexibility provides an isolated environment for the user. As each user enjoys a dedicated Virtual Machine with an operating system, they can install or uninstall applications with full or partial administration rights within the VM. A connection broker is used to manage these VMs. VDI is particularly useful when businesses have to deal with critical and confidential data. V
An Overview of Remote Desktop Service (RDS)
Remote Desktop Service (RDS), a proprietary protocol of Microsoft, allows users to connect remotely to a network with a graphic user interface.
While the RDS client is installed on the user system, the RDS server software is installed on the server, and a remote connection is established with one or more terminal servers.
While users in the RDS network connect to the server using a VM, this VM is shared with other users and operates on the same server operating system (OS) for all users.
VDI combines some of the best aspects of the PC and terminal services.
the fact that each user gets a separate VM creates complexity for the IT staff, wherein it has to manage multiple instances of the OS, updating and patching them
On the other hand, RDS sessions involve multiple users using the same VM and server OS
As there are not many windows instances involved, managing and updating the software is easy.
Moreover, less CPU and memory resources are utilized, which facilitates having more users per system
By deploying a cluster of terminal farms, organizations can provide a high availability of services
By deploying a cluster of terminal farms, organizations can provide a high availability of services.
Based on the number of remote users, VMs can be created and disposed of as well.
However, RDS services do not provide complete administrative rights as resources have to be shared between multiple users.
VDI is a part of RDS networks.
As both RDS and VDI uses Microsoft protocols, the performance levels are almost the same
Any third-party software configuration would make a difference
however, when it comes to user-centralized environment, RDS networks are cheaper and less complex in nature. As it involves the same management and mechanism, RDS gains a slight edge over VDI.
http://www.2x.com/vdi-vs-rds-cloud-requirements/
An Overview of Virtual Desktop Infrastructure (VDI)
This flexibility provides an isolated environment for the user. As each user enjoys a dedicated Virtual Machine with an operating system, they can install or uninstall applications with full or partial administration rights within the VM. A connection broker is used to manage these VMs. VDI is particularly useful when businesses have to deal with critical and confidential data. V
An Overview of Remote Desktop Service (RDS)
Remote Desktop Service (RDS), a proprietary protocol of Microsoft, allows users to connect remotely to a network with a graphic user interface.
While the RDS client is installed on the user system, the RDS server software is installed on the server, and a remote connection is established with one or more terminal servers.
While users in the RDS network connect to the server using a VM, this VM is shared with other users and operates on the same server operating system (OS) for all users.
VDI combines some of the best aspects of the PC and terminal services.
the fact that each user gets a separate VM creates complexity for the IT staff, wherein it has to manage multiple instances of the OS, updating and patching them
On the other hand, RDS sessions involve multiple users using the same VM and server OS
As there are not many windows instances involved, managing and updating the software is easy.
Moreover, less CPU and memory resources are utilized, which facilitates having more users per system
By deploying a cluster of terminal farms, organizations can provide a high availability of services
By deploying a cluster of terminal farms, organizations can provide a high availability of services.
Based on the number of remote users, VMs can be created and disposed of as well.
However, RDS services do not provide complete administrative rights as resources have to be shared between multiple users.
VDI is a part of RDS networks.
As both RDS and VDI uses Microsoft protocols, the performance levels are almost the same
Any third-party software configuration would make a difference
however, when it comes to user-centralized environment, RDS networks are cheaper and less complex in nature. As it involves the same management and mechanism, RDS gains a slight edge over VDI.
http://www.2x.com/vdi-vs-rds-cloud-requirements/
Workstation vs Desktop Computer
- Workstation vs Desktop Computer
2. Performance. A PC has enough power to do most tasks such as email, web surfing, and word processing. But a workstation has more power.
3. Durability. The internal workings of a workstation are held to a higher standard than those of a PC. Each part (motherboard, CPU, RAM, internal drives, video cards, etc.) is built with the understanding that it will be pushed hard all day long
Computers typically classified as a workstation have these five features:
1 ECC RAM. Error-correcting code memory makes your system more reliable
2 Multiple Processor Cores. More processor cores mean more processing abilities.
3 RAID (Redundant Array of Independent Disks).
4 SSD. Solid State Drives work differently than conventional hard-disk drives. There are no moving parts, so there is less chance of a physical failure
5 Optimized GPU. Having a higher end GPU (Graphics Processing Unit) means that your CPU will have to do less work processing the screen output
http://lineshapespace.com/pc-versus-workstation/
VDI hardware comparison: Thin vs. thick vs. zero clients
- VDI hardware comparison: Thin vs. thick vs. zero clients
Thin clients just do less processing than 'fat' clients.
When you deploy VDI, you need to figure out what hardware your virtual desktops will run on
To host virtual desktops, you have a lot of choices: thin clients, zero clients and smart clients -- not to mention tablets and mobile devices
Thin clients and other slimmed-down devices rely on a network connection to a central server for full computing and don't do much processing on the hardware itself.
Those differ from thick clients -- basically traditional PCs -- that handle all the functionality of a server on the desktop itself.
Thick clients
If you use traditional PCs to connect to virtual desktops, you don't get many of the benefits of VDI, such as reduced power consumption, central management and increased security.
It's possible to use thick clients for desktop virtualization, but many organizations don't because it doesn't cut down on overall hardware and requires all local software.
How thick clients compare to thin
Thick clients
a thick client is basically a PC running thin client software
a thick client usually more costly than a thin client device
thick clients have hard drives and media ports, making them less secure than thin clients.
thin clients tend to require less maintenance than thick ones
thin client hardware problems can sometimes lead to having to replace the entire device.
Thin clients
With thin client hardware, virtual desktops are hosted in the data center and the thin client simply serves as a terminal to the back-end server
Thin clients reduce hardware needs by allowing admins to repurpose old PCs.
What to look for in thin client devices
As you choose thin client devices, consider whether you need capabilities such as 3-D, video conferencing and multi-monitor support.
You should also take into account your remote display protocol and how much display processing your back end can supply.
thin clients should also offer centralized management.
you can automatically apply profile policies to groups of thin clients with similar configurations
Zero clients
These are client devices that require no configuration and have nothing stored on them.
zero clients can be less expensive than thick and thin clients.
they use less power and can simplify client device licensing.
Other VDI hardware
Using the iPad as a VDI client
Repurposing old PCs as VDI hardware
you might consider recycling old PCs to use as thin clients.
make sure your PC candidates aren't too old, or else they won't provide solid graphics performance and may be prone to failure.
http://searchvirtualdesktop.techtarget.com/feature/VDI-hardware-comparison-Thin-vs-thick-vs-zero-clients
- Choosing between ‘Thin vs Zero’ Clients for Virtual Desktop Computing
Thin Client devices for VDI are traditionally end-point devices with their own native operating systems, usually offering a version of Windows Embedded Standard (WES) or a Linux based operating system such as DeTOS
Thin clients utilize connection protocols such as Citrix ICA or Microsoft RDP in order to remotely access a desktop that is being hosted on a Virtual Machine stored on a server. They often include a local browser, as well
Zero clients often require less setup than a thin client.
zero clients are not as flexible and often require that the administrators choose one protocol or another for the device to utilize
While a user may only need to enter their credentials to access their desktop sessions, the options for what they can do is more limited.
Instead of an operating system, Zero Clients have a highly tuned onboard processor specifically designed for one possibly three VDI protocols (PCoIP, HDX, or RemoteFX).
Most of the decoding and display processes take place in dedicated hardware and therefore are more efficient than using a software client and a standard CPU and GPU setup as with a Thin Client
Zero Clients have boot up speeds of just a few seconds and are immune to viruses, decreasing the overall downtime of the device and increasing the productivity to the end-user
The Zero Client device requires very little maintenance and rarely needs an update unless there is a significant change/enhancement to the VDI protocol or the occasional BIOS related update.
Alternative Client Solutions
There are also thin clients such as the Acer Veriton N2010G, that offer a feature through the client operating system that enables fast, efficient deployments of new zero client terminals. Another option is choosing a thin client model that provides an OS ZeTOS allowing it to perform as a zero client terminal that runs in a stateless condition
Thin clients and other slimmed-down devices rely on a network connection to a central server for full computing and don’t do much processing on the hardware itself.
The first step on deciding between thin and zero clients really rests within the requirements of your network and the connection you prefer with your end uses.
http://www.devonit.com/blog/thin-vs-zero-thin-vs-zero-clients-virtual-desktop-computing
- Desktop virtualization clients: Fat, thin, or zero?
a full-blown PC with Windows installed is not a thin client in any sense of the word.
A thin client takes on many different forms but ultimately includes a CPU, RAM, and local storage and allows for the network connection
the zero-client solution.
This ultimate VDI solution pushes the computing back on the data center to the greatest degree possible and eliminates the need to support and maintain a desktop thin (or fat) client
The zero clienthas no operating system, no CPU, and no memory at the endpoint
the zero-client solution does require a ton of bandwidth, and those systems can only be used for VDI clients -- they cannot be repurposed later on
http://www.infoworld.com/article/2627997/vdi/desktop-virtualization-clients--fat--thin--or-zero-.html
- The Differences Between Thin and Zero VDI Clients
because they are fine tuned for a specific protocol, zero clients typically offer the end user a more robust video experience,
the decoding and display processes take place on dedicated hardware, zero clients boot up “wicked fast,” require minimal configuration, and tend to be more efficient and secure
zero clients, proprietary, which could put you at risk for vendor lock-in.
If a company plans on swapping out protocols or connection brokers, thin clients may prove to be the more flexible option in the end
If you need the ability to drag and drop a wide range of applications,would like to maintain a truer desktop experience, or you want to avoid vendor lock-in,thin clients may be the better way to go
if you need high-quality multimedia support, want to give your workers the flexibility to log into any terminal or other endpoint within your organization, or want to avoid any desktop-side configuration, consider zero clients solutions
http://www.storagecraft.com/blog/thin-clients-vs-zero-clients/
- Administrators have three options:
implement thin clients by purchasing dedicated machines or repurposing PCs
provide users with zero clients.
Thick clients
The PC continues to run its own operating system and usually requires no significant hardware or software upgrades.
The easiest way to implement a thick client is to install the VDI client and add a desktop shortcut that connects it to the virtual environment.
The user still has full access to the PCs native functionality with the added benefit of virtual desktop access.
Another approach is to lock down the PC's non-VDI components so the user can access only the remote desktop
With this method, the PC acts as a pseudo-thin client
For an organization full of usable PCs, thick clients are an attractive way to go because the company has already invested in the equipment and it's up and running.
the Windows OS running on that thick client means administrators have two environments to maintain for each user
Thick clients can't take full advantage of all VDI has to offer, such as streamlined management, improved security, reduced hardware maintenance and reduced energy consumption
thin client
thin clients are solid-state machines with the OS locked down and only minimal access permitted to non-VDI components
thin clients can run without an internal hard drive or external media ports, which prevents users from downloading sensitive data to their local devices.
No user data is stored locally, minimizing the damage that can be done if the device is compromised.
thin clients are designed for a single protocol which means an organization can become locked into one vendor, making it difficult to accommodate changing desktop needs.
Another approach to thin clients is repurposing existing PCs to act like thin clients.
IT can use a client conversion tool that strips out the old software, installs a lightweight OS and VDI client, and locks down the system like a thin client
Whichever type of thin client an organization chooses, it's important to note that these devices are still PC-like enough that they can support local applications and persistent storage.
Some thin clients even come with extra PCI slots or external media ports.
if a thin client goes down, administrators cannot simply swap out parts like they can a PC. They will instead have to replace the thin client altogether
zero client
The terminal serves no other purpose than to communicate with the VDI servers and render the virtual desktop
Unlike a thin client, a zero client does not run an OS
it is built with a specialized onboard processor specifically designed to handle a remote display protocol.
Because a zero client contains no hard drive, local storage or any other components that are not directly related to supporting VDI access, it is the most secure of the three options
Zero clients require little to no configuration, so they are quick to deploy, easy to set up, support centralized management, require few updates, and use less power than thick or thin clients.
They also offer users a better video experience because the device can be tuned for a specific VDI protocol.
http://searchvirtualdesktop.techtarget.com/tip/Comparing-three-options-for-VDI-endpoints
What is Thin Client Computing?
- What is Thin Client Computing?
They were similar to a thin client in that all processing was done from the CPU or computer they were connected to
Hosting information in the server data center and granting users’ access via what were called “dummy terminals”
A dumb terminal was simply an output device or display monitor that had no computational power to do anything besides display, send and receive text.
A thin client today is a compact piece of computing technology that accesses data remotely through a connection to a server and brings a virtual desktop to the user.
http://www.devonit.com/thin-client-education/what-is-thin-client-computing
- How Do Thin Clients Work?
Since it has no hard drive or local storage, all applications and data are stored on a central server,
Thin clients allow for local printing, audio and serial device support, web browsing, terminal emulation and can combine local processing with network computing.
A major part of a thin client solution is the thin client management console.
The management console,is a virtual appliance that can be installed on your Server to remotely manage all of the deployed thin clients.
It then can create, clone, and push out the customized image to the deployed thin client devices.
This allows IT administrators to freely access any device that is connected to the server, as well as pushing through certificates, software packages, as well as upload full disk images.
http://www.devonit.com/thin-client-education/how-do-thin-clients-work
- Benefits of Using Thin Clients
1.Cost Savings
1.1 Thin Clients Reduce Multiple Costs
IT support costs
Upfront purchasing costs
Capital costs
Use of space in data center
Licensing costs
Total administration and operating cost reduction up to 70%
1.2 Reduces Energy Bill by 97%
Thin clients consume an average of 8-20 watts compared to a 150 watt PC
This reduces carbon footprint
2.Simplified Management
2.1 The Benefits of Thin Client Management are
All software and hardware upgrades, security policies, application changes, etc. can be made in the data center
IT personnel are not required (as they are with PCs) to fix individual problems at the end user desktop location
Less downtime, increasing productivity amongst End Users and IT personnel
Centralized and simplified back up of desktops, laptops, and other client access devices
3.Enhanced Security
3.1 The Benefits of Thin Client Security Include
Thin clients are protected from the use of unauthorized software or the introduction of viruses
Data cannot be copied to a disk or saved to any other location than the server
Centralized processing makes it easy to manage and monitor the system
Simplify security, protect intellectual property, ensure data privacy
4.Increased Productivity
4.1 Systems can be Virtually Preconfigured, Packaged and Put into Operation in Minutes
Quickens setup and enables flexibility, without needing a specialist staff
Productivity can increase, while standard PCs have long repair times that cause delays and higher costs
Access the same apps and data from virtually anywhere
http://www.devonit.com/thin-client-education/benefits-of-using-thin-clients
- Green Computing with Thin Clients
Thin clients significantly lower a company’s environmental footprint by reducing energy consumption and CO2 emissions during use.
Cost savings from electricity can be reinvested.
Thin client computing also lowers operating and administration costs.
Because thin clients have a longer life span and are in built in a significantly smaller form factor, they last longer and can be recycled.
Thin Clients are RoHS compliant. They meet the regulation regarding the restriction of the use of certain hazardous substances in electrical and electronic equipment.
http://www.devonit.com/thin-client-education/green-computing
why VDI?
- why VDI?
http://www.locuz.com/vdi-byod.html
- Why VDI? (5 Reasons people really use VDI)
Datacenter-based desktops, without the hassle of RDSH
The primary purpose of VDI is that you get the benefits of hosting desktops in your datacenter without the hassle of Remote Desktop Session Host (RDSH) / Terminal Server.
VDI Pros and Cons
A Virtual Desktop Infrastructure (VDI) is designed to run desktop operating systems and applications inside virtual machines on servers in a data centre, and these are often referred to simply as virtual desktops
The virtual desktop is accessed via a desktop PC client or thin client via a remote display protocol, therefore many of the features previously loaded on local systems are still accessible but are centrally managed.
VDI Advantages / Pros
Typically, if a user experienced a PC problem previously, a member of IT staff must physically go to the PC to fix the problem. This can prove difficult if the user is at a remote site or is working out in the field. Either the IT technician must travel out to visit the user, or the PC must be sent back to the main office for repair. In either case, productivity suffers as the user no longer has a machine, or the technician is out of the office. With a VDI, most problems such as this can be dealt with remotely from within the data centre.
Desktop applications must be constantly updated, or patches and security updates frequently installed to protect systems.
On occasion, the operating system may be upgraded across the organisation
Technicians previously had to go to every PC in order to update, but a VDI enables this to be within the data centre and then rolled out across the company en masse
The VDI user is able to switch between operating environments, such as Windows 8 and Windows XP
VDI simplifies desktop management and administrative tasks as every attached workstation can use the same image.
A new user of the system can also be up and running quickly.
in the event of a single session failure for a user, a VDI allows the IT department to isolate that machine from others so that the problem does not spread.
VDI also allows the user to access business email and corporate documents from their own personal device, from anywhere.
Desktop security, backup and data protection are centralised, therefore the integrity of the applications and their data can be safeguarded at the data centre.
VDI disadvantages / cons
Implementation of a VDI requires a major investment in server hardware.
Storage and network infrastructure may also have additional cost implications, exceeding the expense of purchasing a basic PC for every individual user.
If that one server goes down, all users will be unable to work, whereas if a single PC goes down, only one user is affected
Although all workstations can use the same image, unique images are required for each of those users who needs a different set of applications or who needs the capability to save personal settings or install their own applications. This quickly multiplies the storage requirement on the VDI server.
when users download and install personal software, such as instant messaging. Difficulties can arise through the accidental downloading of malware applications. If this happens to a remote user, often the problem does not come to light for some time.
operational and support costs are lower, which can prove to be a more significant long-term saving than server hardware investment
http://hardpoint.eu/vdi-pros-and-cons
- Evaluating Your Options for Desktop Virtualization (Part 1)
VDI, or Virtual Desktop Infrastructure, is a technology in which a server is used to host desktop operating systems. This technology is similar to what is used for server virtualization, except that there is usually a mechanism in place to link users to individual virtual desktops so that each user is connected to a different virtual desktop.
http://www.virtualizationadmin.com/articles-tutorials/vdi-articles/general/evaluating-options-desktop-virtualization-part1.html
- Microsoft Virtual Desktop Infrastructure (VDI) Explained
A centralized desktop delivery solution, Microsoft Virtual Desktop Infrastructure (VDI) is. The concept of VDI is to store and run desktop workloads including a Windows client operating system, applications, and data in a server-based virtual machine (VM) in a data center and allow a user to interact with the desktop presented onto a user device via Remote Desktop Protocol (RDP)
http://blogs.technet.com/b/yungchou/archive/2010/01/06/microsoft-virtual-desktop-infrastructure-vdi-explained.aspx
Why BYOD
Why BYOD
Increased productivity and innovation
Personal devices tend to be more cutting-edge, so the enterprise benefits from the latest features. Also users upgrade to the latest hardware more frequently.
Employee satisfaction
Your people use the devices they have chosen and invested in—rather than what was selected by IT
Allowing employees to use personal devices also helps them avoid carrying multiple devices.
Cost savings
BYOD programs sometimes save budget by shifting costs to the user, with employees paying for mobile devices and data services
However, this often results in little to no savings
Consider before adopting BYOD
Personal cost
As mobile devices replace company-provided laptops, certain employees will expect the organization to pay for these new devices as well.
Enterprise cost
Will you have the resources to manage BYOD safely?
Are you willing to set up a private app store for maximum control?
Will your service desk be able to handle the inevitable flood of support calls?
Enterprise control
Certain job functions require access to very sensitive data,IT needs complete control over the mobile devices and applications installed on them
http://www.ibm.com/mobilefirst/us/en/bring-your-own-device/byod.html
Desktop virtualization makes it possible for IT to deliver desktops and apps straight from the data center to any device, making device management radically simpler
Thin client laptops offer security for those mobile users
Rather than the desktop being stored locally on a remote client, a virtualized version of the desktop is stored on a remote central server, allowing users to run an operating system and applications from a thin client laptop or a standard desktop thin client; streamlining a desktop virtualization platform
Desktop virtualization(VDI) addresses two key challenges– security and device management.
By enabling IT to centrally manage and secure desktops, applications, and data in the data center, business information is always secure
Even when data is stored on the end point device, IT has the ability to remotely erase data in the event the device is lost or stolen.
http://www.devonit.com/blog/thin-client-laptops-help-align-desktop-virtualization-with-byod
Increased productivity and innovation
Personal devices tend to be more cutting-edge, so the enterprise benefits from the latest features. Also users upgrade to the latest hardware more frequently.
Employee satisfaction
Your people use the devices they have chosen and invested in—rather than what was selected by IT
Allowing employees to use personal devices also helps them avoid carrying multiple devices.
Cost savings
BYOD programs sometimes save budget by shifting costs to the user, with employees paying for mobile devices and data services
However, this often results in little to no savings
Consider before adopting BYOD
Personal cost
As mobile devices replace company-provided laptops, certain employees will expect the organization to pay for these new devices as well.
Enterprise cost
Will you have the resources to manage BYOD safely?
Are you willing to set up a private app store for maximum control?
Will your service desk be able to handle the inevitable flood of support calls?
Enterprise control
Certain job functions require access to very sensitive data,IT needs complete control over the mobile devices and applications installed on them
http://www.ibm.com/mobilefirst/us/en/bring-your-own-device/byod.html
- employees are demanding access to corporate networks, applications, and information anywhere at any time with any device and managing this isn’t always easy
Desktop virtualization makes it possible for IT to deliver desktops and apps straight from the data center to any device, making device management radically simpler
Thin client laptops offer security for those mobile users
Rather than the desktop being stored locally on a remote client, a virtualized version of the desktop is stored on a remote central server, allowing users to run an operating system and applications from a thin client laptop or a standard desktop thin client; streamlining a desktop virtualization platform
Desktop virtualization(VDI) addresses two key challenges– security and device management.
By enabling IT to centrally manage and secure desktops, applications, and data in the data center, business information is always secure
Even when data is stored on the end point device, IT has the ability to remotely erase data in the event the device is lost or stolen.
http://www.devonit.com/blog/thin-client-laptops-help-align-desktop-virtualization-with-byod
VDI (Virtual Desktop Integration) implementation
VDI(Virtual Desktop Integration) implementation
gathering requirements
identifying stakeholders
establishing milestones
determining goals for success
conducting research
selecting vendors
planning test/production rollouts
gathering feedback
going live
closing the loop on any residual issues
1. Not planning enough resources
Your virtual machines (and users) are going to be extremely hungry for CPU cycles, memory, storage, and network bandwidth
Don't provision the resources you need today or tomorrow – build out the infrastructure for next year or, better yet, three years from now
Monitor how the resources are being used before, during and after the VDI rollout.
make sure you're inherently familiar with your network traffic, subnets, and the hosts/applications running across these
2. Not taking advantage of existing resources
Some vendors might (happily) convince you that you have to run out and buy all new hardware for your data center, not to mention a fleet of shiny thin clients for your users
Don't scrap older desktops in favor of thin client hardware
Let them wear out then replace them
Don't assume a Windows virtual desktop has to be connected to from a computer or thin client – tablets and mobile devices can also be used (depending on your network and remote access capabilities) which is where your BYOD program can really come in handy.
http://www.techrepublic.com/blog/10-things/10-vdi-mistakes-to-avoid/
VDI requires upfront costs, so by the time IT gets to the desktop side; further upfront costs need to be minimized.
Keeping existing PCs appears to be “cheaper” then switching to thin clients for VDI
A PC also known as a thick client, is comprised of a lot of components compared to a thin client.
With each PC you have (at minimum) a hard drive, media ports, OS, applications and anti-virus software.
PCs typically have a 4 year expected life where thin clients have a 6 year expected life
The media ports and hard drive open up the possibilities for a security breach
At the same time the user then can install their software which also increases security risks.
PCs are typically un-managed desktop devices limiting the security capabilities for the desktop user.
Then a thin client only has the thin client OS and a small about of applications if required.
Thin clients are locked down devices eliminated the users’ ability to download unless permitted and all devices can be managed through a thin client management console
Thin Clients are cheaper then PCs
With thin clients, the cost per unit really depends on the unit each user requires. Someone whose daily tasks entail the use of simple applications such as outlook
Exploring the Cost per User for VDI
In most VDI deployments, organizations transition from PCs to thin clients over time.
While every organization is different, we have typically seen around 1/3 of VDI users move to thin client devices and the other 2/3s utilize software options such as VDI Blaster.
This software converts PCs that are towards the end of their life spans to make them (functionally) into thin clients.
Microsoft licensing, customers only need to purchase VDA licenses for the percentage of their devices that are thin clients or not covered under Microsoft SA licensing as they start replacing their PCs over time.
1-Hardware Cost
1.1 Thin Client Software for Physical PCs
1.2 Thin Clients
1.3 Average Cost Per User of Thin Client Device or Software
2 Licensing Costs
2.1 VDI Software
2.2 Microsoft VDA License
1 Overall VDI Initial Cost per User Comparison
1.1 Thin Client
1.1.1 VDI COMPONENT
Server
Storage
Thin Client/Repurposed PC
VDI Software
Microsoft License
1.2 PC
1.1.1 VDI COMPONENT
Server
Storage
Thin Client/Repurposed PC
VDI Software
Microsoft License
http://www.devonit.com/blog/vdi-at-the-desktop
1.Evaluation
1.1 Capital Savings
1.2 Operation Savings
1.3 End –User Operation Savings
1.4 Downtime Savings
1.5 Energy Savings
1.6 Desktop Related Cost Savings for 1, 2, 3, 5, and 10 Years!
http://www.devonit.com/thin-client-education/switching-to-thin-clients
Deploying virtual desktops lets you create a more flexible IT infrastructure so your business becomes more efficient, effective, secure, and manageable.
This method deploys applications and desktops faster and more consistently to a wider variety of users at a lower cost while improving service levels.
Other than the initial start up cost, particularly the costs incurred by obtaining servers, the price drastically lowers deployment costs when compared to a PC environment
Thin clients alone can last between 7-10 years as compared to their PC counterparts.
saving nearly $1000 per seat in the long run in maintenance costs
fewer moving parts result in fewer broken units.
thin clients use anywhere from 3-13 watts of power, which is a considerable energy savings compared to PCs that range anywhere from 60 to 150 watts
desktop virtualization(VDI) can increase the security of your business in two ways
Firstly, all data is stored on the server end, so devices themselves have no information physically on them
As laptop thefts are a big source of leaked information, this is an outstanding security benefit
the nature of thin clients makes them very resistant to viruses. Since nothing on the device is persistent, a simple reboot is all that’s needed to remove any malicious software that may find its way to a user’s terminal.
Desktop Virtualization can significantly decrease maintenance and support costs
Adding new terminals is a simple process
Reduced downtime with server or client hardware failures
Decreased cost of new application deployment
Desktop image management capabilities
Longer refresh cycle for client desktop infrastructure
Secure remote access to the enterprise desktop environment
Reduce costs by increasing energy efficiency and requiring less hardware with server consolidation.
Build up business continuity through improved disaster recovery solutions and deliver high availability
http://www.devonit.com/blog/advantages-in-converting-to-desktop-virtualization
1 Choose the right virtualization approach
1.1 VDI vs Remote Access Terminal Services
1.2 the entire desktop environment on a server as virtual machine
1.3 Remote Access Terminal Services- host applications on a central server and present those applications to those users
2 Assess the network before the development
2.1 verify adequate bandwidth
2.2 enough bandwidth to support the peak load of each virtual desktop user
3 Evaluate thin client terminal management software systems
3.1 test run different thin client management software to determine best interface
4 develop a desktop virtualization server strategy
4.1 cpu,memory,I/O resources to support the peak processing demands of users.
5 Upgrade storage to support desktop virtualization
5.1 data center SAN needs enough additional storage to host all virtual desktops
6 Choose best thin client for each end user
6.1 end users may need different hw requirements
6.2 evaluate applications used in different roles
7 deploy desktop virtualization in phases
7.1 pilot rollouts
7.2 management buy-in
8 be aggressive with endpoint security
9 take strong central security measures
9.1 address access control
9.2 ensure that each user is configured with least-privillege roles and policies
10 devise an implementation plan
10.1 xx amount of thin clients per year over xx amount of years
10.2 depending on corporation size this could be weeks months years
11 implement and test backup services
11.1 backup servers with great regularity to ensure successful disaster recovery(DR)
11.1 backup data frequently / consistently
Virtual desktops are critical to accelerate application deployment and simplify application migration
VDI lets you decouple operating system,application and data from hardware and store them in a centralized location
http://www.devonit.com/blog/11-steps-to-roll-out-a-virtual-desktop-infrastructure
http://www.devonit.com/wp-content/uploads/2014/02/Thin-Client-TCO-Calulator-Sample-Report-Calculator-I.jpg
Improper Design: VDI consists of three key components – Server, Storage and Network. VDI design should be done keeping in mind the maximum scalable limit and minimal downtime of these three components.
Assessing customer’s core applications, operating environment, user profiles and user experience is the key of planning for any VDI rollout.
Step 1: Assess
Defined metrics should be used to capture information on utilization of CPU, memory, network, storage and other compute resources.
Step 2: Plan
The Planning phase is critical as it requires developing high level design documents including specifications of VDI components such as hardware, hypervisor, connection broker, gateway etc
Step 3: Design
if the user requires a USB device to be plugged into the client device, the device and operating system must support USB redirection or if the user requires a multimedia application the client device must support a protocol that can provide adequate user experience
Step 6: User Migration
Migrations Plans must be strategized for seamless user data migrations and profile migrations from existing physical desktops to virtual desktops using thirty party tools or manual methods.
http://www.microland.com/best-practices-for-a-highly-effective-vdi-environment
you'll want to identify the organizational costs associated with physical desktop management so that you can justify the migration to a virtual desktop infrastructure.
Step 2: Understand the existing infrastructure
determine the percentage of your server environment that is virtualized and the hypervisor vendor mix along with the distribution.
Look at the current state of network access for remote users, as well as the current state of security architecture for these users.
determine if you should utilize new storage for your desktop infrastructure, or if you can leverage the existing infrastructure. Think about evaluating protocol options such as Fibre Channel, iSCSI or NAS, and consider which performance and monitoring tools are going to be used to evaluate storage and performance.
Step 3: Determine the desktop user environment
what percentage of users are local versus remote?
Break out the percentage of non-employee users (contractors, partners) that also have to be included in the planning.
determine the end-user experience requirements. Consider important details such as user profile persistence, single vs. multiple desktop needs, granular USB redirection, printing requirements, audio profile (one-way or two-way), and monitor support.
conduct an application virtualization assessment to analyze and capture important metrics such as executable size, device drivers installed per application, total number of application users and average load time.
Application virtualization is critical to accelerating application deployment and simplifying application migration. By decoupling applications and settings from the OS, you can manage any endpoint as a generic device, making complex OS upgrades a non-event.
Step 4: Assess the physical desktop environment
Analyze the current desktop environmental metrics, including network, CPU, storage and memory statistics. Also assess the user personality and profile location, including for mobile users, off-line needs and stationary task workers
Prioritize users based on complexity factors derived from the assessment. Determine sizing factors within the virtual infrastructure based on the assessment. This should include peaks in utilization, storage implications for monolithic 1:1 mapping of images versus a linked clone approach for deployment and performance evaluations from desktop to storage.
Step 5: Mapping the solution options
Look at your remote protocol choices and their impact across network, security and performance.
Step 6: The pilot implementation
Create a framework for pilot implementation on a subset of users. Define various test metrics and scenarios as well as success criteria for the pilot. In order to conduct a successful proof-of-concept or technology bake-off, the three following things need to be clearly understood about your environment and requirements:
--What does success look like for your organization? Setting up measurable, deterministic success criteria for your specific data center environment is imperative.
--Have you benchmarked the current end-user experience in the physical realm? If end-user experience suffers in the virtualized environment, the whole project is likely to collapse.
--Have you ensured that all of the interlocking products that comprise the overall proof-of-concept environment are configured correctly, optimally and in a supportive fashion? If they are not, your results will be meaningless.
Based on the findings, develop a plan and design a VDI framework that includes best practices, deployment reference architectures, milestones and project management resources
Step 7: Implement and manage VDI
At this stage, you are finally ready to implement VDI. Determine project management resources, schedule a rollout date, develop project timelines and select the ideal resources to meet the business and IT needs. Part of the process will be to create a feedback loop for continual process improvement. You will also want to capture performance metrics so optimal performance is achieved.
http://www.infostor.com/index/articles/display/3463093630/articles/infostor/storage-management/virtualization/2010/august-2010/seven-steps_for_a.html
Virtual desktop infrastructure is heavily dependent on the network, so it's important to be familiar with the well-known display protocol vendors and the newcomers.
VDI-in-a-Box offers a quick deployment process with better pricing than XenDesktop. It's up to you whether to go with the age-old XenDesktop or VDI-in-a-Box, which is more for small and medium-sized businesses (SMBs).
http://searchvirtualdesktop.techtarget.com/guides/VDI-pilot-project-guide-How-to-ensure-VDI-implementation-success
gathering requirements
identifying stakeholders
establishing milestones
determining goals for success
conducting research
selecting vendors
planning test/production rollouts
gathering feedback
going live
closing the loop on any residual issues
1. Not planning enough resources
Your virtual machines (and users) are going to be extremely hungry for CPU cycles, memory, storage, and network bandwidth
Don't provision the resources you need today or tomorrow – build out the infrastructure for next year or, better yet, three years from now
Monitor how the resources are being used before, during and after the VDI rollout.
make sure you're inherently familiar with your network traffic, subnets, and the hosts/applications running across these
2. Not taking advantage of existing resources
Some vendors might (happily) convince you that you have to run out and buy all new hardware for your data center, not to mention a fleet of shiny thin clients for your users
Don't scrap older desktops in favor of thin client hardware
Let them wear out then replace them
Don't assume a Windows virtual desktop has to be connected to from a computer or thin client – tablets and mobile devices can also be used (depending on your network and remote access capabilities) which is where your BYOD program can really come in handy.
http://www.techrepublic.com/blog/10-things/10-vdi-mistakes-to-avoid/
- VDI at the Desktop: Thin Clients or PCs for Better TCO?
VDI requires upfront costs, so by the time IT gets to the desktop side; further upfront costs need to be minimized.
Keeping existing PCs appears to be “cheaper” then switching to thin clients for VDI
A PC also known as a thick client, is comprised of a lot of components compared to a thin client.
With each PC you have (at minimum) a hard drive, media ports, OS, applications and anti-virus software.
PCs typically have a 4 year expected life where thin clients have a 6 year expected life
The media ports and hard drive open up the possibilities for a security breach
At the same time the user then can install their software which also increases security risks.
PCs are typically un-managed desktop devices limiting the security capabilities for the desktop user.
Then a thin client only has the thin client OS and a small about of applications if required.
Thin clients are locked down devices eliminated the users’ ability to download unless permitted and all devices can be managed through a thin client management console
Thin Clients are cheaper then PCs
With thin clients, the cost per unit really depends on the unit each user requires. Someone whose daily tasks entail the use of simple applications such as outlook
Exploring the Cost per User for VDI
In most VDI deployments, organizations transition from PCs to thin clients over time.
While every organization is different, we have typically seen around 1/3 of VDI users move to thin client devices and the other 2/3s utilize software options such as VDI Blaster.
This software converts PCs that are towards the end of their life spans to make them (functionally) into thin clients.
Microsoft licensing, customers only need to purchase VDA licenses for the percentage of their devices that are thin clients or not covered under Microsoft SA licensing as they start replacing their PCs over time.
1-Hardware Cost
1.1 Thin Client Software for Physical PCs
1.2 Thin Clients
1.3 Average Cost Per User of Thin Client Device or Software
2 Licensing Costs
2.1 VDI Software
2.2 Microsoft VDA License
1 Overall VDI Initial Cost per User Comparison
1.1 Thin Client
1.1.1 VDI COMPONENT
Server
Storage
Thin Client/Repurposed PC
VDI Software
Microsoft License
1.2 PC
1.1.1 VDI COMPONENT
Server
Storage
Thin Client/Repurposed PC
VDI Software
Microsoft License
http://www.devonit.com/blog/vdi-at-the-desktop
- Thin Client Assessment with Total Cost of Ownership(TCO) Analysis
1.Evaluation
1.1 Capital Savings
1.2 Operation Savings
1.3 End –User Operation Savings
1.4 Downtime Savings
1.5 Energy Savings
1.6 Desktop Related Cost Savings for 1, 2, 3, 5, and 10 Years!
http://www.devonit.com/thin-client-education/switching-to-thin-clients
- Advantages in Converting to Desktop Virtualization
Deploying virtual desktops lets you create a more flexible IT infrastructure so your business becomes more efficient, effective, secure, and manageable.
This method deploys applications and desktops faster and more consistently to a wider variety of users at a lower cost while improving service levels.
Other than the initial start up cost, particularly the costs incurred by obtaining servers, the price drastically lowers deployment costs when compared to a PC environment
Thin clients alone can last between 7-10 years as compared to their PC counterparts.
saving nearly $1000 per seat in the long run in maintenance costs
fewer moving parts result in fewer broken units.
thin clients use anywhere from 3-13 watts of power, which is a considerable energy savings compared to PCs that range anywhere from 60 to 150 watts
desktop virtualization(VDI) can increase the security of your business in two ways
Firstly, all data is stored on the server end, so devices themselves have no information physically on them
As laptop thefts are a big source of leaked information, this is an outstanding security benefit
the nature of thin clients makes them very resistant to viruses. Since nothing on the device is persistent, a simple reboot is all that’s needed to remove any malicious software that may find its way to a user’s terminal.
Desktop Virtualization can significantly decrease maintenance and support costs
Adding new terminals is a simple process
Reduced downtime with server or client hardware failures
Decreased cost of new application deployment
Desktop image management capabilities
Longer refresh cycle for client desktop infrastructure
Secure remote access to the enterprise desktop environment
Reduce costs by increasing energy efficiency and requiring less hardware with server consolidation.
Build up business continuity through improved disaster recovery solutions and deliver high availability
http://www.devonit.com/blog/advantages-in-converting-to-desktop-virtualization
- 11 Steps to Roll-Out a Virtual Desktop Infrastructure
1 Choose the right virtualization approach
1.1 VDI vs Remote Access Terminal Services
1.2 the entire desktop environment on a server as virtual machine
1.3 Remote Access Terminal Services- host applications on a central server and present those applications to those users
2 Assess the network before the development
2.1 verify adequate bandwidth
2.2 enough bandwidth to support the peak load of each virtual desktop user
3 Evaluate thin client terminal management software systems
3.1 test run different thin client management software to determine best interface
4 develop a desktop virtualization server strategy
4.1 cpu,memory,I/O resources to support the peak processing demands of users.
5 Upgrade storage to support desktop virtualization
5.1 data center SAN needs enough additional storage to host all virtual desktops
6 Choose best thin client for each end user
6.1 end users may need different hw requirements
6.2 evaluate applications used in different roles
7 deploy desktop virtualization in phases
7.1 pilot rollouts
7.2 management buy-in
8 be aggressive with endpoint security
9 take strong central security measures
9.1 address access control
9.2 ensure that each user is configured with least-privillege roles and policies
10 devise an implementation plan
10.1 xx amount of thin clients per year over xx amount of years
10.2 depending on corporation size this could be weeks months years
11 implement and test backup services
11.1 backup servers with great regularity to ensure successful disaster recovery(DR)
11.1 backup data frequently / consistently
Virtual desktops are critical to accelerate application deployment and simplify application migration
VDI lets you decouple operating system,application and data from hardware and store them in a centralized location
http://www.devonit.com/blog/11-steps-to-roll-out-a-virtual-desktop-infrastructure
- Sample VDI Assessment & TCO Calculation
- No consideration to Application Virtualization:
Improper Design: VDI consists of three key components – Server, Storage and Network. VDI design should be done keeping in mind the maximum scalable limit and minimal downtime of these three components.
Assessing customer’s core applications, operating environment, user profiles and user experience is the key of planning for any VDI rollout.
Step 1: Assess
Defined metrics should be used to capture information on utilization of CPU, memory, network, storage and other compute resources.
Step 2: Plan
The Planning phase is critical as it requires developing high level design documents including specifications of VDI components such as hardware, hypervisor, connection broker, gateway etc
Step 3: Design
if the user requires a USB device to be plugged into the client device, the device and operating system must support USB redirection or if the user requires a multimedia application the client device must support a protocol that can provide adequate user experience
Step 6: User Migration
Migrations Plans must be strategized for seamless user data migrations and profile migrations from existing physical desktops to virtual desktops using thirty party tools or manual methods.
http://www.microland.com/best-practices-for-a-highly-effective-vdi-environment
- Step 1: Develop the business case
you'll want to identify the organizational costs associated with physical desktop management so that you can justify the migration to a virtual desktop infrastructure.
Step 2: Understand the existing infrastructure
determine the percentage of your server environment that is virtualized and the hypervisor vendor mix along with the distribution.
Look at the current state of network access for remote users, as well as the current state of security architecture for these users.
determine if you should utilize new storage for your desktop infrastructure, or if you can leverage the existing infrastructure. Think about evaluating protocol options such as Fibre Channel, iSCSI or NAS, and consider which performance and monitoring tools are going to be used to evaluate storage and performance.
Step 3: Determine the desktop user environment
what percentage of users are local versus remote?
Break out the percentage of non-employee users (contractors, partners) that also have to be included in the planning.
determine the end-user experience requirements. Consider important details such as user profile persistence, single vs. multiple desktop needs, granular USB redirection, printing requirements, audio profile (one-way or two-way), and monitor support.
conduct an application virtualization assessment to analyze and capture important metrics such as executable size, device drivers installed per application, total number of application users and average load time.
Application virtualization is critical to accelerating application deployment and simplifying application migration. By decoupling applications and settings from the OS, you can manage any endpoint as a generic device, making complex OS upgrades a non-event.
Step 4: Assess the physical desktop environment
Analyze the current desktop environmental metrics, including network, CPU, storage and memory statistics. Also assess the user personality and profile location, including for mobile users, off-line needs and stationary task workers
Prioritize users based on complexity factors derived from the assessment. Determine sizing factors within the virtual infrastructure based on the assessment. This should include peaks in utilization, storage implications for monolithic 1:1 mapping of images versus a linked clone approach for deployment and performance evaluations from desktop to storage.
Step 5: Mapping the solution options
Look at your remote protocol choices and their impact across network, security and performance.
Step 6: The pilot implementation
Create a framework for pilot implementation on a subset of users. Define various test metrics and scenarios as well as success criteria for the pilot. In order to conduct a successful proof-of-concept or technology bake-off, the three following things need to be clearly understood about your environment and requirements:
--What does success look like for your organization? Setting up measurable, deterministic success criteria for your specific data center environment is imperative.
--Have you benchmarked the current end-user experience in the physical realm? If end-user experience suffers in the virtualized environment, the whole project is likely to collapse.
--Have you ensured that all of the interlocking products that comprise the overall proof-of-concept environment are configured correctly, optimally and in a supportive fashion? If they are not, your results will be meaningless.
Based on the findings, develop a plan and design a VDI framework that includes best practices, deployment reference architectures, milestones and project management resources
Step 7: Implement and manage VDI
At this stage, you are finally ready to implement VDI. Determine project management resources, schedule a rollout date, develop project timelines and select the ideal resources to meet the business and IT needs. Part of the process will be to create a feedback loop for continual process improvement. You will also want to capture performance metrics so optimal performance is achieved.
http://www.infostor.com/index/articles/display/3463093630/articles/infostor/storage-management/virtualization/2010/august-2010/seven-steps_for_a.html
- VDI project plan, part one: Understanding product options
Virtual desktop infrastructure is heavily dependent on the network, so it's important to be familiar with the well-known display protocol vendors and the newcomers.
VDI-in-a-Box offers a quick deployment process with better pricing than XenDesktop. It's up to you whether to go with the age-old XenDesktop or VDI-in-a-Box, which is more for small and medium-sized businesses (SMBs).
http://searchvirtualdesktop.techtarget.com/guides/VDI-pilot-project-guide-How-to-ensure-VDI-implementation-success