How to Install Hyper-V on a Dedicated Server (Bare Metal Guide)

Introduction : The "Bare Metal" Problem

So, you have your new, powerful bare metal dedicated server from ServerMO. You're ready to turn it into a virtualization powerhouse using Microsoft's Hyper-V. But when you search for a guide, you find a major problem. Almost every tutorial online starts at "Step 5": "First, open Server Manager on Windows..." They all assume you already have an operating system installed. But you have a bare metal machine. How do you get from an empty server to a running Hyper-V instance? This is that guide.

We will walk you through the entire process from Step 0. This is the true bare metal, dedicated server method. We will cover:

1. Phase 1 (Pre-Install): Choosing your Hyper-V version and mounting the ISO via IPMI/KVM. (The step everyone else skips).
2. Phase 2 (OS Install): Installing the base Windows Server OS.
3. Phase 3 (Role Install): Configuring the Hyper-V role using both the GUI and PowerShell.
4. Phase 4 (Post-Install): Setting up your first virtual network.

Phase 1: Pre-Installation & Planning

Before we start, we have to make two critical decisions and prepare our server for the installation.

Step 1: Decide Your Hyper-V Path (Critical Choice)

This is the most important decision. "Hyper-V" isn't just one product. You have two main choices:

Choice A: Windows Server (with Hyper-V Role) - (Recommended Path)

• What it is:You first install the full Windows Server 2022 (or 2025) operating system. Then, you simply "turn on" the Hyper-V Role from inside the OS.
• Pros:
  • Flexible: You get the full power of Windows Server (file storage, Active Directory, etc.) plus virtualization.
  • Easy to Manage: You can use the familiar Server Manager GUI.
• Cons:Costs a Windows Server license (though you can start with the 180-day evaluation).

Choice B: Microsoft Hyper-V Server (Standalone)

• What it is:A free, lightweight, command-line-only version that only includes the Hyper-V hypervisor.
• Pros: It's free and has a tiny footprint (less security risk).
• Cons:
  • Extremely basic:: It has no GUI. It's only for virtualization.
  • Difficult to manage: You must manage it remotely using PowerShell or Hyper-V Manager from another PC.
  • No future: Microsoft has discontinued this product after 2019.

ServerMO Expert Recommendation: We strongly recommend Choice A: Windows Server (with Hyper-V Role). It gives you the best balance of power, flexibility, and ease of use. This guide will focus on that path.

Step 2: Decide Your Windows Server Type (GUI vs. Core)

After choosing "Windows Server" (Choice A), you have one more decision when you install it:

• Desktop Experience (GUI) : This is the normal Windows you are used to, with a Start menu, icons, and a mouse. It's easy for beginners.
• Server Core : This is a minimal, command-line-only installation. It's faster, more secure, and uses fewer resources. It's the "expert" choice.

Recommendation: If you are comfortable with PowerShell, use Server Core. If you are new to this, start with Desktop Experience (GUI). Our guide will show you how to enable Hyper-V on both.

Step 3: Download the Windows Server 2022 ISO

You can get the official 180-day evaluation ISO directly from the Microsoft Evaluation Center. Download this file and save it to your local computer.

Step 4: Mount Your ISO via IPMI (The "Bare Metal" Step)

This is the "magic" step that nobody else explains. Your ServerMO dedicated server comes with a remote management console (like IPMI, iDRAC, or KVM). This lets you control the server as if you were physically standing next to it.

1. Log in to your ServerMO client area and find your server's IPMI IP address, username, and password.
2. Open that IP in your browser and log in to the IPMI interface.
3. Look for a button that says "Remote Console" or "Launch KVM". Click it.
4. A new window will open showing your server's blank screen.
5. In the menu of this console window, find "Virtual Media" or "Virtual Storage".
6. Select "CD/DVD" -> "Local ISO File".
7. Browse your computer and select the Windows Server 2022 ISO file you just downloaded.
8. Click "Mount" or "Plug In".

You have just virtually "inserted" the Windows installation disk into your bare metal server.

Phase 2: Installing the Windows Server OS (The Bare Metal Step)

In this phase, we will power on the server and install the Windows Server OS from the ISO we mounted in Phase 1. Your IPMI remote console window should still be open.

Step 1: Boot from the Virtual ISO

1. From your IPMI console, "Power On" or "Reboot" the server.
2. As the server turns on, watch the POST screen for keys like F11 (Boot Menu), F2 (Setup), or DEL (Setup).
3. Press F11 (or the equivalent key for "Boot Menu").
4. From the boot list, select the "Virtual CD/DVD" or "UEFI Virtual Optical Drive" that we mounted and press (Enter).
5. You will see a "Press any key to boot from CD or DVD..." message. Press a key immediately.

Step 2: The Windows Setup Wizard

Step 3: Select Your OS Version (GUI vs. Core)

This is a very important screen. This is where we will choose the GUI or Server Core option we decided on in Phase 1.

• Windows Server 2022 Standard
• Windows Server 2022 Standard (Desktop Experience)
• Windows Server 2022 Datacenter
• Windows Server 2022 Datacenter (Desktop Experience)
  
  ServerMO Expert Advice:
  • Server Core (Expert): Choose any version that does not say "Desktop Experience." This will be command-line only.
  • GUI (Recommended): Choose the version that ends with "(Desktop Experience)". This is the normal Windows GUI with a Start Menu.

  For this guide, we will select "Windows Server 2022 Standard (Desktop Experience)". Click "Next".

