Demystifying Windows Server 2016 Licensing
Demystifying Windows Server 2016 Licensing
in a Virtual Environment
info@altaro.com
info@altaro.com || www.altaro.com
www.altaro.com
Agenda
1 Introduction
2 Licensing Presentation
3 Example Scenarios
5 Q&A
6 Conclusion
altaro.com/vm-backup
Software licensing is a legal matter, not a technical concern. The author and presenter of
this work is not a lawyer and no lawyers were consulted when writing this work. Its
contents are intended to be a guideline to aid in comprehension of the concepts of a
specific licensing detail. It does not constitute legal advice or interpretation. Neither the
author and presenter nor Altaro Software, Ltd. are offering legal advice and this work
cannot be construed as such. We cannot be held responsible for any negative outcomes
of the usage of any of the contents, whether it is through an error on our part or a
misunderstanding on yours. For official answers, contact Microsoft Licensing or check
with your reseller. Authorized resellers should have someone on staff that can
authoritatively answer licensing questions. There are very steep fines and bounties
associated with licensing violations. It is worth your time to get official answers.
The most detailed publicly-available material that Microsoft publishes on the subject is
the Product Use Rights document. The clearest publicly-available material that Microsoft
publishes is the Windows Server 2016 Licensing Datasheet. The license agreement that
is included with your software is the only legally binding document. If your compliance is
ever tested in court, the licensing agreement is the only applicable document.
History of Hyper-V
High performance live migration High performance auto tiered storage spaces Hyper-V over SMB
(compression/RDMA)
Write back cache with spaces Hyper-V over Spaces & ReFS
Zero downtime upgrades
Storage QoS 64 VP, 1 TB VMs
Automatic VM Activation
Shared VHDX for guest clustering SR-IOV for 10+GB networking
Live VM export
VHDX online resize 64TB VHDX
Guest backup improvements
Storage deduplication with live VMs for VDI Hyper-V Replica
Enhanced VMConnect
Hyper-V Recovery Manager (Microsoft Azure Network Virtualization
Dynamic memory host balancing Site recovery)
USB redirection over RemoteFX vGPU
First class Linux support – Dynamic memory, file Azure Backup
system consistent host based backup Hot add/remove of storage
Inbox multi-tenant site-to-site VPN gateway for
RemoteFX over WAN physical & virtual networks VHDX resiliency
Generation 2 Virtual Machines Protected VM Networks/Virtual RSS Dynamic & differencing VHDX performance
improvements
Secure boot in a VM Enhanced LBFO performance with NIC teaming
384 LP, 4TB physical system
User defined meta data for VHDX Hyper-V Extensible Switch
2+ Million IOPS to a single VM
PowerShell for all Hyper-V operations 4K Sector support
Resource Pools
Hyper-V Metrics
NUMA in a VM
Shared nothing live migration
1024 running VMs on a host
• Windows Server Standard edition comes with two virtualization rights. That doesn’t
mean that you need to purchase Datacenter edition if you want to run a third virtual
machine. One more Standard edition license will provide licensing for another two
virtual instances.
• Because licenses are always bound to a specific piece of hardware, this means that
you cannot use a single license set for multiple computers, even when they are in a
cluster. When a virtual machine moves from one host to another, the destination
host must already have an available license for that virtual machines’ operating
system.
• Consider a three node cluster with eight virtual machines. You’ll need to determine
the maximum number of active guests that every single node might ever possibly run,
and license each node accordingly. If any single node might run all eight virtual
machines, then every single node must either have four Standard edition licenses or
a single Datacenter edition license. If the nodes won’t run that many, then you can
license a smaller amount per host.
•
•
•
•
•
• 8 two-core packs will be the minimum required to license each physical server.
• The two-core pack for each edition is 1/8th the price of a two proc license for
corresponding 2012 R2 editions.
CBB2
WS 2016 Nano Server CBB1 Server with Desktop Experience and Server Core
WS 2012R2 LTSB
WS 2012 LTSB
Time
• A single license is applied to two CPU cores in the same physical host
• Each physical processor must have sufficient licenses to cover a minimum of eight
cores (four licenses). This is true even if the physical processor does not have eight
cores. More licenses might be required, depending on physical core count.
• Each physical host must be licensed as though it has at least two physical processors,
even if it has only one. This sets a hard minimum of 16 physical cores (8 licenses) for
any single system.
• Windows Server Standard licenses provide for one pOSE and two vOSEs on a licensed
core pair.
• Windows Server Datacenter licenses provide for one pOSE and unlimited vOSEs on a
licensed core pair.
(number of physical cores / 2 rounded up) * (Standard Edition vOSEs / 2) = licenses (at least 8)
Datacenter Edition
Datacenter Edition: (number of physical cores / 2 rounded up) = licenses (at least 8)
Host: Windows
Server 2016
4 cores Standard
+ 4 cores
= 8 cores
Guests: 2x
Windows
Server 2016
Standard
Host: Windows
Server 2016
4 cores Standard
+ 4 cores
= 8 cores
Guests: 3x
Windows
Server 2016
Standard
Host: Windows
Server 2016
6 cores Standard
+ 6 cores
= 12 cores
Guests: 3x
Windows
Server 2016
Standard
Guests: 3x
Windows
Server 2016
Standard
Guests: 50x
Windows
Server 2016
Datacenter
Guests: 50x
Windows
Server 2016
Datacenter
Guests: 56x
Linux
http://www.thomasmaurer.ch/2016
/08/microsofts-new-vmware-
migration-offer-for-windows-server-
2016/
• Virtual backup trusted by 30,000+ SMBs and 4,600+ IT Resellers and MSPs
• Outstanding Support
• Premium support offered as part of the package - Experts in Hyper-V and VMware
IT Reseller?
info@altaro.com
info@altaro.com || www.altaro.com
www.altaro.com