X
Business

Microsoft's desktop virtualization announcements: Take 2

Microsoft's Matt McSpirit responds to yesterday's post
Written by Dan Kusnetzky, Contributor

Yesterday I posted something about Microsoft's desktop virtualization announcement. Almost immediately, Matt McSpirit, Microsoft UK's partner technology adviser for virtualization and management reached out with a few corrections. I've gotten permission to republish some of his comments. Thanks, Matt!

Here's what Matt had to say:

I was reading your article entitled "Microsoft's desktop virtualization announcements: Citrix and customers are the winners", however when talking about the changes in VDI licensing, with VECD becoming VDA, you state it's only a free benefit for Software Assurance Customers, which is not quite accurate. It's now free for those SA-covered devices (previously $23 per device, per year), however there is a separate SKU to cover devices that aren't covered by an SA agreement (Thin Clients can't be, along with OEM PCs, or non-SA devices that weren't covered as a choice by the customer).

This separate SKU is the VDA (Virtual Desktop Access) license, and has a retail price of $100 per device, per year. The primary/named user of this device also gets the roaming use rights that you correctly describe in your post.

More info here: http://www.simonbramfitt.com/2010/03/the-sleeping-giant-awakes-microsoft-gets-desktop-virtualization-right.html

You could, prior to the announcements, purchase VECD for SA (for those customer who already had SA on their desktops, for $23 per device per year), or, for non-SA devices, you could purchase VECD ($110 per year, per device) so there has been a solution for non-SA devices, but a) not everyone knew about it, and b) it didn't give the roaming capabilities that have recently been announced for VDA.

I hope that helps to clarify the story, and provide extra detail for your users.

Thanks!

Matt

There you have it. I still think that this is more complicated than it needs to be. While it certainly reduces the barrier Microsoft customers face, there is still a barrier.

Editorial standards