Hyper-V Server or Windows Server + Hyper-v role?

Started to learn Windows Server. Came to virtualization, but had a question.
What better to put Hyper-V Server as a separate product, or better Windows Server and start the hyper-v role?
If there's a big difference, then please explain in a nutshell what it is.
July 9th 19 at 13:04
4 answers
July 9th 19 at 13:06
Solution
Ask yourself how well you know PowerShell, you need the domain for Hyper-V. If no and Yes, 100% role. Configure Hyper-V host Server almost everything via the command line. Convenience - based management console and the virtual machines on the client (your workplace) in the case of Hyper-V Server and regular Windows Server if the console inside the OS.
As once was discussed after the role installation Hyper-V host itself becomes a client hypervisor. At almost the speed of work will not be noticeable. For study I recommend to raise the role.
: can - hank.Grant7 commented on July 9th 19 at 13:09
: it is possible, in one place (netdom join) just everything :) - Timmothy.Thiel commented on July 9th 19 at 13:12
July 9th 19 at 13:08
  • Hyper-V Server can not do anything except Hyper-V and can only be controlled with PowerShell. He has almost no GUI. Virtualname through the GUI can be controlled via a remote snap-in from your computer by using it on the network this Hyper-V Server.
  • Windows Server can do everything, including Hyper-V and managed via a full GUI.

Due to the fact that Hyper-V Server can't do anything unnecessary, it has less consumption of resources the OS itself, which means more free resources for virtualos. He put on larger parks hypervisors (the hosting company) to increase the density.

If the prospect of writing comanducci in PowerShell instead of the spear into the interface, and no tasks on the server except Hyper-V suits You, then choose Hyper-V Server.
Well Hyper-V Server is perfectly controlled and with a GUI. - hank.Grant7 commented on July 9th 19 at 13:11
: Using remote snap-in. =) - Timmothy.Thiel commented on July 9th 19 at 13:14
: But thank you for remark, will update the answer. - earl.Weissnat commented on July 9th 19 at 13:17
: Well, the snap is quite local to the working machine, is a hypervisor remote. - Carli commented on July 9th 19 at 13:20
About GUI I wrote to the fact that the server itself is not particularly ponastavili the mouse. Some former colleagues with that in the past had problems.

What new path can be visually manedit snap-in, connect to the hypervisor over the network - Yes. - Carli commented on July 9th 19 at 13:23
: Yes, I have too say was a culture shock when I first time hypervisor from Microsoft I saw.
As it is not imagined product from Microsoft, and without GUI.
Although PowerShell in principle in management much easier.
And now they have and 2012, you GUI to disable and nanosilver's already released. - earl.Weissnat commented on July 9th 19 at 13:26
Yeah. It's cool that MS in General is not in place. =) - Carli commented on July 9th 19 at 13:29
July 9th 19 at 13:10
To begin with - the Role. General principles understand and if (need) to be picked on, put server.
July 9th 19 at 13:12
Most likely the difference in the consumed resources of the server. We can assume that a bunch of Windows Server + Hyper-V will consume more resources than the Hyper-V Server. Well, as one of the consequences of Hyper-V Server will run faster.

Find more questions by tags VirtualizationHyper-V