Scott Lowe discusses some strategic reasons why Microsoft has held onto VDA licensing for so long, despite its high cost.
Even while storage and other infrastructure vendors struggle to reduce the per-unit costs of virtual desktop infrastructure initiatives, there’s one aspect of these solutions that hasn’t changed much in recent years: Microsoft’s licensing associated with these kinds of initiatives. Licensing remains a somewhat confusing mess, but I see multiple reasons why Microsoft has yet to correct the issue.
VDA, CDL, SA
Microsoft has a wide variety of licensing programs under which virtual desktops may fit. The most common is Microsoft’s Software Assurance (SA) program. For customers who participate in this program, some desktop virtualization rights are included. For example, you can use a full Windows PC as a Virtual Desktop Infrastructure (VDI) endpoint without having to purchase separate Virtual Desktop Access (VDA) licensing. Bear in mind, though, that this doesn’t cover thin clients that don’t already run Windows. For those clients, you’ll still need to procure a VDA license. I’ll explain the VDA license shortly.
For Windows 8 users, Microsoft also makes available the Companion Desktop License (CDL), but at an additional charge. This license allows a user to access a virtual desktop from up to four devices, such as an iPad, Android tablet, or other such device. It also requires the procurement of VDA. So, in essence, you need Windows 8 + SA or VDA + CDL in order to use your iPad to connect to a virtual desktop instance at work.
VDA and how it’s a strategic move for Microsoft
So, exactly what is this VDA license? Simply put, it’s Microsoft’s way to continue to collect per endpoint revenue for each device that’s used in the corporate world. Microsoft charges $100 per year for each device under this license. If you have a device under VDA, and you’re planning out five years, you can spend $500 over the course of that time just for the privilege of connecting that device to a Windows-based virtual machine for VDI purposes. Suddenly, that inexpensive thin client has been burdened with a cost that exceeds a full-fledged Windows PC.
This licensing program has negated many of the economic benefits of VDI for many organizations. Were it not for this program, I suspect that the industry would be much more VDI uptake. Microsoft, however, would see a net loss in market share and revenue, since the company would be giving up endpoint revenue.
That’s strategic move #1 for Microsoft in favor of VDA. With this license, regardless of the kind of device a customer intends to connect to the VDI environment (whether that device is running Windows Embedded or some Linux variant), Microsoft will continue to receive a payment for that device. I’m sure that, when VDI started gaining steam and non-Widows thin clients became popular, Microsoft was concerned about the erosion of the desktop-based profit stream. As such, VDA was born.
What about the long term?
Frankly, I’m surprised that something hasn’t come along to replace VDA. The licensing program is expensive, and it’s often cited as the reason that some VDI projects fail to meet economic goals. As such, organizations have found other business reasons to consider VDI, including being in support of BYOD initiatives. Of course, there are ways to make the justification, but the fact remains that VDA licensing is a hindrance.
To be fair, there may be more to the program than meets the eye. Microsoft is reportedly working on a Desktop as a Service (DaaS) offering with the codename Mohoro. It’s rumored that this service will sit alongside Office 365 and Azure — or ride on those platforms — and that it will become available in the second half of 2014. Mohoro is intended to provide RemoteApp-like functionality. If that’s the case, then it seems as if users would be able to run Windows programs from the cloud on pretty much any device of their choosing.
I fully expect that there will be licensing costs for Mohoro in the form of some kind of subscription. It’s possible that this cost will be less than VDA pricing, too, which might make Microsoft’s own DaaS offering more compelling from a cost standpoint. That’s strategic reason #2 that I see for Microsoft to have maintained VDA for so long. If they can hold the status quo until their own offering is ready, then they avoid seeing people make a jump to other platforms, at least on the business side.