Understanding Microsoft's New Windows Virtual Desktop Licensing with Software Assurance
As of July 1, Microsoft will bundle VDI/VDA licensing for the Windows client OS into Software Assurance. Here's how the changes may affect you.
- By Greg Shields
Buy Software Assurance but prepare for a recurring cost. That was the unspoken assertion by Microsoft in this month's Virtualized Enterprise Centralized Desktop (VECD) -- also known as VECD Becomes Virtual Desktop Access (VDA) -- licensing changeover. As of July 1, Microsoft will bundle Virtual Desktop Infrastructure (VDI) licensing for the Windows client OS into Software Assurance (SA). Environments that don't have or don't want SA will be required to purchase a separate Windows VDA license for every VDI-hosted desktop.
It's the quiet sea change in licensing language that's particularly worth noting. In short, Microsoft wants more annuity income. It's when you want to use an OS instance through a VDI environment that VDA -- either as part of an SA agreement or not -- comes into play.
Many companies and most enterprises have found use cases where VDI makes operational and economic sense. And as technologies grow and improve over time, we're likely to find VDI successfully creeping into even more use cases over the long term.
It's here where a careful analysis can reveal Microsoft's impending cash cow. If your business tries to save costs by opting out of SA, you're still on the hook for licensing VDI-hosted desktops at $100 per year per device. This fee goes away when you buy up to SA.
I'll Pay If You'll Play
VDA is a per-device license, giving VDI-hosted desktops a set of additional benefits that weren't present in the previous licensing terms. Users who have a primary computer at the office but occasionally work from home will be able to use their VDI instances from their home computers. Shift-worker environments need only purchase enough licenses for each device, no matter how many users may use that device over the course of the day.
While Microsoft extols these two benefits, there's an argument that neither benefit is all that compelling for the vast majority of businesses. Companies who allow people to work from home often give them a laptop as their primary computer (which, by default, tends to become their connection device). This fact reduces the efficacy of the "occasional home use" benefit. Secondly, while shift-worker environments absolutely do exist, they're nowhere near as prevalent as situations involving typical office workers working typical office hours.
VDA's per-device basis will bite you in other ways as well. For example, extra licenses must be purchased for 100 percent home users who aren't given a company-owned device. Extra licenses must also be purchased for users of thin clients.
Per Device or Per User?
Microsoft has never been a company that looks kindly on per-user licensing. OSes being what they are, this historical aversion makes sense. Until only recently, you could install an OS in one place and get the reasonable assurance that OS stayed on that machine. But today's workforce and technologies are evolving to the point where the OS no longer makes operational sense to be tied to a specific device.
Think about these real situations: "Occasional home access" means I can connect to my VDI-hosted desktop through devices that I own, such as my personal computer or mobile phone. But what if my company owns my phone or lets me borrow a piece of its equipment? If I access my VDI-hosted desktop through a company-owned phone, or a company-owned loaner laptop, or even a kiosk in the company lunchroom, that device needs licensing as well.
VDI by definition is intended to deliver a desktop to anywhere, but if I can't control where that may be, staying legal could be impossible.
The language of VDA is a step above the previous VECD, but Microsoft's insinuations of "we're going to make this smell like per-user, without actually making it per-user" in its licensing language is infuriating. Per-device plus a "sometimes at home" option is per-user licensing. The entire concept that an OS that used to be locked to a device for purely technical reasons can now be additionally extended to everywhere just intrinsically reeks of per-user.
About the Author
Greg Shields is Author Evangelist with PluralSight, and is a globally-recognized expert on systems management, virtualization, and cloud technologies. A multiple-year recipient of the Microsoft MVP, VMware vExpert, and Citrix CTP awards, Greg is a contributing editor for Redmond Magazine and Virtualization Review Magazine, and is a frequent speaker at IT conferences worldwide. Reach him on Twitter at @concentratedgreg.