Hyper-V is Microsoft's built-in virtualization platform, included free with Windows Server, letting you run multiple independent virtual servers on a single physical server — exactly what sits behind most modern enterprise infrastructure. Let's install it and build our first VM together.
Hardware prerequisite
The server's CPU needs to support hardware virtualization (Intel VT-x or AMD-V), and this must be enabled in BIOS/UEFI — if you installed Hyper-V but get an error when creating a VM, this BIOS setting is the first thing to check.
Step 1: Install the Hyper-V role
From Server Manager, go to Add Roles and Features. Under Server Roles, check Hyper-V. The system will ask you to create a Virtual Switch (to connect VMs to the network) — select the target network card. Installation finishes, but the server needs to Restart for Hyper-V to become active.
Step 2: Open Hyper-V Manager
After the restart, from Server Manager go to Tools > Hyper-V Manager. This window manages all of the server's virtual machines.
Step 3: Create a new virtual machine
Right-click the server name and select New > Virtual Machine. In the wizard:
Enter a name for the VM — e.g., "Test-Server-01."
Choose the VM generation (Generation 2 is recommended for newer operating systems).
Specify the RAM allocation (e.g., 4096 MB).
Select the Virtual Switch you created in step 1 so the VM has network access.
Create a new virtual hard disk and set its size (e.g., 60 GB).
Point it to the ISO file of the target operating system (e.g., Windows Server or Linux) for installation.
Step 4: Power on and install the OS
Right-click the created VM and click Connect to open its virtual screen. Then click Start — from here, exactly like a physical computer, the OS boots and installs from the ISO file.
Step 5: Manage resources (optional but important)
From each VM's Settings window, you can change RAM, virtual CPU count, and disk space at any time — this flexibility is one of virtualization's biggest advantages over physical servers.
Why does Hyper-V matter?
Instead of buying a separate physical server for every service (one for AD, one for files, one for web), you can run them all as independent virtual machines on a single powerful piece of hardware — a huge cost reduction and a big increase in flexibility. This is exactly what's taught in full detail in my MCSA and virtualization courses.
Blog