PROVIDING DESKTOPS AS A SERVICE LICENSING GUIDE

Providing Desktopsas a ServiceLICENSING GUIDE

PROVIDING DESKTOPS AS A SERVICE LICENSING GUIDE

Microsoft offers multiple ways partners can create and deliver Desktop as a Service. This guide takes you through the Microsoft licensing options available and the required licensing components for providing Desktop as a Service to your users.

Licensing Options for Desktop as a ServiceOffering a Desktop as a Service (DaaS) solution requires giving your customer an appropriately licensed solution for the entire software solution stack. The software solution stack included depends on the software delivery model selected: the DaaS via the Windows Server operating system through the Microsoft Services Provider License Agreement (SPLA) or Dedicated Outsourcing with customer licenses. No option is available in the SPLA to provide a hosted virtual desktop using the Windows Desktop Operating System.

DaaS via Windows ServerTo deliver DaaS via Windows Server, you must license the required software through the SPLA. You can customize the Windows Server Remote Desktop Session Host experience for customers, offering a similar experience to the Windows Desktop Operating System. Windows Server Remote Desktop Services (RDS) is a centralized desktop and application platform solution, delivering presentation and application virtualization technologies. RDS offers you the opportunity to deliver and manage hosted desktops for customers via a supported, proven technology.

To provide DaaS in the licensing model above, you must license Windows Server, Remote Desktop Services, and any additional applications delivered with the DaaS offering through the SPLA.

Windows ServerWindows Server is licensed in the following two licensing models in the SPLA program:

Per Processor: Standard, Enterprise, and Datacenter Editions. You must have a Windows Server processor license to be assigned to each physical processor on the servers supporting your service.

Per User Subscriber Access License (“SAL”): Standard and Enterprise Editions. Customers must assign a SAL for Windows Server to each user that is authorized to access instances of the server software.

Windows Server Remote Desktop ServicesYou must have a SAL for RDS for each user authorized to access your DaaS offering. The following quote is directly from the Services Provider Use Rights (SPUR) document:“You must acquire a Windows Server RDS SAL for each user that is authorized to directly or indirectly access the server software to host a graphical user interface (using the Windows Server RDS functionality or other technology).”

PROVIDING DESKTOPS AS A SERVICE LICENSING GUIDE

Note that you must have the Windows Server RDS SAL for delivering a graphical user interface (GUI) even if you are not using RDS.

Additional Microsoft Desktop ApplicationsIf any additional Microsoft desktop applications are part of your DaaS offering, a SAL for the additional desktop application(s) is required for every unique user who is authorized to access the DaaS solution. Only user SALs are available for applications delivered as part of a DaaS solution (Device SALs are not available).

For example, a DaaS offering including Microsoft Office and Microsoft Visio drawing and diagramming software would require, in addition to the licenses for Windows Server, a user SAL for the following products for each authorized user of the service:

Microsoft Office Microsoft Visio Windows Remote Desktop Services

Dedicated Outsourcing for Desktop servicesYou can also provide DaaS for customers by using the customer’s own Volume Licenses in a dedicated environment (Dedicated Outsourcing). In this scenario, the customer remains the licensee, and all licenses must be deployed and managed in accordance with the Product Use Rights (PUR) and within a physically isolated hardware environment, separate from your other customers. The customer must provide the license for the Windows Desktop Operating System with Software Assurance (or the Virtual Desktop Access [VDA] Subscription license) and required Client Access Licenses (CALs) for implementing the Virtual Desktop Infrastructure (VDI) solution.

Windows Desktop Operating System The Volume Licensing customer provides the license for the Windows Desktop Operating

System through their current license agreement with Microsoft. VDA is granted through Software Assurance on the device or through a VDA Subscription. VDA provides rights to install virtual machines with the Windows operating system on

your servers to be accessed by the licensed device covered with Software Assurance or a VDA subscription.

Virtual machines with Windows running on your server require dedicated physical servers for each individual customer.

Additional Desktop Applications The Volume Licensing customer can provide the licenses for additional desktop

applications provided to be deployed in the dedicated instance. Deploying these desktop applications is subject to the licensing models and restrictions in

the PUR, along with any program specific grants in which the customer licensed the product.

Dedicated Hardware

PROVIDING DESKTOPS AS A SERVICE LICENSING GUIDE

If a customer wants to use their Microsoft Volume Licensing software to receive a hosted virtual desktop delivered to them by you, you must provide fully dedicated physical servers for that customer. The Volume Licensing customer may not be deployed on shared physical servers with other customers (customers with licenses or not). After a fully dedicated physical server environment is in place, the Volume Licensing customer can assign their licenses to your dedicated physical servers per the license requirements in the PUR.

PROVIDING DESKTOPS AS A SERVICE LICENSING GUIDE

Additional Services for Dedicated Outsourcing CustomersYou can provide additional software services to your dedicated outsourcing customers via your SPLA. In addition, multiple customers can share this service. However, the shared server environment that supports such a service cannot be shared with the dedicated physical server environment that supports the dedicated DaaS for any customer.

Frequently Asked QuestionsCan I host the Windows Desktop Operating System through the SPLA? No. No option is available in the SPLA to provide a hosted virtual desktop using the Windows Desktop Operating System.

Can I host Microsoft Office for a customer who is receiving dedicated outsourcing for desktop services?Yes. You can provide additional software services to your dedicated outsourcing customers via your SPLA. In addition, multiple customers can share this service. However, the shared server environment that supports such a hosted Microsoft Office service cannot be shared with the dedicated physical server environment that supports the dedicated DaaS for any customer.

Does Microsoft support offering streamed Microsoft Office to complement my DaaS service? No. The SPLA does not provide rights to stream Microsoft Office to a device and have the user run it locally. You can, however, provide a hosted Microsoft Office solution through RDS.

See the SPUR for the specific license rights for Microsoft Office and Microsoft Application Virtualization Hosting for Desktops. Also, see the Partner Hosted Office Licensing Guide for more information on licensing for Hosted Office scenarios.

Can I deploy multiple customers’ licensed software in a shared hardware environment?No. A customer’s licenses must be deployed in physically isolated environments and are subject to the license rights of the Volume Licensing agreement under which they were purchased.

Can my customer take advantage of License Mobility through Software Assurance to receive a hosted desktop experience/DaaS?No. The Windows Desktop Operating System is not eligible for License Mobility through Software Assurance.

How is delivering a DaaS solution different than using Rental Rights?Rental Rights provide the rights to offer rental PCs to customers whereas the Windows Desktop Operating System software is physically installed on the PC, but does not offer rights to remote access or other features of DaaS. DaaS via Windows Server and dedicated outsourcing provides the features necessary for the DaaS experience. See http://www.microsoft.com/licensing/about-licensing/rental-rights.aspx for more information about Rental Rights.

How can I assure my users that the DaaS solution I am offering is properly licensed?

PROVIDING DESKTOPS AS A SERVICE LICENSING GUIDE

While Microsoft does not confirm an individual partner’s license compliance, you can take the following steps to help your customers understand your compliance with Microsoft’s licensing requirements:

Ensure your marketing materials do not create confusion about how your solution might comply with Microsoft licensing requirements (for example, you should not reference the Windows 7 Desktop Operating System if you are providing a solution based on Windows Server and Remote Desktop Services).

Review and abide by the trademark guidelines for the products you are licensing. See www.microsoft.com/trademarks and your licensing agreement.

Provide public frequently asked questions (FAQ) that describe how your solution meets the Microsoft licensing requirements for a DaaS Solution.

© 2012 Microsoft Corporation. All rights reserved.

The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED, OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

0912