Deploying Windows Server 2022 with the Desktop Experience (GUI) installed is an inefficient use of hardware resources, particularly when the server’s sole purpose is to act as a Hyper-V virtualization host. Every megabyte of RAM consumed by the graphical interface is a megabyte stolen from your virtual machines. Furthermore, installing the full GUI significantly increases the server’s attack surface and demands far more frequent reboot cycles due to mandatory patch installations.
The industry best practice is to deploy Windows Server Core, which provides a minimal, command-line only footprint. However, managing Hyper-V on a Server Core installation requires configuring the host for complete headless remote management, allowing administrators to utilise the graphical Hyper-V Manager MMC snap-in from a separate Windows 11 client workstation.
Initial Server Core Configuration via Sconfig
Upon booting your fresh Windows Server Core installation, you are presented with a simple command prompt. Before any remote management can occur, you must configure the fundamental networking and domain settings. Type sconfig and press Enter to launch the Server Configuration tool.
Within Sconfig, perform the following essential steps:
- Assign a static IPv4 address, subnet mask, and default gateway to ensure the host remains accessible.
- Configure the DNS server addresses to point to your Active Directory domain controllers.
- Rename the computer to your designated naming convention and reboot.
- Re-enter Sconfig and join the server to your Active Directory domain. This step is critical; while workgroup remote management is possible, it requires complex CredSSP and WinRM configuration that is best avoided in enterprise environments.
Installing the Hyper-V Role via PowerShell
Once the server is domain-joined and rebooted, log in using your Domain Administrator credentials. You must install the Hyper-V role and its necessary dependencies. Launch PowerShell by typing powershell in the command prompt.
Execute the following command to install the virtualization hypervisor:
Install-WindowsFeature -Name Hyper-V -IncludeManagementTools -Restart
The -Restart parameter ensures the server automatically reboots to apply the hypervisor layer beneath the operating system. When the server comes back online, it is officially a functioning Hyper-V host, but it is not yet fully configured for remote access.
Enabling Remote Management and Firewall Rules
By default, Windows Server Core restricts remote incoming connections to ensure security. To manage this host from your Windows 11 administrative workstation, you must enable Remote Management and open the specific firewall ports required by the Hyper-V Management console.
Return to the PowerShell prompt and verify that Windows Remote Management (WinRM) is active:
Enable-PSRemoting -Force
Next, you must enable the specific firewall rule groups that permit the remote MMC snap-ins to communicate with the host. Execute the following commands:
Enable-NetFirewallRule -DisplayGroup "Remote Administration"
Enable-NetFirewallRule -DisplayGroup "Hyper-V Management"
Enable-NetFirewallRule -DisplayGroup "Windows Management Instrumentation (WMI)"
Connecting via RSAT on Windows 11
With the Server Core host fully prepared, shift your focus to your Windows 11 administrative workstation. You must have the Remote Server Administration Tools (RSAT) installed. Navigate to Settings, Apps, Optional Features, and install the “RSAT: Hyper-V Management Tools”.
Launch the Hyper-V Manager application on your Windows 11 client. In the left-hand navigation pane, right-click “Hyper-V Manager” and select “Connect to Server”. Enter the fully qualified domain name (FQDN) of your Server Core host. Because both machines belong to the same Active Directory domain, Kerberos authentication handles the security transparently.
You now have a fully graphical, remote management interface to create virtual switches, provision new virtual machines, and monitor performance, while your underlying Server Core host remains incredibly lightweight, secure, and entirely headless.