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 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
http://www.devonit.com/wp-content/uploads/2014/02/Thin-Client-TCO-Calulator-Sample-Report-Calculator-I.jpg
- No consideration to Application Virtualization:
Enterprises typically have to face issues such as installing every application into a standard desktop image, creating multiple images based on different user groups etc., therefore an assessment to analyze important details like total number of application users, average load time etc. needs to be captured. Application Virtualization also enables you to manage any endpoint as a generic device, making complex OS upgrades much easier.
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
Start by providing stakeholders with the documentation necessary to support your project. This information should include understanding the current mechanisms and challenges around physical desktop management, including refresh durations and complexity, Windows 7 deployment, OS and application patching and maintenance procedures, offshore and non-employee access, and finally, regulatory compliance, which is especially necessary in protecting sensitive information.
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
