Forum Discussion
Installing Windows server on Hyper-V
Hey,
What are the reasons that better to install on physical host/computer Windows server, and then by Hyper-v install another Windows Server THAN Install Windows 10pro on physical and then by Hyper-v(of windows 10 pro) the Windows server.?
How about how does it work with essentials, because it does not support Failover Clustering, so what if i use only Essentials on hyper-v (When physical is Windows 10 pro..)
Let me know what is the disadvantage and advantage in these cases..
NgrayIT Read here: https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/about/#differences-between-hyper-v-on-windows-and-hyper-v-on-windows-server
Additionally, what this article does not mention, the Thread-Scheduling works differently as well. There are three different Scheduler-Modes for Hyper-V: fair-share, core and root.
"Fair-share" was the default for Windows Server before Server 2019.
"Core" is the default for Server 2019 and recommended for Server 2016.
"Root" is the scheduler for Client-Hyper-V and only available there.
Changing the scheduler type on Client Hyper-V is not supported or tested.
Aside from that, if you run a virtual Windows Server OS you need a license for it anyway. If you have a license, you can use the same license for the host which allows you to install 2 virtual instances of the same license on top of it (so no reason to use Windows 10 on the host there).
For running a virtual Essentials Server you could just use the free Hyper-V Server 2019 for the host, or read about other options here: https://docs.microsoft.com/en-us/windows-server-essentials/install/install-and-configure-windows-server-essentials-or-windows-server-essentials-experience#BKMK_VirtualWSE
NgrayIT Read here: https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/about/#differences-between-hyper-v-on-windows-and-hyper-v-on-windows-server
Additionally, what this article does not mention, the Thread-Scheduling works differently as well. There are three different Scheduler-Modes for Hyper-V: fair-share, core and root.
"Fair-share" was the default for Windows Server before Server 2019.
"Core" is the default for Server 2019 and recommended for Server 2016.
"Root" is the scheduler for Client-Hyper-V and only available there.
Changing the scheduler type on Client Hyper-V is not supported or tested.
Aside from that, if you run a virtual Windows Server OS you need a license for it anyway. If you have a license, you can use the same license for the host which allows you to install 2 virtual instances of the same license on top of it (so no reason to use Windows 10 on the host there).
For running a virtual Essentials Server you could just use the free Hyper-V Server 2019 for the host, or read about other options here: https://docs.microsoft.com/en-us/windows-server-essentials/install/install-and-configure-windows-server-essentials-or-windows-server-essentials-experience#BKMK_VirtualWSE
- Thanks for your great answer.
When you said i can install 2 virtual machines on top of phycial, did you mean Windows server Essentials?
As well, "For virtualizing Essentials Server you could just use the free Hyper-V Server 2019 for the host", Hyper-V server 2019 dont have GUI..
Is it bad idea or lets say "not clever" idea to install essentials version on physical device?
My purpose is to run websites(iis) and dbs..As far as I know you can install Hyper-V role on an essentials instance but only if you cancel the essentials roles installation so that only Hyper-V role is installed, then you can install a single guest instance.
Its not clear why you want essentials? If all you need is a single instance of windows to run a website with database backend you can install it on a server standard physical machine. If Hyper-V is a requirement then you can buy a server standard license that, by default, provides rights for up to 2 Operating System Environments. (as long as no other roles on host)
