Hyper-V Architecture 2016 and How To Install
-
@BBigford said in Hyper-V Architecture 2016 and How To Install:
The only exception to installing Hyper-V Core (that I see anyway) has been if a datacenter license is needed, since a datacenter license needs to be applied to a GUI.
There is no Hyper-V Core. Just Hyper-V. There is only one version. How does datacenter apply here? There is no DC license for Hyper-V.
-
@BBigford said in Hyper-V Architecture 2016 and How To Install:
But, less than 13 Standard licenses and not growing (or installing more non-Windows servers as they grow), definitely stick with Core and license servers individually as needed.
Of course you already knew all of that, just thought it was worth mentioning here.
I don't understand how the VM licensing relates to Hyper-V.
-
@scottalanmiller said in Hyper-V Architecture 2016 and How To Install:
@BBigford said in Hyper-V Architecture 2016 and How To Install:
But, less than 13 Standard licenses and not growing (or installing more non-Windows servers as they grow), definitely stick with Core and license servers individually as needed.
Of course you already knew all of that, just thought it was worth mentioning here.
I don't understand how the VM licensing relates to Hyper-V.
Just using an example where someone might have more than 13 licenses of Windows Server on a host, using more than that would make sense to have a Datacenter license because the cost of DC would be less than the accumulative cost of Standard on each WS. Since a DC license can't be applied Hyper-V Server/free/non-licensed/Core/non-GUI.
I was just saying it would make sense to have a GUI install in that case.
-
Wish I could upvote the original post more times :D.
-
@BBigford said in Hyper-V Architecture 2016 and How To Install:
@scottalanmiller said in Hyper-V Architecture 2016 and How To Install:
@BBigford said in Hyper-V Architecture 2016 and How To Install:
But, less than 13 Standard licenses and not growing (or installing more non-Windows servers as they grow), definitely stick with Core and license servers individually as needed.
Of course you already knew all of that, just thought it was worth mentioning here.
I don't understand how the VM licensing relates to Hyper-V.
Just using an example where someone might have more than 13 licenses of Windows Server on a host, using more than that would make sense to have a Datacenter license because the cost of DC would be less than the accumulative cost of Standard on each WS. Since a DC license can't be applied Hyper-V Server/free/non-licensed/Core/non-GUI.
I was just saying it would make sense to have a GUI install in that case.
Why would DC licensing not be able to be applied to Hyper-V? The license gets tied to the hardware, not to an individual desktop-workspace on the hardware. . .
-
@DustinB3403 said in Hyper-V Architecture 2016 and How To Install:
@BBigford said in Hyper-V Architecture 2016 and How To Install:
@scottalanmiller said in Hyper-V Architecture 2016 and How To Install:
@BBigford said in Hyper-V Architecture 2016 and How To Install:
But, less than 13 Standard licenses and not growing (or installing more non-Windows servers as they grow), definitely stick with Core and license servers individually as needed.
Of course you already knew all of that, just thought it was worth mentioning here.
I don't understand how the VM licensing relates to Hyper-V.
Just using an example where someone might have more than 13 licenses of Windows Server on a host, using more than that would make sense to have a Datacenter license because the cost of DC would be less than the accumulative cost of Standard on each WS. Since a DC license can't be applied Hyper-V Server/free/non-licensed/Core/non-GUI.
I was just saying it would make sense to have a GUI install in that case.
Why would DC licensing not be able to be applied to Hyper-V? The license gets tied to the hardware, not to an individual desktop-workspace on the hardware. . .
Because you can't install a license on Hyper-V Server. It isn't like a CAL where you just buy it for auditing, the OS will cease functioning if a license is not applied. You have to apply it somewhere to subsequently license the VMs on the host.
-
@BBigford said in Hyper-V Architecture 2016 and How To Install:
@DustinB3403 said in Hyper-V Architecture 2016 and How To Install:
@BBigford said in Hyper-V Architecture 2016 and How To Install:
@scottalanmiller said in Hyper-V Architecture 2016 and How To Install:
@BBigford said in Hyper-V Architecture 2016 and How To Install:
But, less than 13 Standard licenses and not growing (or installing more non-Windows servers as they grow), definitely stick with Core and license servers individually as needed.
Of course you already knew all of that, just thought it was worth mentioning here.
I don't understand how the VM licensing relates to Hyper-V.
Just using an example where someone might have more than 13 licenses of Windows Server on a host, using more than that would make sense to have a Datacenter license because the cost of DC would be less than the accumulative cost of Standard on each WS. Since a DC license can't be applied Hyper-V Server/free/non-licensed/Core/non-GUI.
I was just saying it would make sense to have a GUI install in that case.
Why would DC licensing not be able to be applied to Hyper-V? The license gets tied to the hardware, not to an individual desktop-workspace on the hardware. . .
Because you can't install a license on Hyper-V Server. It isn't like a CAL where you just buy it for auditing, the OS will cease functioning if a license is not applied. You have to apply it somewhere to subsequently license the VMs on the host.
I'd have to double check on that as I don't think it matters if its a VM or a bare metal install.
-
@DustinB3403 said in Hyper-V Architecture 2016 and How To Install:
@BBigford said in Hyper-V Architecture 2016 and How To Install:
@DustinB3403 said in Hyper-V Architecture 2016 and How To Install:
@BBigford said in Hyper-V Architecture 2016 and How To Install:
@scottalanmiller said in Hyper-V Architecture 2016 and How To Install:
@BBigford said in Hyper-V Architecture 2016 and How To Install:
But, less than 13 Standard licenses and not growing (or installing more non-Windows servers as they grow), definitely stick with Core and license servers individually as needed.
Of course you already knew all of that, just thought it was worth mentioning here.
I don't understand how the VM licensing relates to Hyper-V.
Just using an example where someone might have more than 13 licenses of Windows Server on a host, using more than that would make sense to have a Datacenter license because the cost of DC would be less than the accumulative cost of Standard on each WS. Since a DC license can't be applied Hyper-V Server/free/non-licensed/Core/non-GUI.
I was just saying it would make sense to have a GUI install in that case.
Why would DC licensing not be able to be applied to Hyper-V? The license gets tied to the hardware, not to an individual desktop-workspace on the hardware. . .
Because you can't install a license on Hyper-V Server. It isn't like a CAL where you just buy it for auditing, the OS will cease functioning if a license is not applied. You have to apply it somewhere to subsequently license the VMs on the host.
I'd have to double check on that as I don't think it matters if its a VM or a bare metal install.
Doesn't matter if what is a VM? The VMs have to be licensed. If you don't apply a license to the host of the VMs, then there is the issue.
Didn't realize licensing has gone up with WS 2016, so the number went from 13 to 15 WS before it makes sense to not license the WS VMs individually, instead of using DC.
I'm now getting the topic off track on the focus of the original post though.
-
@BBigford said in Hyper-V Architecture 2016 and How To Install:
@scottalanmiller said in Hyper-V Architecture 2016 and How To Install:
@BBigford said in Hyper-V Architecture 2016 and How To Install:
But, less than 13 Standard licenses and not growing (or installing more non-Windows servers as they grow), definitely stick with Core and license servers individually as needed.
Of course you already knew all of that, just thought it was worth mentioning here.
I don't understand how the VM licensing relates to Hyper-V.
Just using an example where someone might have more than 13 licenses of Windows Server on a host, using more than that would make sense to have a Datacenter license because the cost of DC would be less than the accumulative cost of Standard on each WS. Since a DC license can't be applied Hyper-V Server/free/non-licensed/Core/non-GUI.
I was just saying it would make sense to have a GUI install in that case.
DC isn't applied to Hyper-V at all. It's applied to Windows. There is no licensing for Hyper-V, so it's a different discussion. You are talking about the VMs, not the hypervisor.
-
@BBigford said in Hyper-V Architecture 2016 and How To Install:
@DustinB3403 said in Hyper-V Architecture 2016 and How To Install:
@BBigford said in Hyper-V Architecture 2016 and How To Install:
@scottalanmiller said in Hyper-V Architecture 2016 and How To Install:
@BBigford said in Hyper-V Architecture 2016 and How To Install:
But, less than 13 Standard licenses and not growing (or installing more non-Windows servers as they grow), definitely stick with Core and license servers individually as needed.
Of course you already knew all of that, just thought it was worth mentioning here.
I don't understand how the VM licensing relates to Hyper-V.
Just using an example where someone might have more than 13 licenses of Windows Server on a host, using more than that would make sense to have a Datacenter license because the cost of DC would be less than the accumulative cost of Standard on each WS. Since a DC license can't be applied Hyper-V Server/free/non-licensed/Core/non-GUI.
I was just saying it would make sense to have a GUI install in that case.
Why would DC licensing not be able to be applied to Hyper-V? The license gets tied to the hardware, not to an individual desktop-workspace on the hardware. . .
Because you can't install a license on Hyper-V Server. It isn't like a CAL where you just buy it for auditing, the OS will cease functioning if a license is not applied. You have to apply it somewhere to subsequently license the VMs on the host.
But not on Hyper-V. You can't install it on Vmware, Xen or KVM but datacenter works in all of those places. Hyper-V is not special.
-
@BBigford said in Hyper-V Architecture 2016 and How To Install:
Doesn't matter if what is a VM? The VMs have to be licensed. If you don't apply a license to the host of the VMs, then there is the issue.
That's not a plausible requirement. Something is wrong with what you are thinking. Datacenter is not connected to Hyper-V in any way.
-
For management sake, do we consider 5Nine the "XenCenter" equivalent for Hyper-V?
-
@FATeknollogee said in Hyper-V Architecture 2016 and How To Install:
For management sake, do we consider 5Nine the "XenCenter" equivalent for Hyper-V?
Yes
-
@scottalanmiller said in Hyper-V Architecture 2016 and How To Install:
@BBigford said in Hyper-V Architecture 2016 and How To Install:
Doesn't matter if what is a VM? The VMs have to be licensed. If you don't apply a license to the host of the VMs, then there is the issue.
That's not a plausible requirement. Something is wrong with what you are thinking. Datacenter is not connected to Hyper-V in any way.
This was what I was getting at. Hyper-V is the hypervisor, is totally free and in no way has an association with Windows licensing requirements. DataCenter Licensing is for Windows Server and therefore is not associated with Hyper-V.
-
@scottalanmiller said in Hyper-V Architecture 2016 and How To Install:
@FATeknollogee said in Hyper-V Architecture 2016 and How To Install:
For management sake, do we consider 5Nine the "XenCenter" equivalent for Hyper-V?
Yes
No "XOA" style manager AFAIK?
-
@BBigford said in Hyper-V Architecture 2016 and How To Install:
If you don't apply a license to the host of the VMs, then there is the issue.
This part here is what I think you are mixing up. You apply datacenter licensing to the hardware, not the what is installed on the the hardware.
DC licensing doesn't care if it's XenServer, KVM or Hyper-V. It's there to license the VM's on that hardware. Nothing else is tied into it.
If you're saying you can't use DC licensing without the Dom0 being a Windows Server, you're sorely mistaken.
-
@FATeknollogee I believe it's required to run as an application, I don't think it has a web interface like XO.
-
@FATeknollogee said in Hyper-V Architecture 2016 and How To Install:
@scottalanmiller said in Hyper-V Architecture 2016 and How To Install:
@FATeknollogee said in Hyper-V Architecture 2016 and How To Install:
For management sake, do we consider 5Nine the "XenCenter" equivalent for Hyper-V?
Yes
No "XOA" style manager AFAIK?
Not yet. Someone will make one, i'm sure.
-
@DustinB3403 said in Hyper-V Architecture 2016 and How To Install:
@FATeknollogee I believe it's required to run as an application, I don't think it has a web interface like XO.
That's correct.
-
@scottalanmiller said in Hyper-V Architecture 2016 and How To Install:
@FATeknollogee said in Hyper-V Architecture 2016 and How To Install:
@scottalanmiller said in Hyper-V Architecture 2016 and How To Install:
@FATeknollogee said in Hyper-V Architecture 2016 and How To Install:
For management sake, do we consider 5Nine the "XenCenter" equivalent for Hyper-V?
Yes
No "XOA" style manager AFAIK?
Not yet. Someone will make one, i'm sure.
Never tried it but here's a basic web interface.
http://hv-manager.org/
