This document provides an overview of Microsoft volume licensing for various products, including Windows Server 2012 R2, Remote Desktop Services, virtual desktop infrastructure (VDI), and desktop applications. It discusses licensing models, rights and restrictions for each product. For Windows Server, it explains processor licensing and the types of client access licenses (CALs). It also covers licensing requirements for using desktop applications remotely in a virtual environment, including ensuring compatibility of products, components, languages and versions between the accessing device and virtual instance.

1. Witek Jaworek
Senior Licensing Manager
witoldja@microsoft.com

2.  Omawiamy licencjonowanie w umowach
wolumenowych
• EA, EAS
• Select Plus, Select, MPSA,
• Open, Open Value, OVS
Zakres prezentacji
2
 Nie omawiamy licencjonowania w innych umowach, np:
• OEM
• FPP (box, „paczka”)
• ISV Royalty

3.  Prawa do Używania Produktów (Product Use Rights)
 Lista Produktów (Product List)
http://www.microsoft.com/licensing/products/products
.aspx#tab=2
Podstawowe dokumenty
3

4.  Licensing Briefs
http://www.microsoft.com/licensing/about-
licensing/volume-licensing-briefs.aspx#tab=4
Pomocne informacje
4

5. Windows Srv 2012R2
5
Licensing model:
Processor/CAL (Processor License + CAL + Optional External Connector

6.  You must assign each license to a single Server.
 All physical processors need to be licensed.
 Each license covers up to two physical processors.
 You may run the server software in one physical OSE
and in up to two virtual OSEs for each license you
assign.
 If you run all of the permitted instances the instance
in the physical OSE can only be used to manage the
virtual OSEs.
Windows Srv 2012R2 Standard
6

7.  You must assign each license to a single Server.
 All physical processors need to be licensed.
 Each license covers up to two physical processors.
 You may run the server software in any number of
OSEs, both physical and virtual.
Windows Srv 2012R2 DataCenter
7

8.  You may Run an Instance of Windows Server
Enterprise, Standard, Essentials, Web, HPC or any
earlier version of the qualifying editions in place of
Standard / Datacenter in any of the OSEs.
Down-edition rights
8

9.  You must assign each CAL to a user or device, as
appropriate, and each External Connector License to a
Licensed Server.
 CALs or External Connector Licenses are required for access
to server software.
 CALs and External Connector Licenses permit access to the
corresponding version (including earlier versions used under
downgrade rights) or earlier versions of server software.
 CALs are not required to access server software running a
Web or HPC Workload.
Access Licenses (CAL)
9

10.  Win Srv Device CAL: Permits one device (used by any user)
to use Windows Srv functionalities on any of your servers.
 Win Srv User CAL: Permits one user (using any device) to
use Windows Srv functionalities on any of your servers.
 Win Srv External Connector: Permits multiple external
users to access a single Windows server. If you have
multiple servers, you need multiple external connectors.
Types of access licenses:
10

11.  You may choose to combine Win Srv Device CALs and
Win Srv User CALs simultaneously with the server
software.
 You may permanently reassign your device CAL from
one device to another or your user CAL from one user
to another.
 You may temporarily reassign your device CAL to a
loaner device while the first device is out of service, or
reassign your user CAL to a temporary worker while
the worker is absent.
Use of access licenses:
11

12. 12

13. Remote Desktop Services
(formerly known as Terminal Services)
13
Licensing model:
Processor/CAL (Processor License + CAL + Optional External Connector

14. Microsoft licensing policies for Windows Server Remote
Desktop Services require that, in addition to a Windows
Srv CAL, you must acquire a Windows Server 2012 RDS
CAL for each user or device that
 directly or indirectly accesses any of the RDS
functionality
and/or
 directly or indirectly accesses the server software to
interact with a graphical user interface (GUI) using RDS
functionality or any other third-party technology.
RDS Technologies Requiring RDS CALs
14

15.  RDS Device CAL: Permits one device (used by any user) to
use Remote Desktop Services functionality on any of your
servers.
 RDS User CAL: Permits one user (using any device) to use
Remote Desktop Services functionality on any of your
servers.
 RDS External Connector: Permits multiple external users to
access a single Remote Desktop server. If you have
multiple servers, you need multiple external connectors in
addition to any required Windows Server External
Connectors.
Types of access licenses:
15

16.  You may choose to combine RDS Device CALs and
RDS User CALs simultaneously with the server
software.
 You may permanently reassign your device CAL from
one device to another or your user CAL from one user
to another.
 You may temporarily reassign your device CAL to a
loaner device while the first device is out of service, or
reassign your user CAL to a temporary worker while
the worker is absent.
Use of access licenses:
16

17. Licensing Windows Desktop OS for use with
VM
17
Licensing model:
Per Copy per Device / Per Copy per User

18. Windows VDA Rights allow for a licensed device or
user to access virtual Windows desktops either
remotely and/or locally, depending on how the device
or user is licensed. You can license devices or users for
Windows VDA rights in the following ways:
 License devices with Windows Software Assurance or
Windows VDA subscription on a per device basis.
 License users with Windows Software Assurance or
Windows VDA subscription on a per user basis.
Virtual Desktop Access (VDA)
18

19. 19
Windows
Enterprise SA
Windows
VDA
Per
Device
Per
User
Per
Device
Per
User
Any user of a Licensed Device, or any device used
by a Licensed User; may remotely access up to
four Instances of the Software Running in Virtual
OSEs or one Instance of the Software Running in
one Physical OSE on (a) device(s) in your
datacenter.

20.  Windows OEM licenses do not permit remote access
to a Windows virtual machine running in a data
center
Windows OEM doesn’t have VDA rights
20

21. 21

22. Licensing Desktop Application for use with
virtual environment
22
Licensing model:
Per Device

23.  You must assign each license to a single device.
 You may install the software on the Licensed Device
and a network Server.
 You may use any number of copies of the software.
 Each license permits only one user to access and use
the software at a time.
General Terms
23

24. Use of Microsoft desktop applications in a virtual
environment requires that the suite/edition, components,
language, and version of the license acquired for the
desktops from which the desktop application is remotely
accessed matches that of the copy of the application being
accessed. For example:
 Product (or suite): Microsoft Office Standard 2013 and
Microsoft Office Professional Plus 2013 are different
products (or suites). A desktop licensed for Office Standard
2013 may not remotely access and use Office Professional
Plus 2013.
Compatibility requirements
24

25.  Components: A license for a suite (for example, a
Microsoft Office suite) for the accessing desktop must have
exactly the same components as the copy of the Microsoft
Office suite being remotely accessed.
 Language: The English/multilanguage version of the
Microsoft Office suite may not be accessed remotely from
a desktop, which is licensed for a single language version
of the Microsoft Office suite. Likewise, remote access to a
licensed copy of Microsoft Office Multi-Language Pack
2013 requires the accessing desktop be licensed for the
Office Multi-Language Pack 2013.
Compatibility requirements, cont.
25

26.  Version: Microsoft Office 2013 and Microsoft Office
2010 are different versions. You may not remotely
access Microsoft Office 2013 from a desktop that is
licensed for Microsoft Office 2010.
Microsoft Office retail (FPP) and original equipment
manufacturer (OEM) products released in 2007 or later
do not permit network use.
Compatibility requirements, cont.
26

27. 27

28. Questions?
28

29. Dziękuję
29