1. PowerPoint Presentation Sample WRITER: KIM STEFFENS DESIGNER: JENNIFER CHADWICK AGENCY: YESLER CLIENT: MICROSOFT | LICENSING TRAINING

2. LICENSING TRAINING

3. Why Is Correct Licensing Important?

4. Significant Revenue Opportunity
At least $131 million per year in revenue uplift1
Potential revenue increase of 90 percent1
Mkt Current $/yr
Mkt Required $/yr
$147M
$278M
90%
“There is a lot of revenue to be captured if someone wants to go after it.”
– Microsoft Field Sales Rep
~$131M/yr
[Adam] I’ll get the source. I’m not sure if it’s available on a share somewhere we could reference…
1Crimson Consulting, insert source info here

5. What’s Happening in the Field?
Account teams report nearly universal mislicensing in virtualized environments.
“I would say that 99 percent of customers that use virtualization don’t have the Windows Server 2008 Datacenter SKU, so they can’t run unlimited virtual machines.”
“Mislicensing exists at the operating system level (more virtual machines than licenses) and hardware level (not all processors are licensed), and virtual machine mobility restrictions are violated.”
“If I had to guess, out of approximately 50 accounts I had last year, 80 percent or more are not licensed properly.”
“In 100 percent of the cases where customers have virtualized they are not properly licensed.”

6. What’s Happening for Partners?
Partners report general confusion about virtualization licensing, regardless of the license type.
Windows Server licensing costs for setting up a failover server make it cost-prohibitive, and many customers are likely to be out of compliance.
Software Assurance (SA) does not address concerns regarding OEM licensing portability.
Licensing types are seldom mixed, for example not combining a Windows Server OEM operating system license and a Microsoft SQL Server volume license.

7. Why Is Mislicensing Happening?
Lack of clear, consistent communication from Microsoft
WHAT WE’RE DOING TO HELP:
Clear, consistent communication from Microsoft
All consolidated licensing and pricing information can be found on the Windows Server website.
For licensing information, go to: download.microsoft.com/download/e/e/c/eecf5d44-9a88-43d8-afdb- d2ab82be035c/R2_License_Guide-ONLINE.pdf
For pricing information, go to:

8. Why Is Mislicensing Happening?
Complex licensing models
WHAT WE’RE DOING TO HELP:
Simplified licensing models
Easy, unlimited virtualization with Windows Server 2008 R2 Datacenter Editions
Synchronized license rights across operating system environment, application, and management server versions:
Standard (least flexible, limited)
Enterprise (flexible but limited)
Datacenter (flexible unlimited)
Same rules for all virtualization platforms

9. Why Is Mislicensing Happening?
Lack of tools to support licensing compliance
Lack of communication between Procurement Manager and IT Pro
WHAT WE’RE DOING TO HELP:
Tools to support licensing compliance
Microsoft provides free Microsoft Assessment and Planning (MAP) Toolkit.

10. Why Is Mislicensing Happening?
Growth of virtual machine density outpacing licensing
Complex mobility rights for virtual machines
WHAT WE’RE DOING TO HELP:
Windows Server 2008 R2 Datacenter Edition provides unlimited ability to move across densities and mobilities.

11. Common Licensing Mistakes
Underlicensing
Virtualizing above the number of allowed virtual instances
Example: Using more than four virtual machines with Windows Server 2008 R2 Enterprise Edition
Assuming (incorrectly) that Microsoft Service Provider Licensing Agreement (SPLA) allows Virtual Desktop Infrastructure (VDI) for hosters
General underlicensing of servers by operating system environment in live migration scenarios
Overlicensing
General overlicensing due to past purchases of Windows Server 2008 R2 Standard and Enterprise Edition licenses

12. Licensing Basics
Let’s start off with an overview of the key components that make up basic Windows Server 2008 R2 licensing scenarios.

13. Licensing Basics Correct licensing depends on Servers Processors
Users or devices
Instances of software

14. Licensing Basics: Servers
7/4/2019 5:55 AM
Licensing Basics: Servers
Physical Servers 
Traditional server devices
Rack-mounted servers & blades
Hard-partitioned system (seen here with four partitions)
Server “A”
Server “B”
Server “A”
Server “B”
Server “C”
Server “A”
Server “B”
Server “C”
Server “D”
A server is a physical hardware system capable of running server operating system software.
Blades and hard partitions are considered to be separate physical hardware systems, and therefore separate servers.
© 2010 Microsoft Corporation. All rights reserved. MICROSOFT CONFIDENTIAL.
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.

15. Licensing Basics: Servers
7/4/2019 5:55 AM
Licensing Basics: Servers
Virtual Machines (VMs)
Multiple, self-contained operating system environments that coexist on the same physical server using a software layer (“hypervisor”) to provide virtualization
Underlying physical server resources are shared among different virtual machines, each running its own operating system. VM VM VM VM
Hypervisor
© 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
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.

