转自:http://www.aidanfinn.com/?p=13090

Remember that Microsoft licenses its servers at the physical level, not the VM level, so no matter what hypervisor you are using, the licensing is exactly the same.

I am not answering any more questions on this post - to be honest, there have been too many for me to have the time to deal with them. Don’t bother asking – I’ll ignore/delete it.  My recommendations are:

  1. Re-read this post if you do not understand it after the first or second reads. To be honest, most of the questions have been from people who are just trying to make things complicated. Just license the hosts for the maximum number of Windows Server VMs that can ever run on that host, even for 1 second. It is that simple!
  2. Ask your LAR/distributor/reseller – that’s their job and that’s why you pay them

This post follows my dissertation on Windows Server 2012 licensing, which is essential reading before proceeding with this post.

I’m putting Hyper-V aside for just a few minutes to talk about how you will license virtualisation of Windows Server 2012 in virtual machines no matter what virtualisation you use, be it vSphere, Hyper-V, XenServer, or whatever tickles your fancy.  BTW, the counting here also applies to:

  • System Center 2012
  • Core Infrastructure Suite (CIS)
  • Enrolment for Core Infrastructure (ECI – minimum of 25 hosts)

Please read this post s-l-o-w-l-y and let it sink in.  Then read it again.  If you have been eating bowls full of VMware FUD then read it a third time – slowly.

FAQ

  • VOSE or virtual operating system environment is a licensing term for virtual machine (VM).  It is used when talking about licensing a VM for Windows Server.
  • When you buy a license for virtualisation you legally buy and assign it to hardware, not to VMs.  The virtualisation rights of Windows Server licenses the VMs on the licensed host for Windows Server.
  • There is no mobility with OEM.
  • You can move a volume license and it’s virtualisation rights once every 90 days.  If you want to use HA (clustering), Live Migration/vMotion, DRS/Dynamic Optimization/PRO, then you need sufficient virtualisation rights on each host to support the maximum number of VMs that is possible on that host, even for 1 second.
  • You cannot split a license or it’s virtualisation rights across hosts.
  • Virtualisation rights are 2 VOSEs for a host licensed by Windows Server 2012 Standard and unlimited VOSEs for a host licensed for Windows Server 2012 Datacenter.
  • Virtualisation rights covers the host for the assigned edition of Windows Server 2012 and lower versions/editions of Windows Server.  It does not include Windows 8/7/Vista.
  • You can assign more than 1 license to a host

In other words, you license a host for the maximum number of Windows Server VMs that it could host.

1 Host, 1 CPU, 2 VMs

Here you want to run a single host that has 1 CPU.  The host will run 2 Windows Server virtual machines.  You will assign a single Windows Server 2012 license to this host.  The license covers 2 CPUs (there is only 1) and provides virtualisation rights for 2 virtual operating system environments (VOSEs).  In other words, you get rights to install Windows Server 2012 Standard (or previous versions) in 2 VMs on this host.

1 Host, 2 CPUs, 4 VMs

The Standard edition covers 2 VOSEs, but the customer wants 4 VMs running Windows Server Standard 2008 R2.  A single copy of WS2012 Standard will not suffice.  2 copies are bought to provide the 4 (2 * 2 VOSEs) VMs with licensing.

1 Host, 2 CPUs, 10 VMs

There are two options; do you go with the Standard or Datacenter editions of Windows Server 2012?

The Standard edition covers 2 VOSEs, but the customer wants 10 VMs running Windows Server Standard 2008 R2. A single copy of WS2012 Standard will not suffice. 5 copies are bought to provide the 10 (5 * 2 VOSEs) VMs with licensing.  Based on USA Open NL pricing the licensing of these VMs will cost $882 * 5 = $4,410.

The Datacenter edition of WS2012 gives unlimited VOSEs and covers 2 CPUs in the host.  This solution will require a single Windows Server 2012 Datacenter license which will cost $4,809.

Decision: If you will not go over 10 VMs on this host then Windows Server 2012 Standard edition is the way to go.  If you estimate that there is a good chance of the VM numbers growing then spend an extra $399 and pick up the easier to account-for Windows Server 2012 Datacenter with it’s unlimited VOSE rights.

10 is the magic number using USA Open NL pricing. Once you reach 10 VOSEs on a 1 or 2 CPU host, you need to consider the Datacenter edition because it is cheaper once you hit 11 VOSEs.

1 Host, 4 CPUs, 4 VMs

It’s an unusual configuration but a valid one for the demonstration.  The WS2012 Standard/Datacenter SKUs cover 2 CPUs each.  In this case there are 4 CPUs.  This will require 2 copies of Windows Server 2012 Standard, which also covers the 4 VMs.

Let’s pretend that 300 VMs will run on this host with 4 physical CPUs.  Then we would assign 2 copies of Windows Server Datacenter on it.  2 copies will cover 2 CPUs each (4 CPUs) and unlimited VOSEs.

That Host with 320 Logical Processors – 10 CPUs with 16 Cores with Hyperthreading

