Essential Guide

Browse Sections


This content is part of the Essential Guide: How to set up VDI: Tips and considerations
Evaluate Weigh the pros and cons of technologies, products and projects you are considering.

How the move to Windows 10 could lead IT to deploy VDI

When IT moves users to Windows 10, it should take the time to also look at the potential of VDI, a technology that has grown a lot in recent years and become more affordable.

Before IT professionals make the move to Windows 10, they have a lot to think about, including ensuring application and hardware compatibility and figuring out how to approach the OS's automatic updates. They should also think about using the transition period as an opportunity to deploy VDI.

VDI has been left behind by many organizations that were burned by the technology early on. These are the organizations that, instead of testing the waters, jumped in headfirst only to find that users didn't accept VDI because of performance issues, a lack of functionality or just plain instability. For other organizations, a plan to deploy VDI was never even on the radar.

As organizations transition to Windows 10, however, IT pros should understand that modern VDI is not the same beast it was when the technology first came about. As a result, it's time for organizations to reopen their eyes to VDI and see how far it has come.

What has changed?

First and foremost, the cost to deploy VDI is lower than ever before. From a Capex perspective, VDI has always been a hard sell. However, hardware costs have plummeted and, coupled with a major boost in performance in many areas, including compute -- CPU and memory -- networking and storage, VDI is more practical and affordable than ever.

Enhancements in hardware, from faster CPU and memory to the rise of 10 GbE networks in the data center, have all helped make VDI more realistic for organizations. Hyper-converged infrastructures from vendors such as Nutanix have also changed the game. Solid-state drives and VSAN have replaced the venerable hybrid hard drive as the go-to storage device for network-attached storage.

Just because IT can deploy VDI does not always mean that it should.

In addition, the price for graphics processing units (GPUs), such as Nvidia Grid, has dropped, so IT can deliver a boost to graphics performance, which makes it easier to deliver more applications from a centralized location. It also helps ensure graphics-intensive apps, such as computer-aided design tools, work well with VDI. Improvements in application delivery and layering have dramatically eased the ability to produce desktops that can meet users' performance needs.

User environment management tools that are easier to work with have also enabled VDI shops to deliver nonpersistent desktops with a persistent experience more easily than ever. As a result, users can customize their desktops as they see fit, but IT can still deliver a fresh, fully patched, clean desktop on a day-to-day basis without the demanding storage needs of persistent desktops.

Ultimately, the move to Windows 10 is a good excuse to take a look around at what other technology is out there that could make life easier for IT rather than a true driving force for organizations to deploy VDI. IT should re-evaluate its entire deployment and make a decision based on sound business requirements and needs. Just because IT can deploy VDI does not always mean that it should.

Dig Deeper on Virtual desktop strategies and architecture

Join the conversation


Send me notifications when other members comment.

Please create a username to comment.

Is an OS migration a good time to make other major changes, such as adopting VDI?
Here is what I would recommend
 Step 1 - Take all the Win32 apps and put them in layering and XenApp so you get away from updating them in the VDI/Native PCs. The pace at which these Windows 10 OS are getting updated, you can't keep up with the updates of the OS
Step 2 - Convert as many Desktops or PCs to VDI instances as possible. You are trying to centralize as much as possible to simplify the patch cycle. 
Step 3 -  All other PCs needs to be managed via UEM solution and only apps which support modern style management and updates should be pushed to these end points. These end points should avoid any win32 apps. 
Step 4 Separate out content from the end points and put data into EFSS/BFSS solutions so your windows updates are again easier and It is easy to access data anywhere. 
<disclosure> I work for Citrix but these are my opinions </disclosure>