I’ve been out and about a lot this year presenting my researching on “Attacking the High Costs of Desktop Virtualization” and although I could give this presentation in my sleep I realized after my presentation at Gartner Catalyst that I needed to address a question that has come up in every presentation during Q/A:
What about the license cost for Microsoft?
I’m not sure why I didn’t address this question earlier. I talk about it in my research but when I present on it I skip over it. Maybe I’m externalizing an internal debate “there is nothing I can do about it so why bother” the problem is that’s Gunnar Berger talking, not Research Director at Gartner, Gunnar Berger. At some point before VMworld I decided that its my job, as a voice in the industry, to fight for my clients and to say out loud what they say to me in private. So I took to the stage with my traditional material on VDI cost (storage, storage and more storage) and I added something new: #FixVDA!
#FixVDA is simple to understand in a single hashtag: something is broken in the Virtual Desktop Access (VDA) license and needs to be fixed. I created a couple slides in my presentation that pointed to some of the fundamental flaws of this license. The first slide points to the exponential cost difference between using Windows Server “as a desktop” utilizing the RDS CAL versus using Windows Client OS as a desktop:
Then I summed up this cost difference in a few words:
There are a lot of things that have caused virtual desktop technology to stall in its adoption. However as I point out in my presentation, many of these things (storage/clients/software) are cost driven and are being addressed. As a whole, VDI is getting closer to the point where a virtual desktop is cost equivalent to a physical desktop. I believe the game changer in this industry happens when it is common knowledge that a virtual desktop is cheaper than a physical desktop. That’s what happened with servers, that hasn’t happened with desktops… at least not yet. To get there we need lots of vendors to work together to make this stuff more cost effective but one thing we really need is for Microsoft to get on board.
I have some thoughts as to how this can be done, but for this first blog I wanted to summarize that which I have already said.
See Part 2