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.
-
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/ -
@black3dynamite 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:
@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/Claims to require Windows and not to work with Hyper-V itself.
-
-
-
@scottalanmiller said in Hyper-V Architecture 2016 and How To Install:
@EddieJennings said in Hyper-V Architecture 2016 and How To Install:
Whamo Namo
Today's server crash brought to you by Whamo. Makers of fine sledge hammers everywhere.
-
@BBigford said in Hyper-V Architecture 2016 and How To Install:
I was just saying it would make sense to have a GUI install in that case.
The only reason you would ever install Windows Server on bare-metal instead of the free Hyper-V Server 2016, is if you need to use features or services on bare-metal that are not available or allowed on the free Hyper-V Server. For example, just because you CAN install something on Hyper-V Server, doesn't mean you technically are allowed to according to Microsoft's licensing.
For example, I have installed Windows Server 2016 Standard on a physical HOST because I needed to use deduplication on the host's physical storage. Deduplication is not available on Hyper-V Server 2016, so I was forced in to installing Windows. That's one scenario where you would not install Hyper-V Server.
But Scott is correct, you should otherwise ALWAYS install Hyper-V Server 2016 on bare-metal, regardless of licensing.
-
@scottalanmiller 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.
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.
I think what he might be getting at is automatic VM activation, which occurs if you have applied a Datacenter License key to Windows Server Datacenter running on the Host. But that's a moot reason to install full Windows on a Host when there are options to use a KMS or other license server.
-
@Tim_G said in Hyper-V Architecture 2016 and How To Install:
For example, I have installed Windows Server 2016 Standard on a physical HOST because I needed to use deduplication on the host's physical storage. Deduplication is not available on Hyper-V Server 2016, so I was forced in to installing Windows. That's one scenario where you would not install Hyper-V Server.
Why would you need/want dedup at the hypervisor level? Are you implying that MS's dedup is not allowed to be used inside a VM? If so, do you have a link?
-
@Tim_G said in Hyper-V Architecture 2016 and How To Install:
@BBigford said in Hyper-V Architecture 2016 and How To Install:
I was just saying it would make sense to have a GUI install in that case.
The only reason you would ever install Windows Server on bare-metal instead of the free Hyper-V Server 2016, is if you need to use features or services on bare-metal that are not available or allowed on the free Hyper-V Server. For example, just because you CAN install something on Hyper-V Server, doesn't mean you technically are allowed to according to Microsoft's licensing.
It's important to note though that you are allowed to install anything there as long as licensing for the feature is acquired. Example might be having Datacenter licensing for the hardware - you can then put any function or feature that you want in the Dom0 VM because you paid for it. It's still lean so many things won't exist or work. But you always have the option of paying for the Dom0 to be allowed to do additional things from Windows either by consuming one VM OSE from a standard license or by having a D.C. License.
-
@Tim_G said in Hyper-V Architecture 2016 and How To Install:
I think what he might be getting at is automatic VM activation, which occurs if you have applied a Datacenter License key to Windows Server Datacenter running on the Host. But that's a moot reason to install full Windows on a Host when there are options to use a KMS or other license server.
I wonder if MS updated Hyper-V Server 2016 to allow you to add a DC key just for this reason?
-
@scottalanmiller said in Hyper-V Architecture 2016 and How To Install:
@Tim_G said in Hyper-V Architecture 2016 and How To Install:
@BBigford said in Hyper-V Architecture 2016 and How To Install:
I was just saying it would make sense to have a GUI install in that case.
The only reason you would ever install Windows Server on bare-metal instead of the free Hyper-V Server 2016, is if you need to use features or services on bare-metal that are not available or allowed on the free Hyper-V Server. For example, just because you CAN install something on Hyper-V Server, doesn't mean you technically are allowed to according to Microsoft's licensing.
It's important to note though that you are allowed to install anything there as long as licensing for the feature is acquired. Example might be having Datacenter licensing for the hardware - you can then put any function or feature that you want in the Dom0 VM because you paid for it. It's still lean so many things won't exist or work. But you always have the option of paying for the Dom0 to be allowed to do additional things from Windows either by consuming one VM OSE from a standard license or by having a D.C. License.
Yes that's a good point.
