DaaS, Part 2 (3 of 3) – what happens when you provide it with a Microsoft OS?

Recap, Part 2 (1 + 2 of 3): As an MSP you have to use licenses from the SPLA Program if you want to offer solutions based on Microsoft software which also includes licenses. Windows 7 Enterprise is definitely the OS you want to provide your complete managed DaaS.

The Issue
When working with managed services and SCCM, as the “manager”, you cannot use OEM-versions as OS-license because you can’t control the license, it belongs to one specific computer, and you cannot handle one image for every PC. Neither can you use non VL-licenses, like the Windows 7 Ultimate, because they use traditional Microsoft licensing servers and not KMS or MAK (read more). You are stacked to use either licenses from VL or SPLA.

Check the picture in chapter 2 again which says; “The Windows 7 Enterprise operating system (OS) is available to Microsoft Software Assurance customers”. This means you can find the Windows 7 Enterprise version in the VL Programs, if you signed up for SA. This is a fact and I won’t go in to that discussion even if I think you should be able to buy it without SA. So this is fine if you as an MSP want to offer a managed DaaS where the customer is responsible for the licenses.

A complete managed DaaS where the license is included should then use Windows OS license from the SPLA program. Here is the big problem; Microsoft only offers Professional in the SPLA Program! According to Microsoft; Windows 7 Enterprise is an SA benefit. According to me; SPLA is in a way SA too, you have the right to run the latest version; SPLA is the way to offer services including the license; Windows Enterprise is the version for companies; why isn’t it available in SPLA? MSP doesn’t need the other SA-benefits but we need the Enterprise version and I really think we’re paying for it.

Going back to the DaaS, part 1; as a MSP you will not be able to fulfill 100% because if you want to give enterprises enterprise options customers have to buy or subscript their own licenses from a VL agreement. Today there is no way to deliver a complete managed DaaS. Microsoft; please do check this out; you are making a mistake here. I’ve talked to a lot of people at Microsoft about this; both on Nordic, EMEA and Corp level but no one really understand or can explain why it isn’t available in SPLA. My intention was to discuss this on the DaaS round table at Microsoft Hosting Summit 2011. Unfortunately all the talk was about VD’s, AppV and other V-things – yes, “the other” DaaS…

Microsoft, you haven’t done your homework in this matter. Adjust to the market like you did with the excellent License Mobility. Make the Windows Client Enterprise SKU available in SPLA Program. It really can’t be that difficult.

Don’t misunderstand me, I love Windows 7 Enterprise and we want to offer it in our services, but we can’t.

The end of DaaS, Part 2 – what happens when you provide it with a Microsoft OS? Thank you for reading the whole story.

All articles in my special DaaS story:
DaaS, Part 1 – do we all mean the same thing?
DaaS, Part 2 (1 of 3) – what happens when you provide it with a Microsoft OS?
DaaS, Part 2 (2 of 3) – what happens when you provide it with a Microsoft OS?
DaaS, Part 2 (3 of 3) – what happens when you provide it with a Microsoft OS?

If you want to engage me or discuss this further; please contact me.

DaaS, Part 2 (2 of 3) – what happens when you provide it with a Microsoft OS?

Recap DaaS, Part 2 (1 of 3) : As an MSP you have to use licenses from the SPLA Program if you want to offer solutions based on Microsoft software which also includes licenses.

Windows 7 Enterprise
As a MSP you want to offer services and solutions which bring the best value to the customer and the best business for the MSP. Best value to a customer (small, SME/-B or Ent) is offering Microsoft Windows 7 Enterprise as the OS in a complete managed DaaS. It offers features lower versions don’t. This is a breakout from a Microsoft website about Windows 7 Enterprise:

As you can see Microsoft says “unique technology for enterprise customers” and “with Windows 7 Enterprise, you can take advantage of the following features that are not available in Windows 7 Professional”. Note! “…not available in Windows 7 Professional”.

A true complete managed DaaS should be based on Windows 7 Enterprise and not on Professional. You have the great and professional features listed above where I want to highlight especially DirectAcess but also the BranchCache, Federated Search, BitLocker + TG and AppLocker…and then why not mention the other two great VDI opt and Multilingual UI. They are all features companies should take part of. But they cannot...in a complet managed DaaS.

Tomorrow: DaaS, Part 2 (3 of 3 ) -‘The issue’

All articles in my special DaaS story:
DaaS, Part 1 – do we all mean the same thing?
DaaS, Part 2 (1 of 3) – what happens when you provide it with a Microsoft OS?
DaaS, Part 2 (2 of 3) – what happens when you provide it with a Microsoft OS?
DaaS, Part 2 (3 of 3) – what happens when you provide it with a Microsoft OS?

DaaS, Part 2 (1 of 3) – what happens when you provide it with a Microsoft OS?

This is really not the biggest issue in the cloud and XaaS-world but I feel significant enough to highlight. Never the less it is one of these issues that players on the cloud market have to adjust to make the cloud work ok. I know it is a long story, but it has to be said. I have divided the Part 2 into three parts to make it easier to read.

If I could get 10 people at Microsoft to read and understand this… It could be a “small step for Microsoft, a giant leap for “DaaS-kind””. ;)

Recap DaaS, Part 1: There are two types of DaaS: the traditional virtual desktop and the growing complete managed DaaS which includes desktop (vd or not), hardware and the complete management. But it’s difficult when you as an MSP want to include the license.

Last spring I was invited to Microsoft in Sweden to discuss the possibility to sell complete managed DaaS including Win OS and Office 2010. Note! This meeting wasn’t initiated by me. But since I’m really in to this type of services I started to check this out and soon the idea ran into trouble…

License basics
As an MSP delivering services based on Microsoft software you should use the SPLA Program. You are not allowed to lease any other type of licenses. You can use SPLA as long as you have control of the equipment, this means either MSP- or customer owned equipment in a datacenter or MSP owned equipment on-premise at the customer. But you can never use it on customer owned equipment on-premise at the customer.

In some cases (private clouds and systems which can be a part of License Mobility) the customer can use their own licenses and they can be bought or subscribed from Microsoft, but it is a business between the customer, a LAR (Large Account Reseller) and Microsoft.

License basic is; you should have a license to have the right to install (and use) the software and you should have control of the equipment where the software is installed so you can uninstall it when the right to have it installed ends. That’s why an OEM-license comes with the computer, not the user.

This is quite clear by Microsoft. As an MSP you know quite well what you can and cannot do. But this is also where Microsoft stops the evolution of a complete managed DaaS.

To be continued in DaaS, Part 2 (2 of 3). Coming soon.

All articles in my special DaaS story:
DaaS, Part 1 – do we all mean the same thing?
DaaS, Part 2 (1 of 3) – what happens when you provide it with a Microsoft OS?
DaaS, Part 2 (2 of 3) – what happens when you provide it with a Microsoft OS?
DaaS, Part 2 (3 of 3) – what happens when you provide it with a Microsoft OS?