DaaS, Part 1 – do we all mean the same thing?

When talking DaaS (Desktop as a Service) I often get confused; what do you/I/we mean? One type is the traditional virtual desktop accessed by i.e. Microsoft Remote Desktop Services Client (formerly known as Terminal Services Client) with or without a Citrix Desktop Receiver. I think this is a SaaS, maybe a bit advanced but still a SaaS and a SaaS only. This type is according to me far the most common DaaS on the WW market. The other is as I see it most frequent on the Nordic market but please tell me if I lack in this.

Another type of DaaS, the one I usually think about is a complete managed DaaS. A DaaS including the basic infrastructure, platform, directory, file and print services which all will be accessed from a thin client, pad or a traditional pc, no matter the OS. The physical client itself should be included in the service, a physical client which of course contains a complete and environmental certificated (green) DLM (Desktop Lifecycle Management). Responsible for managing the physical client and the OS are the MSP, i.e. with Microsoft System Center Configuration Manager (SCCM) and the physical support handled by IMAC-D routines. The customer should only have to call for 1 piece of DaaS to fulfill one users need during agreed time and price.

What about the license? Yes, it should be included but it isn’t that easy if we want to use the most common operating system – Microsoft Windows. I will get back to this issue in: DaaS, Part 2 – what happens when you provide it with a Microsoft OS? which will be available in a couple of days.

To the DaaS customers should be able to add their typical applications and services (cloud or not). Whether this software and licenses can be included is more a LA (License Agreement), logistic and policy thing. If you as a MSP can lease it and make money out of it – why shouldn’t you?

I really can’t say which one of them is "true" DaaS but customers and MSP’s must be able to differentiate them from each other. Should you rather call the complete managed DaaS a WaaS, (Workplace as a Service) instead? Maybe, but it might confuse more than explain and it really gets a bit frustrating with all the different XaaS’s meaning different and same things.

I think the complete managed DaaS-market will increase. It’s part of the Orchestrator mind set. Customers have to focus on the core business. Customers have to buy complete IT, not one or more XaaS’s who fulfill 25, 50 or 75%. Do remember; the customers’ internal IT department can be the Orchestrator.

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?