Step 4: License and Install Type

Step 5: Where to Install Windows? (Partitioning)

1. This screen will now show all the hard drives in your server. You will likely see Drive 0 Unallocated Space.
2. Select this "Drive 0".
3. Click the "New" button.
4. Leave the size as default and click "Apply".
5. A pop-up will ask if it's okay for Windows to create system partitions. Click "OK".
6. You will now see several partitions (Recovery, System, MSR). Select the largest one, which will be labeled "Primary", and click "Next".

Step 6: Installation & First Boot

Windows will now begin copying files and installing the OS. This will take several minutes (10-15 min).

The server will automatically reboot when it's finished.

Step 7: Set Administrator Password

After rebooting, Windows will ask you to set a password.

• Create a strong password for the "Administrator" user.
• Re-enter the password to confirm.
• Click "Finish".

Phase 3: Installing the Hyper-V Role

Now that our Windows Server 2022 OS is installed and running, it's time to "turn on" the Hyper-V feature. We will cover both the graphical (GUI) method and the command-line (PowerShell) method.

Method 1: The GUI Way (Using Server Manager)

This method is for those who installed the "Desktop Experience (GUI)" version of Windows Server.

Step 1: Open Server Manager

After you log in, the Server Manager dashboard will typically open automatically. If it doesn't, click the Start button and select "Server Manager".

Step 2: Launch the "Add Roles and Features" Wizard

1. On the Server Manager dashboard, in the top-right corner, click "Manage".
2. Select "Add Roles and Features" from the menu.

Step 3: Navigate the Wizard

The "Add Roles and Features Wizard" will open.

1. Before You Begin: Click "Next".
2. Installation Type: Select "Role-based or feature-based installation". Click "Next".
3. Server Selection: Your server will already be selected. Click "Next".

Step 4: Select the Hyper-V Role (Critical Step)

1. On the "Server Roles" screen, scroll down and check the box for "Hyper-V".
2. A new pop-up window, "Add features that are required for Hyper-V?", will appear. This adds the management tools. Click the "Add Features" button.
3. Back on the Server Roles screen, click "Next".

Step 5: Complete the Hyper-V Configuration

The wizard will now ask you a few questions specific to Hyper-V.

Step 6: Install and Reboot

1. On the "Confirmation" screen, check the box that says "Restart the destination server automatically if required". This is mandatory for Hyper-V.
2. A warning pop-up will appear. Click "Yes".
3. Click the "Install" button.

The server will install the features and then reboot automatically. After the reboot, the Hyper-V role will be installed and active.

Method 2: The PowerShell Way (Fast & For Server Core)

This is the fastest method and the only method if you installed "Server Core".

Step 1: Open PowerShell as Administrator

1. On GUI: Click Start, type "PowerShell", right-click it, and select "Run as administrator".
2. On Server Core: The command prompt will be open by default. Just type powershell and press Enter.

Step 2: Run the Installation Command

Type (or copy/paste) the following single command and press Enter:

[Code block showing the PowerShell command Install-WindowsFeature -Name Hyper-V -IncludeManagementTools -Restart ]

Your server will install the role and then restart.

Phase 4: Post-Installation (Configuring the Virtual Switch)

Your server has rebooted and Hyper-V is now installed. You're finished with the installation, but there's one crucial configuration step left. Your server has a physical network card that connects it to the internet. Your new Virtual Machines (VMs) can't use that card directly. We need to create a Virtual Switch to act as a bridge between your server's physical network and your new VMs. Note: If you used the GUI Wizard (Method 1) in Phase 3, you might have already created a virtual switch. If so, you can double-check its settings here. If you used the PowerShell method, you must do this step.

We will use the Hyper-V Manager GUI for this, as it's the clearest way.

Step 1: Open Hyper-V Manager

1. Click the Start button.
2. Type "Hyper-V Manager" and open it. (You can also find it in Start > Windows Administrative Tools).

Step 2: Open the Virtual Switch Manager

1. In the Hyper-V Manager tool, in the right-hand "Actions" pane, click on "Virtual Switch Manager...".

Step 3: Create the External Switch

A new window will open. This is where we create the network bridge.

1. On the left, select "New virtual network switch".
2. From the list of types, select "External". This is the only type that can connect your VMs to the outside internet.
3. Click the "Create Virtual Switch" button.

Step 4: Configure the External Switch

Now, you'll see the settings for your new switch.

Step 5: Apply Changes

1. Click "Apply".
2. You will see a warning: "Applying changes may disrupt network connectivity...". This is normal. Your server's network connection will drop for a few seconds as it reconfigures itself.
3. Click "Yes".

After a few moments, your network will come back online. You have successfully created a virtual switch.

Conclusion : Your Hyper-V Host is Ready

You have now completed the true bare metal installation, the step-by-step process that no one else shows:

1. Phase 1 : You used IPMI/KVM to mount your ISO.
2. Phase 2 : You installed the Windows Server OS on your bare metal..
3. Phase 3 : You installed the Hyper-V Role..
4. Phase 4 : You configured your External Virtual Switch so your VMs can access the internet.

Your ServerMO dedicated server is now a fully-functional Hyper-V host.

Your Next Step: Create Your First VM

You are now ready for the final step: creating your first virtual machine.

1. In Hyper-V Manager, in the "Actions" pane, click New > Virtual Machine....
2. Follow the wizard, and when it asks you to "Configure Networking", select the new External_vSwitch you just created.

Congratulations, your virtualization journey has begun!