Negotiated Drive Speed
-
@scottalanmiller said:
The additional licensing piece, which is effectively pointless to discuss for many reasons, is the one part that makes people confused.
If you have Windows Server Standard you get this special case "physical" license that can be used as a freebie local GUI for hyperV and nothing else. This is not recommended for install and is generally not good to install, so it's not a benefit in any real way. It cannot be used for anything but the management of HyperV (so it is not a useable VM.) So it can be discounted because even if you have the rights to it, it isn't useful and gains you nothing (essentially.)
Don't think about it, because it doesn't matter. The two former rules are all that actually matter.
OK, then I did 100% understand the licensing. I don't really find it confusing.
Also, I know you feel that way, but from what I have read, it basically takes up very little resources on the server. Even less so if you run it in GUI-less mode.
-
@BRRABill said:
Also, I know you feel that way, but from what I have read, it basically takes up very little resources on the server. Even less so if you run it in GUI-less mode.
If you run GUI-less, what is its point? No matter how little it takes up, it wastes resources, increases the patch cycle (the biggest concern) and increases the attack surface.
You can excuse that it is "not that bad" as much as you want. Tell me why it is better, instead.
-
@Dashrender said:
In other words, if you use that manage Hyper-V VM for something other than managing Hyper-V, for backups for example, you are now limited to only one more VM with your Windows Server license.
True, but a confusing way to approach it. You get two VMs that "do anything." It's that simple. Does it do something? It used a license. The number you get doesn't change. You get two.
-
@scottalanmiller said:
@BRRABill said:
Also, I know you feel that way, but from what I have read, it basically takes up very little resources on the server. Even less so if you run it in GUI-less mode.
If you run GUI-less, what is its point? No matter how little it takes up, it wastes resources, increases the patch cycle (the biggest concern) and increases the attack surface.
You can excuse that it is "not that bad" as much as you want. Tell me why it is better, instead.
I, myself, wouldn't run it GUI-less. I like pictures.
I am familiar with all the tools it uses to manage the VMs.
That is, for me, why it is better. At least in concept.
-
@Dashrender said:
In other words, if you use that manage Hyper-V VM for something other than managing Hyper-V, for backups for example, you are now limited to only one more VM with your Windows Server license. If you only use it to manage Hyper-V, you can install Windows Server as a VM 2 more times, for a total of three Hyper-V VMs with only one license. But this is generally a waste of resources since you can and should be managing Hyper-V using Hyper-V manager and RSAT from another machine.
Backups of the VMs would be OK though, no? That is managing the VMs. Though from previous threads it doesn't seem like anyone does that anyway. So it is a moot point.
I would definitely be looking to manage it from another machine. I've only ver install it local to the server, and used RDP to connect to it. But I see now there are better ways, obviously.
-
@BRRABill said:
@scottalanmiller said:
@BRRABill said:
Also, I know you feel that way, but from what I have read, it basically takes up very little resources on the server. Even less so if you run it in GUI-less mode.
If you run GUI-less, what is its point? No matter how little it takes up, it wastes resources, increases the patch cycle (the biggest concern) and increases the attack surface.
You can excuse that it is "not that bad" as much as you want. Tell me why it is better, instead.
I, myself, wouldn't run it GUI-less. I like pictures.
I am familiar with all the tools it uses to manage the VMs.
That is, for me, why it is better. At least in concept.
Why not? have you ever used ESXi? it's been GUI-less since day one. You install it from USB or CD, then connect to it via web browser, download and install vSphere client, connect via the client and go!
Hyper-V GUI-Less is similar - Install from USB or CD, on local workstation, install Hyper-V manager and RSAT, connect and GO!
-
@BRRABill said:
I, myself, wouldn't run it GUI-less. I like pictures.
I am familiar with all the tools it uses to manage the VMs.
That is, for me, why it is better. At least in concept.
If you use the GUI, it is cumbersome. RDP to a machine to manage it? That's horribly complex and slow. Even if you have it installed, you would never want to use it.
Have you looked at the alternative? I truly do not understand this "I'm familiar with it" line. I don't see how the MS tools are any more "natural" than the other ones. They are all equally not something that you are used to.
-
@BRRABill said:
@Dashrender said:
In other words, if you use that manage Hyper-V VM for something other than managing Hyper-V, for backups for example, you are now limited to only one more VM with your Windows Server license. If you only use it to manage Hyper-V, you can install Windows Server as a VM 2 more times, for a total of three Hyper-V VMs with only one license. But this is generally a waste of resources since you can and should be managing Hyper-V using Hyper-V manager and RSAT from another machine.
Backups of the VMs would be OK though, no? That is managing the VMs. Though from previous threads it doesn't seem like anyone does that anyway. So it is a moot point.
I would definitely be looking to manage it from another machine. I've only ver install it local to the server, and used RDP to connect to it. But I see now there are better ways, obviously.
Nope, that's doin' something. You could stop the VMs and copy them manually somewhere else, but I don't think Hyper-V (just like ESXi and XS) doesn't have a built-in backup solution. You have to use another backup solution, and you can't do that on the management VM, cause that's doin' somethin' and would use a VM license.
-
@Dashrender said:
Nope, that's doin' something. You could stop the VMs and copy them manually somewhere else, but I don't think Hyper-V (just like ESXi and XS) doesn't have a built-in backup solution. You have to use another backup solution, and you can't do that on the management VM, cause that's doin' somethin' and would use a VM license.
Technically XS does
-
@BRRABill said:
Backups of the VMs would be OK though, no? That is managing the VMs.
If you have to get into semantics and word games to try to make it sound legit, you can safely assume that there is no way it's okay.
-
@scottalanmiller said:
@Dashrender said:
Nope, that's doin' something. You could stop the VMs and copy them manually somewhere else, but I don't think Hyper-V (just like ESXi and XS) doesn't have a built-in backup solution. You have to use another backup solution, and you can't do that on the management VM, cause that's doin' somethin' and would use a VM license.
Technically XS does
OH - OK I know most use XO - but I think Dustin was using something else before that...
-
@Dashrender said:
@scottalanmiller said:
@Dashrender said:
Nope, that's doin' something. You could stop the VMs and copy them manually somewhere else, but I don't think Hyper-V (just like ESXi and XS) doesn't have a built-in backup solution. You have to use another backup solution, and you can't do that on the management VM, cause that's doin' somethin' and would use a VM license.
Technically XS does
OH - OK I know most use XO - but I think Dustin was using something else before that...
Yes, NAUBackup.
