On the other hand, if you decide to go with free Hyper-V Server , you will have to purchase additional OS licenses for all VMs running in your system. Even though choosing and purchasing an OS license for every VM in the system might seem like a challenging and resource-intensive task, you still should not stop using Hyper-V Server.
In fact, you can greatly benefit from use of free Hyper-V Server by installing open-source OSs, which are available for free and can be easily accessed and used by anyone. They provide a high level of productivity and a rich feature-set, which makes open-source OSs a great alternative to using licensed Windows-based OSs.
As you already know, free Hyper-V Server and the Hyper-V role on Windows Server are essentially the same hypervisor with similar sets of features and server capabilities. However, while Windows Server provides a wide range of server roles, free Hyper-V Server serves only one purpose, which is server virtualization. If you only need a server for purposes of virtualization and want to minimize costs associated with Hyper-V deployment, free Hyper-V Server is the best choice for you. However, if you need a server with an advanced set of server roles and capabilities, you are prepared to purchase an OS license, and want to enjoy the benefits of readily available technical support, then you should deploy Windows Server with the Hyper-V role enabled.
This way, you can avoid the pitfalls of using either Hyper-V Server or Windows Server and make the most use of these deployment options. Shouldn't be a problem, some general info Each host needs to be licensed. Core licenses are sold in packs of two. Thank you all! Comment Show 0. Thank you all for the quick response! One more question that just occurred to me is what key should I use in the VM? Yes, that's correct. Use the same key as used on host. Related Questions.
Thanks for your feedback. Where does it say this on a Microsoft web site. I will have to show this to management to get it purchased.
Here is what I needed. Check out the license for Windows Section 2. Use in a virtualized environment. This license allows you to install only one instance of the software for use on one device, whether that device is physical or virtual. If you want to use the software on more than one virtual device, you must obtain a separate license for each instance. On Windows 10 we have a couple of programs that cannot be installed at the same time with out conflicts.
I read this already a couple of times, but it only tells me at best that the physical machine can't be PDC at the same time - but that only with the same license? Does it with a different license? If so can I run the HyperV with another License as application server? It isn't recommended to run other roles on a hyper-v host.
Also especially not recommended to run hype-v role on a domain controller.
0コメント