MS Server licensing RRS feed

  • Question

  • First, I have no idea if this is the right forum or right category,  so I guessed. 

    Here's one licensing scenario I am trying to find out if it is legal or not, so far even our authorized rep can't tell me if it is or is not.  On the current host, which runs 2012 R2, there are 2 2012 R2 guests and one fully licensed 2016 guest.  We need to upgrade one of the 2012 R2 VMs to 2016. So is is that legal?  In the end we'd have the host at 2012 R2, one guest at 2012 R2, and two 2016 VMs.  Or, would I be facing having to upgrade the host to 2016 (getting raked for another full license in the process)? Any advice is greatly appreciated. Thanks.

    Tuesday, May 7, 2019 3:44 PM

All replies

  • This forum is for Virtual Server 2005, nothing to do with licensing.  I don't believe that there are forums for licensing, since the forums are mainly user to user.

    Windows Server 2012 standard grants you two licenses for OSE (VMs) assuming you are not running any roles other than Hyper-V on the host (hardware) installation.

    By "fully licensed 2016 guest" what do you mean?  A Windows Server 2016 standard license has been used?

    If so, you can "assign" this license to the physical server (no need to actually install it on the physical server) and have the benefit of the 2 OSE licenses that it offers.  This assumes it meets the core licensing requirements, which require a minimum number of cores per the server and also that all cores are fully licensed for the physical server.  You can continue to assign licenses to the physical server and gain the benefit of two OSEs with each additional Windows Server 2012/2016/2019 Standard license. 

    2016 Ref: 

    2102 Ref:

    TLDR: assuming your 2016 license is correct for #ofcores and not used anywhere else except this server, you are legally licensed for two 2012 VMs and two 2016 VMs, as you have one 2012 Std and one 2016 std license assigned.  

    However, "someone told me on the forums that my licenses are legal" won't mean anything to Microsoft in an audit.  You should contact Microsoft Licensing if you want verification.

    Tuesday, May 7, 2019 5:24 PM