16. Licensing Basics: Inside the Server
Microsoft Operating System Environments
Virtual operating system environment (VOSE) or virtual machines (VMs)
Operating system configured to run on a virtual (or otherwise emulated) hardware system
Physical operating system environment (POSE)
Operating system configured to run directly on a physical hardware system
Includes operating system instances used to run hardware virtualization software or to provide hardware virtualization services
Virtual Machine
Virtual Machine VM VM
Server Software
Server Software
Operating System
Operating System
Virtual Processor
Virtual Processor
An instance is an installed copy of software.
Hypervisor
POSE
Server Software
Operating System
Processors

17. Licensing Basics: Types of Licenses
Windows Server License – Physical Server
One physical server running Windows Server 2008 R2 Standard or Enterprise = one license
One CPU running Windows Server 2008 R2 Datacenter = one license
Windows Server Client Access Licenses (CAL)
User CAL 
One user who accesses the server = one CAL
Device CAL 
One device that accesses the server = one CAL
Remote Desktop Services
One user = one CAL
Rights Management Services
With the User CAL, you purchase a CAL for every user who accesses the server to use services such as file storage or printing, regardless of the number of devices they use for that access.
Purchasing a User CAL might make sense if employees need to have roaming access to the corporate network using multiple devices, or from unknown devices, or if the company simply has more devices than users in the organization.
An external connector is an external user such as a business partner, contractor, or customer.
If you want external users to have access to your network, you can either acquire CALs for each external user, or acquire EC licenses for each server that will be accessed by these external users.
External Connector (EC) License
One server accessed by external users = one EC license

18. Licensing Basics: Types of Licenses
Windows Server License – Virtual Machine
One VM running Windows Server 2008 R2 = one license
CALs are required to access instances of Windows Server 2008 R2 running on VMs.
Customers should check application software licensing for instances running on VMs.
Product
Licensing Model
Instances
per License
Comments
Web/SBS Standard
Server
1 POSE or 1 VM
POSE or VOSE
Standard Edition
Server / CAL
1 POSE and 1 VM
POSE can be used only to handle virtualization
Enterprise Edition
1 POSE and 4 VMs
Datacenter Edition
Processor/CAL
Unlimited
If all physical processors are licensed
SBS Premium Edition
2 POSE and 2 VMs
Web and SBS Standard Editions allow you to run only one instance of the software, so you need one license for each instance, physical or virtual.
Standard and Enterprise Editions allow you to run both one physical and one virtual instance at the same time using one license.
Datacenter Edition allows you to run an unlimited number of processors if all physical processors are licensed (with a minimum number of two processor licenses).

19. Licensing Basics: Understanding Mobility
Physical Operations System Environments (POSE)
OEM licenses are assigned permanently to the server they were purchased with.
Volume licenses can move
OEM
once every 90 days.

20. Licensing Basics: Understanding Mobility
Virtual Operating System Environments (VOSE)
VOSE or VMs can be moved at will.
There are no licensing constraints around how frequently they can be moved.
When moving an instance , customers must be sure that the destination location has an appropriate license to accept the VM.
Moving an instance of software from one server to another is not the same as reassigning a software license from one server to another. Moving an instance of software means to move the software bits from one server to another. Reassigning a software license means to assign that license to another server so that it becomes the server licensed to run that software.

21. Licensing Basics: Key Points
Correct licensing depends on
Servers:
Physical or virtual
Processors:
Based on number of processors, not number of cores
Users or devices
Client access licenses required per user or device
Instances of software
Each VM running Windows Server 2008 R2 requires a license.
CALs are required to access all instances of Windows Server 2008 R2 that are running on a VM.

22. Examples

23. How Many Incremental Licenses Are Needed?
Scenario: Move physical server to a virtual environment
Example: 4 Windows Server Standard licenses
on 1 physical server and 4 VMs
on 4 physical servers VM
Virtual Machine
Manage/Service VM
Parent
Applications
Child
POSE
POSE
POSE
POSE
Windows Server License
Windows Server License
Windows Server License
Windows Server License
No new licenses are needed.

24. How Many Incremental Licenses Are Needed?
Scenario: Move physical server to a virtual environment
3 Standard licenses and 1 Enterprise license
on 4 physical servers
on 2 physical servers and 6 VMs VM
Virtual Machine
Manage/Service VM
Parent
Applications
Child
POSE
POSE
POSE
POSE
1 Standard license = 1 VM
1 Enterprise license = 4 VMs
Windows Server License
Windows Server License
Windows Server License
Windows Server Enterprise License VM
Virtual Machine
Manage/Service VM
Parent
Applications
Child
Customer is over- licensed!
No new licenses are needed.
Windows Server Enterprise License
Windows Server Enterprise License
Windows Server Enterprise License

25. Licensing Windows Server 2008 R2 (Virtual)
A Windows Server license is required for each VM running Windows Server.
Windows Server CALs are required to access VMs running Windows Server.
Customers should check the license terms for the applications.
POSE
Windows Server License VM
Virtual Machine 1 VM
Virtual Machine 2 VM
Virtual Machine…
Windows Server License
Windows Server License
Windows Server License
Product License
Product License
Product License
Product License

