![]() ![]() The next few steps are can be skipped if you have Active Directory on a Domain with Hyper-V Administrator permissions set. The idea of using a client and server is that you could use Hyper-V Manager on a power-efficient portable client device while running Hyper-V Server and mulitple OS workloads on your stationary workstation or bare metal server. Once installed, we can use Hyper-V Manager on our client locally or to connect to Hyper-V Server and create and manage VMs there. Or in PowerShell as Administrator: Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All If you can't find Hyper-V Manager by searching the Start Menu, you may need to enable it in Windows Features: Hyper-V Manager requires Windows 10 Pro, Enterprise, or Education. You really get the most from your headless Hyper-V Server by connecting it to Hyper-V Manager from another Windows 10 client or using PowerShell. You can also access your Hyper-V Server with an RDP client like Remmina: sudo apt install remmina On AMD chips you will need Windows 10 build 19636 or higher and currently nested KVM acceleration is not supported. ![]() Note: Hyper-V nested virtualization works well on Intel chips. ![]() If you are running Hyper-V Server on Hyper-V and run into issues starting new VMs you may need to shut down and enable nested virtualization for that VM: Set-VMProcessor -VMName "Hyper-V Server 2019" -ExposeVirtualizationExtensions $true It is also possible to forward the Remote Desktop connection without using an external switch, but this quick and dirty for our lab testing. You can then access Remote Desktop from other devices on the network, using the External Switch IP: If you are running Hyper-V Server inside Hyper-V (and not on bare metal) then you will need to shutdown your VM, go to your Virtual Switch Manager on your host, add an External Switch, which is reachable from outside your localhost, and then add it to your Hyper-V Server VM: Then connect from another device with the Remote Desktop client built into Windows: You can enable Remote Desktop to Hyper-V Server, allowing the server to act as a headless VM server, with option 7:Īfter enabling, you can try Remote Desktop by getting the Hyper-V Server's IP address with option 8: Log back into our freshly updated system: Then I manually run updates with option 6, which will end with needing to restart: I also enable Telemetry so Microsoft can see, anonymously, what I am doing with Hyper-V Server with option 10: The first thing I do is enable Automatic Updates for security purposes with option 5: Then we get to the main show: A Command Prompt and our Hyper-V Server Configuration script. Hyper-V Server is all managed on the device in a terminal user interface (TUI). The first run of Hyper-V Server looks a bit sparse. Windows will create some system and reserved partitions: Select 'Custom' install unless you are upgrading:Ĭreate new and format virtual disks, as needed: The initial install process for Hyper-V Server looks remarkably like Windows 10. You could even run Hyper-V Server inside another type 1 hypervisor such as Hyper-V or KVM that supports nested virtualization extensions. You can burn your Hyper-V Server ISO to a DVD or to a USB with Rufus. You simply need to complete some work information: You can download Hyper-V Server 2019 for free directly from Microsoft: Note though, you will need proper licenses for Windows versions running on top of Hyper-V Server. Microsoft provides an unlimited evaluation period to use it. What is nifty about Hyper-V Server is that it is free from Microsoft. Hyper-V supports Windows 7, 8.1, 10, as well as a variety of Linux and BSD guests. If you are familiar with Windows 10 Server, think of Hyper-V Server as Windows 10 Server with just the Hyper-V Role and a very minimal TUI. Hyper-V Server 2019 is a lightweight version of Windows 10 Server 2019 that is optimized to act only as a Hyper-V host. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |