Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
This SPLA Compliance Check List document has been compiled by HP SLMS to assist Service Providers in understanding the
program and product licensing rules under Microsofts Service Provider Licensing Agreement (SPLA) with a view to reporting
license usage accurately and achieving compliancy. It covers the main areas to consider when assessing and quantifying
licensing requirements under SPLA. It is intended to be used in conjunction with Microsofts Service Provider Use Rights (SPUR)
document - which governs the use of Microsoft software products and is the only complete, up-to-date and legal source of
SPLA licensing information - as well as the SPLA agreement signed by the Service Provider with Microsoft.
Table of Contents
Licensing Types under SPLA .............................................................................................................................................................. 2
Software Dependencies .................................................................................................................................................................... 2
Windows Server 2012 R2 .................................................................................................................................................................. 3
SQL Server 2014 ................................................................................................................................................................................ 4
System Center 2012 R2 ..................................................................................................................................................................... 5
Core Infrastructure Server (CIS) Suites ............................................................................................................................................. 6
Cloud Platform Suite (CPS)................................................................................................................................................................ 6
Exchange Server 2013 ....................................................................................................................................................................... 6
Lync Server 2013 ............................................................................................................................................................................... 7
SharePoint Server 2013 .................................................................................................................................................................... 7
Productivity Suite.............................................................................................................................................................................. 7
Forefront Identity Manager 2010 R2 ................................................................................................................................................ 7
Remote Desktop Services, AD Rights Management Services & App Virtualization for RDS.............................................................. 7
Office 2013 ....................................................................................................................................................................................... 8
Azure ................................................................................................................................................................................................. 8
Rental/Managed PC Environments ................................................................................................................................................... 8
Hardware Ownership ........................................................................................................................................................................ 9
Disaster Recovery ............................................................................................................................................................................. 9
Downgrade Rights........................................................................................................................................................................... 10
License Mobility through Software Assurance ............................................................................................................................... 10
Internal Use .................................................................................................................................................................................... 10
Dedicated Hosting - Customer Owned Licenses ............................................................................................................................. 11
Windows Desktop OS...................................................................................................................................................................... 11
Virtual Desktop Infrastructure (VDI) - Streaming - Desktop as a Service (DaaS) ............................................................................ 11
January 15 Edition
Per Processor for Host: License the hardware per processor for the host fabric in which an instance can run
Per Instance for Guest: License for each virtual instance that runs on the host
Software Dependencies
With some Microsoft software products, there may be requirements for software to be used in conjunction with others as part
of a solution stack i.e. if you license Product A which requires Product B, then Product B will need to be licensed also. Service
Providers need to know what products are required to deploy a solution and ensure all these products are licensed
appropriately.
Microsoft publishes a Software Licensing Dependency Reference Guide. While designed for volume licensing programs, it
provides useful information on software dependencies from a purely technical perspective. SPLA can have additional licensing
requirements sitting on top of the technical dependencies so Service Providers should always consult the SPUR or contact HP
SLMS for advice. Here are some examples:
SQL requires Windows. This means that if you report SQL licenses, you also need to report Windows licenses covering
the Operating System.
SharePoint requires Windows & SQL: This means that if you report SharePoint licenses you also need to report
Windows licenses covering the Operating System, and SQL licenses covering the server(s) on which SQL is installed.
Hosted Exchange requires Windows: This means that if you report Exchange licenses, you also need to report
Windows licenses covering the Operating System.
Dynamics NAV requires Windows and SQL. This means that if you report Dynamics NAV licenses you also need to
report Windows licenses covering the Operating System, and SQL licenses covering the server(s) on which SQL is
installed.
January 15 Edition
Service Provider licenses a 2-processor server 2 Processor Licenses to cover a 2-processor server.
Service Provider licenses a 4-processor server 4 Processor Licenses to cover a 4-processor server.
Service Provider licenses a 2-processor server with 4 VMs 8 Processor Licenses for 4 VMs on a 2-processor server.
Service Provider licenses a 2-processor server with 6 VMs 12 Processor Licenses for 6 VMs on a 2-processor server.
Windows Server 2012 R2 Essentials, the latest version of Windows Small Business Server Essentials, is also available under
SPLA. It can run on physical servers with up to two processors and has been designed for small businesses with up to 25 users.
January 15 Edition
Physical Server Licensing: License all physical cores on hardware. Minimum 4 core licenses per physical
processor. Core licenses sold in 2-core packs.
License by Virtual Machine: License only the virtual cores deployed for each Virtual Machine. Minimum of 4
virtual cores per VM.
Unlimited virtualization is available for Enterprise Edition when the Service Provider licenses all Cores on the physical hardware.
Microsoft has also introduced SQL Parallel Data Warehouse, a special edition of SQL Server optimized to support data
warehouse solutions targeted primarily at SaaS ISVs. From a licensing perspective, the PDW appliance is considered to be a
single unit with two or more servers controlled by a single PDW virtual OSE. Service Providers should report all physical cores
running the SQL PDW software and report all physical processors running Windows Server Standard and System Center
Standard software each month. SQL PDW part number is only available with an amendment under SPLA.
Downgrade Rights
There are very specific downgrade rights that apply to SQL 2014. Please refer to the SPUR for full details on down-edition rights
per edition.
Fail-Over
When a Service Provider is licensing SQL products by Core (if SQL 2014 or SQL 2012) or Processor License (if SQL 2008 R2 or
prior), the following are the rules on Fail-Over Servers taken from the SPUR document.
For any OSE in which you run instances of the server software, you may run up to the same number of passive
fail-over instances in a separate OSE in anticipation of a fail-over event. You may run the passive fail-over
instances on a server other than the licensed server. However, if you licensed the server software under the
Physical Cores of a Server section above and the OSE in which you run the passive fail-over instances is on a
separate server, the number of physical cores on the separate server must not exceed the number of physical
cores on the licensed server and the core factor for the physical processors in that server must be the same or
lower than the core factor for the physical processors in the licensed server. If you have licensed the server
software under the Individual Virtual OSE section above, the number of hardware threads used in that separate
OSE must not exceed the number of hardware threads used in the corresponding OSE in which the active
instances run.
Clustering
If there is any clustering in the server architecture where Virtual Machines float between servers in a server farm this will
need to be assessed.
January 15 Edition
System Center 2012 R2 Client Management Suite includes Services Manager, Operations Manager, Data Protection
Manager and Orchestrator functionality.
System Center 2012 R2 Configuration Manager SAL will also include Virtual Machine Manager functionality.
Forefront Endpoint Protection joined System Center 2012 family of products and was rebranded System Center R2
Endpoint Protection.
Previous Editions
With the release of System Center 2012, the previous editions of System Center components were retired:
However, Service Providers can continue ordering software product after they have been removed from the SPLA pricelist until
they have migrated to a newer version or their agreement expires (whichever comes first). New and renewal may only order
System Center 2012 products.
January 15 Edition
Environments: Both are ideal for highly virtualized servers but while Core Infrastructure Suite is ideal for managing a
homogenous environment of Windows Server workloads, the Cloud Platform Suite enables Service Providers to
manage a heterogeneous environment running multiple server operating systems.
January 15 Edition
Productivity Suite
Productivity Suite SAL provides cost savings as a suite over buying component SALs separately. It provides rights equivalent to
Exchange 2013 Standard SAL, Lync Server 2013 Enterprise SAL & SharePoint Server 2013 Standard SAL. It is licensed per user
SAL only.
Remote Desktop Services, AD Rights Management Services & App Virtualization for RDS
Remote Desktop Services SAL
Under SPLA, Service Providers must report a Remote Desktop Services Subscriber Access License (SAL) for every user authorized
to access the Windows Server 2012 RDS functionality, regardless of actual access. Service Providers must also acquire a
Windows Server 2012 Remote Desktop Services SAL for each user that is authorized to directly or indirectly access Windows
Server 2012 Remote Desktop Services or Windows Server 2012 to host a graphical user interface (using the Windows Server
2012 Remote Desktop Services functionality or other technology).
Active Directory Rights Management Services SAL
Service Providers must acquire a Windows Server 2012 Active Directory Rights Management Services SAL for each user that is
authorized to directly or indirectly access the Windows Server 2012 Active Directory Rights Management Services functionality.
Application Virtualization for Remote Desktop Services
Service Providers must acquire a Windows Server 2012 Remote Desktop Services SAL for each user that is authorized to directly
or indirectly access the Microsoft Application Virtualization for Remote Desktop Services functionality. Application Virtualization
SAL is only available for Service Providers to stream any non-Microsoft application to the end-users device with the exception
of Dynamics NAV.
January 15 Edition
Office 2013
There are two ways that a Service Provider can license Office software to deliver a hosted solution under SPLA. The first option
involves hosting on Windows Server and users connect to it using Remote Desktop Services; the second is on Rental/Managed
PCs where Office SALs need to be reported.
A similar approach is taken to license other desktop productivity software such as Visio (Standard & Enterprise) or Project
(Standard & Enterprise).
(i) Using Remote Desktop Services
Office is hosted on Windows Server and Service Provider is required to license the entire software solution stack appropriately.
Therefore they need to report Windows Server licenses, Office SALs & Windows Remote Desktop Services SALs. Windows
Server 2012 licensing is described above. A SAL for Remote Desktop Services (RDS) is required for each unique end user
authorized to access the hosted Office service. A SAL for Microsoft Office (Office Standard or Office Professional Plus) is
required for every unique end user who is authorized to access the hosted Office service. The quantity of RDS SALs and Office
SALs reported must always match.
(ii) Rental/Managed PC
If Service Provider is providing a Rental/Managed PC with Windows, they need to report a Windows Professional Upgrade SAL
assigned to each laptop or PC as part of the SPLA Rental PC amendment. Rental rights are available only through an
amendment - the Managed PC Amendment (K04). Service Provider would need to sign this amendment to get access to
Windows Professional Upgrade SKU that has to be installed on top of their OEM version of Windows.
Azure
Windows Azure Services platform is considered a Data Center Provider by Microsoft and can be used by Service Providers to
deliver software services under the same terms as those governing the use of other Data Center Providers. Use of products on
Windows Azure is subject to Microsofts verification under the terms of the Service Providers SPLA. Windows Azure is not
available to be licensed through the SPLA. It can be purchased either directly at windowsazure.com or via a Microsoft
Enterprise Agreement.
Only v2013 agreements include language to support the use of Azure as the Datacenter Provider. Even though SPLA
agreements prior to v2013 do not include the language to support Azure as Datacenter Provider, those Service Providers are
permitted from use of products on Windows Azure to provide software services and are not obliged to sign a new v2013
agreement before use of products on Windows Azure to provide software services becomes an option. Microsoft state that
signing a SPLA v2013 agreement does open up greater possibilities for the Service Provider in the whole area of Datacenter
Providers, Software Services Resellers etc. An important point to make is that Service Providers must comply with the rules in
the SPUR regarding what products are available for licensing on top of data center providers server. Products are designated
YES in the SPUR as Eligible for Software Services on Data Center Providers.
Rental/Managed PC Environments
Operating System upgrade licenses are offered in SPLA only for the scenario where the Service Provider is providing
rental/managed PCs to end customers on a rental or subscription basis, and only through the Rental/Managed PC Amendment
(K04).
Request for the amendment needs to be sent to the local Microsoft Licensing Sales Specialist (LSS) and accompanied by
information on what OEM client OS licenses the Service Provider will be bringing to the solution, a high level explanation of
service they plan to offer along with the relevant Program Signature Form.
January 15 Edition
Hardware Ownership
Under all SPLA v2010 agreements, Service Provider must own or lease the hardware on which the SPLA-licensed product is
installed to provide software services regardless of the location of the servers (e.g. at end-user premise, Service Providers own
datacenter). SPLA v2013 agreements will allow SPLA-licensed product to be installed on end customer-owned hardware.
SPLA v2013 agreements will allow SPLA-licensed product to be installed on end customer-owned hardware provided the Service
Provider maintains day-to-day control and management of this hardware.
Disaster Recovery
Note the following extract covers Disaster Recovery rights and is taken from the Universal License Terms of the July 14
Service Provider Use Rights (SPUR):
Disaster Recovery Rights
For each instance of eligible server software licensed in the Per Processor or Per Core licensing models that you run in a physical or virtual
OSE on a licensed server, you may temporarily run a backup instance in a physical or virtual OSE on a server dedicated to disaster recovery.
The license terms for the software and the following limitations apply to your use of software on a disaster recovery server:
The disaster recovery server can run only during the following exception periods:
For brief periods of disaster recovery testing within one week every 90 days
Around the time of a disaster, for a brief period, to assist in the transfer between the primary production server and the disaster
recovery server
In order to use the software under disaster recovery rights, you must comply with the following terms:
The disaster recovery server must not be running at any other times except as above.
The disaster recovery server may not be in the same cluster as the production server.
Windows Server licenses are not required for the disaster recovery server if the following conditions are met:
The Hyper-V role within Windows Server is used to replicate virtual OSEs from the production server at a primary site to a disaster
recovery server.
Use of the software on the disaster recovery server should comply with the license terms for the software.
Once the disaster recovery process is complete and the production server is recovered, the disaster recovery server must not be
running at any other times except those times allowed here.
January 15 Edition
Downgrade Rights
Under SPLA rules, Service Providers license the most current version and are entitled to apply downgrade rights to install
previous versions. There are no generally restrictions on prior versions however some specific rules come into play, particularly
for SQL. This extract covering downgrade rights is taken from Microsofts Service Provider Use Rights (SPUR):
Rights to Use Other Versions
License terms for products permit use of one or more copies or instances at a time. For all these products, for any permitted
copy or instance, you may create, store and run in place of the version licensed, a copy or instance of a:
prior version;
You may not use different versions of different components, such as server software and additional software, unless the
license terms for the product expressly permit you to do so.
Internal Use
Internal use of software licensed by a Service Provider under SPLA is permitted, however there is a 50% rule that must be
adhered to on a product-by-product basis. The full conditions associated with Internal Use are covered in the following extract
from the Service Provider License Agreement (SPLA) between Microsoft and Service Provider. Note Customer = Service
Provider:
January 15 Edition
Windows Desktop OS
Windows Desktop OS cannot be offered in a virtual environment. Service Providers can offer desktop software in a
Managed/Rental PC environment. Service Provider must install the desktop software on laptops that they own and lease the
hardware and software to the end customers. The laptops must have an OEM version of Windows and then the Service
Providers must report Windows SALs under SPLA.
January 15 Edition