26. Multi-Core Processors
Windows Server 2008 R2 Enterprise licensing does not impose limits on the number of cores that the physical server or the VM can use.
There are no limitations to how cores are distributed between VMs.
Windows Server License
Windows Server License
POSE VM
Virtual Machine 1 VM
Virtual Machine 2
Server Software
CORE
CORE
CORE

27. Understanding Use Rights and Virtualization Rights

28. Standard Edition: 1 POSE and 1 VM
Although the VMs are not tied to a physical server, the right to run the VM is.
A VM cannot be hosted on a server different from the server to which the license that provides the right to that VM was assigned.
1 Physical and 1 Virtual OSE (VM)
(Applications on the parent partition)
1 Physical and 1 Virtual OSE (VM)
(Applications on a child partition)
Parent
Child
POSE
POSE VM
Virtual Machine
Server Software VM
Virtual Machine VM
Virtual Machine
Server Software
Manage/Service VM
Parent  Partition - Logical hard drive division in the VM responsible for running the hypervisor layer and creating and managing child partitions
Child Partition - Responsible for running virtualized operating systems and applications
There can be only one parent partition on a given machine, but there can be as many child partitions as computing resources will support
Windows Server License
Windows Server License

29. Enterprise Edition: 1 POSE and 4 VMs
Although the VMs are not tied to a physical server, the rights to run the 4 VMs are .
A VM cannot be hosted on a server different from the server to which the license that provides the right to that VM was assigned. VM
Virtual Machine
Manage/Service VM
Parent
Server Software
Child
POSE
Windows Server Enterprise License
Windows Server Enterprise License
Windows Server Enterprise License
Windows Server Enterprise License
Windows Server Enterprise License
Windows Server Enterprise License
1 Enterprise license = 4 VMs

30. Datacenter Edition: 1 POSE and unlimited VMs
Although the VMs are not tied to a physical server, the rights to run the 4 VMs are.
A VM cannot be hosted on a server different from the server to which the license that provides the right to that VM was assigned. VM
Virtual Machine
Manage/Service VM
Parent
Server Software
Child
POSE
Datacenter
Edition
Datacenter
Edition
Datacenter Edition allows you to run an unlimited number of processors if all physical processors are licensed (with a minimum number of two processor licenses).
Datacenter
Edition
Datacenter
Edition
Datacenter
Edition
Datacenter
Edition
Datacenter
Edition
Datacenter
Edition
1 Datacenter license = Unlimited VM processors if all physical processors are licensed

31. Virtualization Rights for Server OSEs
Windows Server License – Virtual Machine
One VM running Windows Server 2008 R2 = one license
CALs are required to access instances of Windows Server 2008 R2 running on VMs.
Customers should check application software licensing for instances running on VMs.
Product
Licensing Model
Instances
per License
Comments
Web/SBS Standard
Server
1 POSE or 1 VM
POSE or VOSE
Standard Edition
Server / CAL
1 POSE and 1 VM
POSE can be used only to handle virtualization
Enterprise Edition
1 POSE and 4 VMs
Datacenter Edition
Processor/CAL
Unlimited
If all physical processors are licensed
SBS Premium Edition
2 POSE and 2 VMs
Web and SBS Standard Editions allow you to run only one instance of the software, so you need one license for each instance, physical or virtual.
Standard and Enterprise Editions allow you to run both one physical and one virtual instance at the same time using one license.
Datacenter Edition allows you to run an unlimited number of processors if all physical processors are licensed (with a minimum number of two processor licenses).

32. Licensing for Dynamic Data Center Environments

33. Licensing for Dynamic Data Center Environments
General Rule: License servers for peak capacity.
All servers in a cluster must be appropriately licensed for all running instances, regardless of whether the workload:
Always runs on a single server.
Runs in parallel on the server as a backup when the primary server fails.
Runs only if the primary server is down.
Is load balanced when the primary server has high use.
Only runs during maintenance and patching.

34. Licensing for Dynamic Data Center Environments
Two common scenarios for moving software instances:
Running a workload on a primary server and periodically moving it to a second server
Running the same workload simultaneously on two servers
These scenarios would cover
Hardware failure.
Load balancing.
Software versioning and security.
Downtime.
Disaster recovery.

35. Moving a Software Instance
Virtual Operating System Environments (VOSE)
VOSE or VMs can be moved at will.
There are no licensing constraints regarding how frequently VMs can be moved.
If Server A becomes overloaded, the VM that is running the software instance can be moved to Server B.
When moving an instance, customers must be sure that the destination location has an appropriate license to accept the VM. A
Moving an instance of software from one server to another is not the same as reassigning a software license from one server to another. Moving an instance of software means to move the software bits from one server to another. Reassigning a software license means to assign that license to another server so that it becomes the server licensed to run that software. B

36. Reassigning a Software License
Physical Operations System Environments (POSE)
Volume licenses can move
OEM licenses are assigned permanently to the server for which they were originally purchased.
Moving an instance of software from one server to another is not the same as reassigning a software license from one server to another. Moving an instance of software means to move the software bits from one server to another. Reassigning a software license means to assign that license to another server so that it becomes the server licensed to run that software.
OEM
once every 90 days.

37. 7/4/2019 5:55 AM
© 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
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.