Начал осваивать Windows Server. Дошел до виртуализации, но появился вопрос.
Что лучше ставить, Hyper-V Server как отдельный продукт, или лучше Windows Server и на нем завести роль hyper-v?
Если есть какая-то большая разница, то объясните, пожалуйста, в двух словах в чем она заключается.
-
Вопрос задан
-
5775 просмотров
Задайте себе вопрос на сколько хорошо вы знаете PowerShell, нужен ли домен для Hyper-V. Если нет и да, то 100% роль. Настройки хоста Hyper-V Server почти все через командную строку. По удобству — консоль управления виртуальными машинами на клиенте (вашем рабочем месте) в случае Hyper-V Server и если обычный Windows Server то консоль внутри ОС.
Как уже не один раз обсуждалось после установки роли Hyper-V хост сам становиться клиентом гипервизора. По скорости работы практически будет не заметно. Для учебы я рекомендую поднять роль.
Пригласить эксперта
- Hyper-V Server ничего не может, кроме Hyper-V и управляется только с PowerShell. У него почти нет GUI. Виртуалками через GUI можно управлять через удалённую оснастку со своего компьютера, подключившись через неё по сети к этому Hyper-V Server.
- Windows Server может всё, включая Hyper-V, и управляется через полноценный GUI.
Из-за того, что Hyper-V Server не может делать ничего лишнего, у него меньше потребления ресурсов самой ОС, а значит больше свободных ресурсов для виртуалок. Его ставят на больших парках гипервизоров (хостинг-компании) для повышения плотности.
Если перспектива писать командочки в PowerShell вместо тыка в интерфейс, и отсутствие задач на этом сервере кроме Hyper-V Вас устраивает, то выбирайте Hyper-V Server.
Для начала — Роль. Общие принципы поймёте и если будет (необходимость) ковыряться дальше — поставите server.
Скорее всего разница в потребляемых ресурсах такого сервера. Можно предположить, что связка Windows Server + Hyper-V будет потреблять ресурсов больше, чем Hyper-V Server. Ну и как одно из следствий — Hyper-V Server будет работать шустрее.
Hyper-V Server бесплатен.
Войдите, чтобы написать ответ
-
Показать ещё
Загружается…
Минуточку внимания
Skip to content
Hyper-V Servers vs Windows Server Hyper-V – An Overview
Importance of Virtualization
Virtualization concepts aim for increased business productivity by using a minimal number of physical servers. These virtualization concepts can be implemented by the firmware or software components known as Hypervisors. The Hypervisor has the ability to virtualize the physical server, thus permitting the system to host multiple guest VMs. They are eventually optimized to enhance the production of the physical server environment. Traditionally the Hypervisors are deployed directly on the bare metal or they run as an application on the operating system which resides on the physical hardware.
Protect Your Data with BDRSuite
Microsoft Hyper-V
Microsoft has developed a convincing alternative to some of the other hypervisor vendors in the Virtualization market. It fairly provides Hyper-V Servers and Windows Server Hyper-V to reduce the workloads of IT firms, SMBs and Enterprise level organizations. These Hypervisors are capable of creating and running virtual machines optionally by enabling the Hyper-V role on the Windows Servers or as a separate Hyper-V server OS on the Bare metal. Here comes the confusion that “Whether to go with Hyper-V Servers or to Windows Server Hyper-V”, which is better?
Hyper-V Servers vs Windows Server Hyper-V
Microsoft developed Hyper-V Servers which signified the growth of the virtualization technology. Hyper-V Servers are exclusively a Standalone product which has direct access to the physical machine’s hardware, where you lose the ability to enable the Hyper-V role on the physical Server machine. Hyper-V Servers seated on the Host hardware consolidates the single Host machine into a number of virtual machines, which operates on the available pooled resources of the server machine in order to convert the higher density environment into smaller space. On the other hand, Hyper-V Servers are completely free to download and install. it also allows you to build your own virtual environment. Then what’s the role of Windows Server Hyper-V?
To make it more simplified, Microsoft alters the Hyper-V Server to be implemented as a role on the Server class Windows operating system. Therefore the Host OS turns out into the parent partition where the hypervisor partition resides between the parent partition and the Host hardware. Windows Server with Hyper-V comes out with different editions (Standard, Datacenter, Essentials) in the market which relies on the type of Windows server operating system of your choice. The difference is that adapting to Hyper-V Server restricts the user to experience the robust set of features and roles of windows operating system but the Windows server Hyper-V eliminates this feature restriction. So, which is better? To be honest, I’m not sure which one is better than the other. The fact is that Microsoft delivers these packages on the licensing basis. In my opinion, the user’s choice would be at absolute best based on their licensing needs.
Conclusion
The optimized Features and periodical updates on Microsoft Hypervisors gives a tough competition for the other Hypervisor vendors around the virtualization market.
Follow our Twitter and Facebook feeds for new releases, updates, insightful posts and more.
Try BDRSuite for Free!
Schedule a live demo with one of our product experts
Start your full-featured 30-day free trial
Explore detailed pricing, editions & features
Since 2008, Microsoft has provided two deployment options for the Hyper-V hypervisor – a standalone installation of Hyper-V Server and a Hyper-V role that can be added onto an existing Windows Server operating system. Which Hyper-V edition is better for you? Today’s blog post compares and contrasts Hyper-V Server 2016 with the Hyper-V role for Windows Server 2016. Licensing, installation, user interface, VM management, clustering, and use cases are explored. After reviewing each deployment type in detail, we explore their advantages and disadvantages to help you determine what option suits your virtual environment best.
Hyper-V Server 2016
The first type of deployment for Hyper-V reviewed in this blog post is the standalone Hyper-V Server 2016.
Licensing
Hyper-V Server 2016 is distributed for free and can be downloaded from Microsoft’s site. You can use Hyper-V Server 2016 for an unlimited period of time without paying anything and without activation, but there are no licenses provided for guest VMs running Windows. As a result, you must purchase licenses for guest Windows systems according to Microsoft’s license agreement. There are no licensing issues if you deploy VMs running Linux. Be aware that Microsoft prohibits the use of a standalone Hyper-V Server 2016 as a web server, file server, database server, or any other type of server whose role is not hosting virtual machines.
Installation
The installation process of Hyper-V Server 2016 is similar to installing Microsoft Windows Server Core. It looks like Windows Server Core with the minimal set of features needed for it to function as a hypervisor. Configuration of Hyper-V Server 2016 is also minimal – the hypervisor is ready to work right after installation.
User interface
Similarly to Windows Server Core, Hyper-V Server is lightweight and has no GUI (graphical user interface); only a command line interface (CLI) is provided. You will not find any options related to Hyper-V in the console-based server configuration menu. You can create users, install updates, change computer names, manage network settings, enable remote management, shut down or restart the server, and exit to CMD. You can enter PowerShell from CMD. VMs can be created, deleted, started, stopped, renamed etc. with PowerShell.
VM management
You can create, delete, start, and stop VMs on your instance of Hyper-V Server with PowerShell locally and remotely. If this VM management method is not convenient for you, use Hyper-V Manager remotely. For this, you need another Windows machine with the Hyper-V role installed. When you install the Hyper-V role on a Windows machine, Hyper-V manager is installed by default. Open Hyper-V Manager, connect to your headless Hyper-V Server 2016, and manage your VMs. As an alternative to Hyper-V Manager, you can use another GUI tool for centralized management called System Center Virtual Machine Manager (SCVMM). Note that while Hyper-V Manager is free, you have to pay for SCVMM.
Clustering features
Clustering is supported by Hyper-V Server 2016. The requirements are the same as the requirements for a Hyper-V Failover Cluster built on Windows Server 2016 nodes with the Hyper-V role installed. The entire cluster configuration can be done with PowerShell.
Use cases
The free Hyper-V Server 2016 is a nice solution for virtualizing existing Windows servers and Windows desktops that are already licensed, as well as running Linux machines that don’t require licenses. Hyper-V Server 2016 can also be used for educational and testing purposes or for companies that do not have high numbers of VMs that must be licensed.
Hyper-V 2016 Role on Windows Server 2016
Let’s now explore the same categories for the Hyper-V role on Windows Server 2016.
Licensing
A paid license must be applied to Windows Server 2016 on a per-core basis (except for the Essentials edition – but using this is not rational for Hyper-V). You can select the Standard or Datacenter edition. The Windows Server 2016 Standard edition includes licenses for two Windows-based Hyper-V virtual machines and is suitable for smaller virtualized environments. Windows Server 2016 Datacenter Edition includes licenses for unlimited numbers of Hyper-V virtual machines running Windows, and accordingly is recommended for highly virtualized environments. Moreover, the Datacenter edition allows you to deploy shielded VMs and use Storage Spaces Direct, with storage replicas and a software-defined networking stack.
You do not pay for the ability to install the Hyper-V role; you pay for the instance of Windows Server running on your host and the Windows OS running on your VMs.
Installation
Windows Server 2016 must first be installed to enable the Hyper-V role. Windows Server 2016 can be installed in the core mode (which is similar to the installation of Hyper-V Server) or in GUI mode. Using the GUI mode (the “desktop experience”) is more convenient, and Hyper-V Manager could be used locally on Windows Server 2016 with the Hyper-V role in this case. If you enable the Hyper-V role on Windows Server 2016 Datacenter Core, despite the lack of GUI, you can deploy an unlimited number of VMs running Windows according to the license agreement.
User interface
Windows Server 2016 with the Hyper-V role allows you to use both command line and graphical user interfaces. As explained in the previous section, you can select the user interface in the beginning of Windows Server 2016 installation. Windows Server 2016 Core provides only a command line interface. Install Windows Server 2016 with the desktop experience if you want to use a GUI.
VM management
If you have installed Windows Server 2016 in the GUI mode and enabled the Hyper-V role, then you can use Hyper-V Manager to manage VMs residing on a local server and VMs residing on remote servers. You can also use PowerShell or System Center Virtual Machine Manager (SCVMM).
Clustering features
All Hyper-V failover clustering features are supported if you enable the Hyper-V role on Windows Server 2016. You can deploy a Hyper-V failover cluster with multiple nodes and shared storage to achieve high availability of Hyper-V VMs running on Hyper-V hosts.
Use cases
Windows Server 2016 with the Hyper-V role is adopted for use in production environments with Windows VMs. Windows Server 2016 Datacenter Edition is the best option in highly virtualized production environments where the most of Hyper-V VMs are running Windows. Note that Windows Server 2016 offers much more than just the Hyper-V role. You can deploy any other role on your server running Windows Server 2016.
Advantages and Disadvantages of the Two Hyper-V Deployments
Each type of Hyper-V deployment has its own advantages and disadvantages. This section outlines the pros and cons of the standalone Hyper-V Server 2016 and Windows Server 2016 with Hyper-V.
Advantages of Hyper-V Server 2016
- Zero price. Hyper-V Server 2016 is absolutely free. No activation required.
- Small footprint. Hyper-V Server 2016 is a lightweight distribution that occupies less disk space and consumes less memory than Windows Server 2016 with the Hyper-V role.
- Security. Fewer components are included in Hyper-V Server, which means fewer vulnerabilities. Only the components required to run VMs are present.
Disadvantages of Hyper-V Server 2016
- No Windows GUI.
- Limited management tools.
- Licensing limitations. Windows VMs must be licensed separately. No other roles except Hyper-V can be enabled on the server.
Advantages of Windows Server 2016 with a Hyper-V role (with GUI)
- Ease of use. The Windows GUI can be used, allowing you to manage a server conveniently.
- More tools and features available. Any server role can be installed.
- Full support (software and hardware).
- Includes licenses for Windows installed on Hyper-V VMs.
- Windows installed on Hyper-V VMs can be automatically activated (true for Datacenter edition).
Disadvantages of Windows Server 2016 with a Hyper-V role (GUI-based)
- Consumes more hardware resources.
- Cost. The license is expensive, and the Windows OS installed on hosts must be activated.
- More potential vulnerabilities.
Hyper-V Server 2016, similarly to Windows Server 2016 Core, does not include Windows Explorer, which is the main component of Windows graphical shell. (Internet Explorer is a part of Windows Explorer.) This is a less user-friendly solution, but it improves security. In the GUI mode, even if you use only tools such as MMC (Microsoft Management Console) for server management, without using Internet Explorer, Internet Explorer is still present in your system and could constitute a threat for your server. This is the reason many IT specialists may prefer installing the Core Edition of Windows Server operating system in some situations.
At the same time, some basic graphics features used for displaying windows that are not Explorer-related are available in the headless edition of Windows Server 2016 and Hyper-V Server 2016. For example, you can press Ctrl+Shift+Esc to run the Windows Task Manager.
One additional advantage of the standalone Hyper-V Server is that the smaller number of included components means you need less frequent updates (patches) and, as a result, fewer reboot events for the server.
Both Hyper-V Server 2016 and the Hyper-V role enabled on Windows Server 2016 are type 1 hypervisors. A type 1 hypervisor is a native hypervisor installed directly on hardware, whereas a type 2 hypervisor runs as an application on the installed operating system. The trick is that when Windows Server 2016 with the Hyper-V role is loaded, Hyper-V is initialized first, before starting Windows, which makes it type 1 hypervisor.
Conclusion
Today’s blog post has explored the similarities and differences between standalone Hyper-V Server 2016 and Windows Server 2016 with the Hyper-V role installed. Most of Hyper-V features are the same for these two types of Hyper-V deployment (the exceptions being shielded VMs and Storage Spaces Direct, which are available with Windows Server 2016 Datacenter Edition). The main differences are in licensing host operating systems and guest Windows operating systems – Hyper-V Server 2016 is free, but guest Windows installed on VMs must be licensed separately. Windows Server 2016 requires a paid license, but includes licenses for VMs running Windows. The user interfaces and management tools also differ. Hyper-V Server 2016 and Windows Server 2016 Core with Hyper-V don’t have GUIs, and hence must be managed either locally through CLIs or remotely from other machines with GUIs. Windows Server 2016 (with GUI/desktop experience) and Windows Server 2016 Core provide the same Hyper-V functionality, but Windows Server 2016 with GUI can be managed locally through GUI-based tools such as Hyper-V Manager.
Regardless of which edition of Hyper-V you decide to use in your environment, remember to back up your virtual machines. NAKIVO Backup & Replication can back up VMs running on standalone Hyper-V Server 2016, VMs running on Windows Server 2016 with the Hyper-V role, and VMs running in a Hyper-V Failover Cluster.
Like in eternal debates about what is better – cats or dogs, fathers or mothers, cars or bikes –, there is no ready answer to the question of the Windows 10 Hyper-V and Windows Server Hyper-V debate. It’s difficult to say for sure which one is “better” to make you choose it over the other. The reason is that both of them are necessary for meeting business needs at different times and under different circumstances. These two tools integrate well with our Hyper-V backup solutions (visit our official website to learn more) and boost your disaster readiness. Keep reading to discover when and why it’s ideal for you to choose one over the other.
Windows 10 Advantages Over Windows Server
Let’s start our analysis by looking at some of the capabilities Windows 10 has over Windows Server. Indeed, Windows 10 has admirable features Windows Server lacks. For instance, it has a Quick Create feature. This capability facilitates your virtual machine’s creative processes by enabling it to choose an OS image from its Create Gallery.
Also, it has a default virtual switch that facilitates more effortless connecting to virtual machines without creating manual switches. Thus, you enjoy efficient functionality while operating your virtual machines.
Windows Server’s Advantages Over Windows 10
Inversely, Windows Server supports failover clustering and makes your VMs more available than Windows 10 does. This feature is necessary for promoting a robust production atmosphere. Additionally, it supports the Hyper-V Replica feature its counterpart lacks. This capability enables stand-alone virtual hard disks connected to your virtual computers to synchronize asynchronously to a single or a pair of hosts. Thus, you can always access your virtual PC copies when primary hosts fail because you can activate them on one of the replica hosts.
It also has a virtual Fiber Channel that lets virtual computers utilize physical hosts’ bus adapters connecting its storage.
Moreover, it has the Discrete Device Assignments capability that lets virtual machines to utilize PCIe hardware devices. It also features Hyper-V Replica, lets you migrate virtual PCs live between different hosts, and has virtualizing GPU capabilities.
How They Differ
So, how do these tools differ? Here are their core differences that will assist you in making an informed and beneficial decision.
Their memory management models differ. When working on servers, you manage your Hyper-V memory, assuming that virtual computers alone are on it. However, when running it on Windows, you manage its memory, expecting most client computers to run applications while running virtualized PCs. For instance, developers could run a couple of virtualized computers on the same computers while running other apps.
Hyper-V Server: Pros and Cons
Lastly, we compare and contrast them based on their different strengths and weaknesses.
Pros
- It’s free of charge, and you don’t need to activate it to work.
- Its footprint is minimal because it’s small and doesn’t occupy much space on your disks. Also, it doesn’t consume much memory.
- It’s secure because it doesn’t include many parts, meaning it’s less vulnerable to attacks.
Cons
- It lacks a Windows GUI.
- Its management tools are fewer.
- Its licensing is limited because virtualized machines require separate silences. Thus, you can’t enable any other role in its servers besides Hyper-V.
Windows Server: Pros and Cons
Pros
- It’s easy to use it.
- It features GUI, and so, enabling convenient server management.
- It enjoys complete software and hardware support.
- It has more tools and capabilities.
- You can install other server roles beside Hyper-V.
- It allows for the automatic activation of Windows installed on Hyper-V computers.
Cons
- It consumes a lot of your hardware resources.
- It’s costly because you need to buy licenses and activate the Windows operating system on hosts.
- Its many components make it vulnerable to attacks.
Can you see what the debate boils down to? It’s not a matter of what’s better or worse; it’s a matter of what you need at a time and under specific conditions. Thus, we hope you will use this information to choose wisely.
Laptop with Windows 10 logo -DepositPhotos
Signup for the newsletter
Sign For Our Newsletter To Get Actionable Business Advice