After sitting through a virtualization sales pitch focused around Virtual Desktop Infrastructures (VDI) this afternoon I had several thoughts on the topic I thought may be blog worthy.
VDI has been a constant buzzword for a few years now, riding the coattails of server virtualization.Â For the majority of those years you can search back and find predictions from the likes of Gartner touting â€˜This is the year for VDIâ€™ or making other similar statements, typically with projected growth rates that donâ€™t ever happen.Â What you wonâ€™t see is those same analyst organizations reaching back the year after and answering to why they over hyped it, or were blatantly incorrect. (Great idea for a yearly blog here, analyzing previous years failed predictions.)
The reasons theyâ€™ve been incorrect vary over the years starting with technical inadequacy of the infrastructures and lack of real understanding as an industry.Â When VDI first hit the forefront many of us (myself included) made the assumption desktops could be virtualized the same as servers (Windows is Windows right?)Â What we neglected to account for is the plethora of varying user applications, the difficulty of video and voice, and other factors such as boot storms which are unique and or more amplified within VDI environments than their server counterparts.Â From there for a short while the VDI rollout horror stories and memories of failed Proof of Concepts slowed adoption and interest for a short period.
Now weâ€™re at a point where the technology can overcome the challenges and the experts are battle hardened with knowledge of success and failures in various environments; yet still adoption is slow.Â Users are bringing new devices into the workplace and expecting them to interface with enterprise services; yet still adoption is slow.Â We supposedly have a more demanding influx of younger generation employees who demand remote access from their chosen devices; yet still adoption is slow.Â This doesnâ€™t mean that VDI isnâ€™t being adopted, nor that the market share numbers arenâ€™t increasing across the board; itâ€™s just slow.
The reason for this is that our thinking and capabilities for service delivery have surpassed the need for VDI in many environments. VDI wasnâ€™t an end-goal but instead an improvement over individually managed, monitored, and secured local end-user OS environments.Â The end-goal isnâ€™t removing the OS tie to the hardware on the end-point (which is what VDI does) but instead removing the applications tie to the OS; or more simply put: removing any local requirements for access to the services.Â Starting to sound like cloud?
Cloud is the reason enterprise IT hasnâ€™t been diving into VDI head first, the movement to cloud services has shown that for many we may have passed the point where VDI could show true Return On Investment (ROI) before being obsoleted.Â Cloud is about delivering the service to any web connected end-point on-demand regardless of platform (OS.)Â If you can push the service to my iOS, Android, Windows, Linux, etc. device without the requirement for a particular OS, then whatâ€™s the need for VDI?
To use a real world example I am a Microsoft zealot, I use Windows 7, Bing for search and only IE for browsing on my work and personal computers (call me retro.)Â I also own an iPad, mainly due to the novelty and the fact that I got addicted to â€˜Flight Controlâ€™ on a friends iPad at release of the original.Â I occasionally use the iPad for what Iâ€™d call â€˜productivity workâ€™ related to my primary role or side projects.Â Using my iPad I do things like: Access corporate email for the company I work for and my own, review files, access Salesforce, and Salesforce Chatter, and even perform some remote equipment demos, my files are seamlessly synched between my various other computers.Â I do all of this without a Windows 7 virtual desktop running on my iPad, itâ€™s all done through apps connected to these services directly.Â In fact the only reason I have VDI client applications on my iPad is to demo VDI, not to actually work.
Now an iPad is not a perfect example, Iâ€™d never use it for developing content (slides, reports, spreadsheets, etc.) but I do use it for consuming content, email, etc.Â To develop I turn to a laptop with full keyboard, screen and some monitor outputs.Â This laptop may be a case for VDI but in reality why?Â If the services I use are cloud based, public or private, and the data I utilize is as well, then the OS is irrelevant again.Â With office applications moving to the cloud (Microsoft Office 365, Google Docs, etc.) along with many others, and many services and applications already there, what is the need for a VDI infrastructure?
VDI like server virtualization is really a band-aid for an outdated application deployment process which uses local applications tied to a local OS and hardware.Â Virtualizing the hardware doesnâ€™t change that model but can provide benefits such as:
- Centralized control
- Added security
- More efficient backup
- Support staff reduction/repurposing
- Broader device support
- Reduced administrative overhead
Once the wound of our current application deployment model has fully healed, the band-aid comes off and we have service delivery from cloud computing environments free of any OS or hardware ties.
So friends donâ€™t let friends virtualize desktops right?
Not necessarily.Â As shown above VDI can have significant advantages over standard desktop deployment.Â Those advantages can drive business flexibility and reduce costs.Â The difficult questions will become
- Whether your organization can utilize a pure service delivery model based on security needs, organizational readiness, application/service readiness, etc.
- Whether the VDI gains will be seen before the infrastructure can be replaced with a fully service based model
Many organizations will still see benefits from deploying VDI today because the ROI of VDI will occur more quickly than the ability to deliver all business apps as a service.Â Additionally VDI is an excellent way to begin getting your feet wet with the concepts of supporting any device with organizational controls and delivering services remotely.Â Coupling VDI with things like thin apps will put you one step closer while providing additional flexibility to your IT environment.
When assessing a VDI project youâ€™ll want to take a close look at the time it will take your organization to hit ROI with the deployment and assess that against the time it would take to move to a pure service delivery model (if your organization would be capable of such.)Â VDI is a fantastic tool in the data center tool bag, but like all others itâ€™s not the right tool for every job.Â VDI is definitely the Next Generation but it is not The Final Frontier.
Here are some sales statements that are commonly used when pitching VDI, all of these I consider to be total hogwash.Â Try out or modify a few of my one line answers next time your vendors there telling you about the wonderful world of VDI and why you need it now.
Vendor: â€˜<Insert analyst here (Gartner, etc.)> says that 2011 is the year for VDI.â€™Â Alternatively â€˜<Insert analyst here (Gartner, etc.)> predicts VDI to grow X amount this year.â€™
My answer: â€˜Thatâ€™s quite interesting, letâ€™s adjourn for now and reconvene when youâ€™ve got data on <Insert analyst here (Gartner, etc.)>â€™s VDI predictions for the previous 5 years.â€™
Vendor: â€˜The next generation of workers coming from college demand to use the devices and services they are used to, to do their job.â€™
My answer: â€˜Excellent, theyâ€™ll enjoy working somewhere that allows that, we have corporate policies and rules to protect our data and network.â€™Â This wonâ€™t work in every case as Mike Stanley (@mikestanley) pointed out to me, universities for example have student IT consumers who are the paying customers, this would be much more difficult in such cases.
Vendor: â€˜People want a Bring Your Own (BYO) device model.â€™
My Answer: â€˜If I bring my own device and the fact that I want to matters, what makes you think Iâ€™ll want your desktop?Â Just give me application or service.â€™