The maximum specification for Windows Server 2012 Hyper-V is 320 logical processors in the host.  That could be 10 Intel CPUs, each with 16 cores, with Hyperthreading enabled.  We don’t count cores or logical processors when we license.  We count CPUs, sockets, or plain old processors – pick the term you prefer.  There are 10 CPUs/sockets/processors in this server.  That requires 5 copies of either Windows Server 2012 Standard or Datacenter, depending on the required number of VOSEs.

Clusters

Let’s move on to the clusters, where people usually get things wrong because they don’t understand (or don’t want to understand) the mobility rights.  VOSEs licensed by OEM cannot move.  VOSEs licensed by VL can move once every 90 days.  The correct solution is to license each host for the maximum number of VOSEs that it can have for even one second.  And when I say “correct” I mean legal.  Software Asset Management professionals (auditors) are not stupid and the “tricks” I hear people proposing are neither original or unknown to these auditors.

Reminder: This applies even to you non-Hyper-V folks.

2 Hosts, 1 CPU each, 4 VMs

Don’t get fooled!  This is not one host with 3 VMs and 1 host with 1 VM.  This is 2 hosts, each of which can have up to 4 VMs.  In the past we would have used Enterprise edition on each host.  That has been replaced by Windows Server 2012 Standard edition, that now has all the features and scalability of the Datacenter edition.

Take each host and size it for 4 VOSEs.  That means we need to assign 2 copies of Windows Server 2012 Standard edition to each host.  That’s 4 copies of WS2012 Standard.

2 Hosts, 2 CPUs each, 10 VMs

10 VMs with 2 hosts means that it is possible to have all 10 VMs on a single host.  You have two options to license each host for up to 10 VOSEs.

Firstly you could license each of the hosts with 5 copies of Windows Server 2012 Standard.  That will give you 10 (5 * 2) VOSEs.  This requires 10 (5 * 2 hosts ) copies of Standard at a cost of $8,820 using USA Open NL.

Alternatively you could license each host with 1 copy of Windows Server 2012 Datacenter, at a cost of $9,618.  The extra $798 will allow you to burst beyond 10 VOSEs to unlimited VOSEs.  Switching to licensing hosts using the Datacenter edition means we don’t have to count VOSEs and we have unrestricted mobility between hosts.

2 Hosts, 2 CPUs each, 20 VMs

We have exceed the magic number of 10, and now it is cheaper to license with the Datacenter edition with it’s unlimited VOSEs per host.  Each host has 2 CPUs, so each host requires 1 copy of Datacenter.  There are 2 hosts so we require 2 copies of Windows Server 2012 Datacenter.

You could add more hosts to this cluster and each could have unlimited VMs.  As long as the hosts have 1 or 2 CPUs each, each additional host requires only 1 copy of Windows Server 2012 Datacenter to license it for unlimited installs of Windows Server for the VMs on that host.

Lots of Hosts, Lots of VMs, 4 CPUs per Host

The magic number of 10 VOSEs is a dot in the rear view mirror.  We now have lots of hosts with lots of VMs flying all over the place.  Each host has 4 CPUs.  To license the VOSEs on each host, we will require licensing for 4 CPUs.  This will require 2 copies of Windows Server 2012 Datacenter per host, each covering 2 CPUs.

Live Migration Outside the Cluster

And new for WS2012 thanks to Live Migration living outside the cluster: you must ensure that the destination host is adequately licensed for VOSEs to accommodate the new VM. If this is an infrequent move then you could avail of the VL 90 day mobility right to reassign a license, ensuring the the old host is sufficiently licensed for remaining VOSEs and physical CPUs.

Hyper-V Server 2012

Hyper-V Server has no virtualisation rights and includes no free licensing for VOSEs.  Therefore it is irrelevant in this conversation.

Economically Speaking – Why Hyper-V Makes Sense

If you buy Windows Server licensing for a host to license your VMs, then you are a tickbox (or PowerShell cmdlet) and a reboot away from having Hyper-V.  Buying another product is just more money spent.  And let’s be honest,Windows Server 2012 Hyper-V is not what you might have used/looked at before.

Technorati Tags: Windows Server 2012,Virtualisation,Licensing,Hyper-V,Xen,VMware

Copyright Warning

This blog post is the property of Aidan Finn (@joe_elway / http://www.aidanfinn.com) and may not be reused in any manner without prior consent of Aidan Finn. You may quote one paragraph from this blog post if you link to the original blog post.

Related posts:

  1. Windows Server 2012 Licensing In Detail
  2. Reminder of Windows Server 2012 and Windows 8 Licensing For VL Purchases
  3. Volume Licensing for Windows Server 2012 And Windows 8 Are Now Available
  4. How To Buy Windows 8 For Different Scenarios
  5. Windows Server 2012–Won’t Somebody Think Of The CALs?!?!

windows 2012授权模型的更多相关文章

  1. 在工作组的环境中配置Windows 2012 R2的远程桌面服务

    在工作组的环境中配置Windows 2012 R2的远程桌面服务 How to configure Remote Desktop Service in Windows 2012 R2 workgrou ...

  2. windows 2012 r2下安装sharepoint 2013错误解决

    日前,我在安装sharepoint 2013时,需要预部署一些软件,我们知道运行产品准备工具“prerequisiteinstaller”后就可以自动下载安装配置这些软件,但是使用系统为windows ...

  3. [转载]Windows 2012 R2安装SharePoint 2013 手动安装工具软件

    之前介绍过在window 2012中安装SharePoint 2013,这次,借着SharePoint 2013 sp1补丁发布之际,介绍下在window 2012 r2中安装SharePoint 2 ...

  4. Windows 2012 R2中安装SharePoint 2013 sp1参考

    之前介绍过在window 2012中安装SharePoint 2013,这次,借着SharePoint 2013 sp1补丁发布之际,介绍下在window 2012 r2中安装SharePoint 2 ...

  5. Windows Phone 执行模型概述

    Windows Phone 执行模型控制在 Windows Phone 上运行的应用程序的生命周期,该过程从启动应用程序开始,直至应用程序终止. 该执行模型旨在始终为最终用户提供快速响应的体验.为此, ...

  6. 网件无线网卡在windows 2012支持问题

    网件的无线网卡的驱动是支持windows 8.1的,但是安装了驱动后,却没法启动网卡.网上搜索后发现,service里面网件有一进程没法启动:而2012年忘记官方论坛技术支持答复咨询居然说,网件驱动不 ...

  7. windows 2012 服务器打开ping端口,开通远程连接

    windows 2012 服务器打开ping端口,开通远程桌面连接 控制面板->系统与安全->高级防火墙->入站规则 找到:windows 远程桌面 (http in )  右键启用 ...

  8. SVN二次开发——让SVN、TSVN(TortoiseSVN)支持windows的访问控制模型、NTFS ADS(可选数据流、NTFS的安全属性)

    SVN二次开发 ——让SVN.TSVN(TortoiseSVN)支持windows的访问控制模型.NTFS ADS (可选数据流.NTFS的安全属性) SVN secondary developmen ...

  9. jenkins集群加入Windows 2012 server作为slave

    必须安装.net framework 3.5, 參考: http://technet.microsoft.com/en-us/library/dn482071.aspx 不要在windows 2012 ...

随机推荐

  1. springboot—spring aop 实现系统操作日志记录存储到数据库

    原文:https://www.jianshu.com/p/d0bbdf1974bd 采用方案: 使用spring 的 aop 技术切到自定义注解上,针对不同注解标志进行参数解析,记录日志 缺点是要针对 ...

  2. 为什么不能用memcached存储Session

    Memcached创建者Dormando很早就写过两篇文章[1][2], 告诫开发人员不要用memcached存储Session.他在第一篇文章中给出的理由大致是说,如果用memcached存储Ses ...

  3. SharePoint 如何导出部署的场解决方案

    前言 当我们在做服务器场迁移或者备份的时候,经常需要场中部署的解决方案包,然而,很多时候,我们无法找到这些解决方案包.很多解决方案在部署的时候,可能就已经删掉了,很多解决方案由于时间久远,我们不知道哪 ...

  4. insert into select 多个表

    INSERT INTO user_auth(userid, auth_plane_id) select user.user_id AS userid, plane.id AS auth_plane_i ...

  5. float浮点数的四舍五入

    瑞生网http://www.rationmcu.com版权所有 前几天,有个小伙伴在做实验过程中,发现了一个奇怪的现象,这个现象就是… 他在用printf输出浮点数的时候,想把数据保留到小数点后的两位 ...

  6. java-nio之zero copy深入分析

    对于所有的io操作,底层一定是调用操作系统的api来进行读写.受限于不同的操作系统,操作方式一定是有差异的.以下read和write操作,可以看做服务器从磁盘硬件上读取文件数据,然后通过socket发 ...

  7. C++11 std::unique_lock与std::lock_guard区别及多线程应用实例

    C++多线程编程中通常会对共享的数据进行写保护,以防止多线程在对共享数据成员进行读写时造成资源争抢导致程序出现未定义的行为.通常的做法是在修改共享数据成员的时候进行加锁--mutex.在使用锁的时候通 ...

  8. chain33 区块链开发框架诞生记

    chain33 诞生记 很多年没有写博客了,应该说,自从2013年开始玩比特币,就没有写过了.这5年来,做了很多事情,也见了很多以前做梦都没有想到过都事情.我做的最开心的事情,也是觉得最有意义的事情, ...

  9. 关于html+ashx开发中几个问题的解决方法 (转)

    在跟html+ashx打交道的园友们肯定会发现,这种模式虽然优美,但在开发中会遇到一些难处理的地方.我也不例外,下面是自己在实际开发中总结出来的几条经验,希望跟大家分享,更希望得到大家的建议和更好的解 ...

  10. C# MemCached分布式缓存

    using System; using System.Collections.Generic; using System.Text; using Memcached.ClientLibrary; us ...