EMC VMware made much of its dual-prong approach to overcoming challenges in cloud infrastructure with its vCloud Suite and end-user computing arena with its new Horizon suite. A great deal of work remains, but the goal of these two suites is to eventually provide a holistic approach stretching from the user's desktop (whether a traditional desktop or mobile device) all the way through the infrastructure nuts and bolts that allow delivery of application services.
Missing in the myriad PowerPoint presentations was VMware's VDI product, VMware View. It doesn't seem to fit into either suite and is left floating somewhere between cloud infrastructure and end-user experience delivery without a clear home in either.
[ Get InfoWorld's Deep Dive report on how to deploy VDI. | Looking to run Microsoft Office via Windows on your iPad? See InfoWorld's top pick. | Subscribe today to the Enterprise Data Explosion newsletter for the latest insights on data center and enterprise storage technology. ]
Part of me hoped to see View eventually find its way into the vCloud Suite so that public and private cloud operators could deliver Windows instances via the cloud (called desktop as a service, or DaaS, by the industry). It's true that View would need to be heavily refactored to make this jump because it currently integrates directly with VMware vCenter to automate the provisioning of desktop pools and is incompatible with vCloud Director. At the moment, VMware seems to have no appetite to overcome that challenge.
The reason it lacks the appetite, though, is not because VMware sees no value in selling vCloud Director to provide DaaS. No, the issue is that Microsoft's licensing rules have made it virtually impossible to carry off.
To continue reading, register here to become an Insider.
This story, "Microsoft sabotages Windows-via-the-cloud services" was originally published by InfoWorld.