Over a million developers have joined DZone.

Licensing Woes for Delivering Desktops as a Service

DZone's Guide to

Licensing Woes for Delivering Desktops as a Service

· Cloud Zone
Free Resource

Are you joining the containers revolution? Start leveraging container management using Platform9's ultimate guide to Kubernetes deployment.

For years I’ve been talking internally (and some externally) about the horrible licensing situation Microsoft has around delivering desktops as a service. This started with VDI type of solutions and continues for cloud-based desktop delivery. I haven’t been able to write about it very much because my employer didn’t want a post to setup some sort of liability situation. Fair enough. So for the past several years I’ve just told people, “you really need to look at your licensing implications and a good place to start is Lady Licensing’s website” (thank you Emma for an awesome resource.

That all changes now. Thanks to Brian Madden and Gabe van Zanten there’s been a lot of talk about MS licensing woes for desktops. I’m glad the discussion is finally taking place and I really hope the community pressures Microsoft to adjust their desktop licensing policies just like they adjusted their server licensing policies to let customers actually use their software in a more effective way. Remember, it’s only you the customer that can make this change – typically other vendors don’t have the right pressure points to press on.

Make sure you go and read Brian’s latest post on this topic with all of the relevant links to the right information. Then go and contact your Microsoft rep and VPs and anyone else you have contacts for an press on them to start doing the smart thing here.

Mike out.

Using Containers? Read our Kubernetes Comparison eBook to learn the positives and negatives of Kubernetes, Mesos, Docker Swarm and EC2 Container Services.


Published at DZone with permission of Mike Dipetrillo, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}