Microsoft Hyper-V Server 2019 is a free product that delivers enterprise-class virtualization for your datacenter and hybrid cloud. Microsoft Hyper-V Server 2019 provides new and enhanced features that can help you deliver the scale and performance needs of your mission-critical workloads.

Detailed instructions can be found here:
https://www.youtube.com/watch?v=_j88dLq7Wr0&t=11s

Requirements can be found here:
https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/system-requirements-for-hyper-v-on-windows

You can download the ISO from here:
https://www.microsoft.com/en-us/evalcenter/evaluate-hyper-v-server-2019

Installation Guidelines

• Upon installation you will be prompted to activate.
• A product key is not required.

First we have to enable communication between the two servers…. Click to open

There is a great free tool you can use, which we highly recommend:

Probus IT Home – Hyper-V Manager ProHVM and more… (probus-it.com)

After a client’s power failure where the UPS failed to properly  shutdown the Hyper-V Server, VMs were not able to start. 

See below for the error we got every time we tried to start a VM:

Start-vm : ‘win-8-mngmt’ failed to restore virtual machine state. (Virtual

Machine ID B790B331-90AD-4D68-B2B4-34B604F849A2)

Virtual machine ‘win-8-mngmt’ could not be started because the hypervisor is

not running (Virtual machine ID B790B331-90AD-4D68-B2B4-34B604F849A2).

the following actions may help you resolve the problem:

(1) Verify that the processor of the physical computer has a supported version

if hardware-assisted virtualization.

(2) Verify that hardware-assisted virtualization and hardware-assisted data

execution protection are enabled in the BIOS of the physical computer.  (If

you edit the BIOS to enable either setting, you must turn off the power to the

physical computer and then turn it back on.  Resetting the physical computer

is not sufficient.)

(3) If you have made changes to the Boot Configuration Data store, review these

hanges to ensure that the hypervisor is configured to launch automatically.

All VMs were on a saved status and were not able to start.
The Hyper-V’s version was 2012R2.

For our case it seemed that updates that were already installed and run after the reboot of the server created the problem:
The following updates caused the issue: KB5009624 and KB5009624.
So here it is how to uninstall them from command line:

wusa /uninstall /kb:5009624

wusa /uninstall /kb:5009595

Just to be on the safe side, download and install hotfix KB5010794 which fixes this bug.

You must download it manually from the Microsoft Update Catalog.

Download and install from within Hyper-V from this link:

https://www.catalog.update.microsoft.com/Search.aspx?q=KB5010794

In case you want to remove and re install the hyper-V feature use the following Power Shell commands:

Remove-WindowsFeature -Name Hyper-V

Install-WindowsFeature -Name Hyper-V

Start your Hyper-V Manager , right click over your server and select “Import Virtual Machine”:

Browse to the location of the backup folder:

Select the Virtual Machine to Restore:

Select “Register…” when you restoring to a new server or “Restore…” for restoring to the same server:

This is a bit tricky, first locate where your Virtual Disks are located:

Then select the same folder:

If you get a similar error just select the “Default Switch”:

Click “Finish” to start the restore:

Your VM is now restored/registered to your Hyper-V:

And it’s also visible from Synergy HyperV Backup:

At the prompt, type the following command, and then press Enter:
wmic

You’ll now see the wmic:root\cli> prompt in the console. This means you can now use Windows Management Instrumentation (WMI) operations.

Next, you’ll want a list of the programs installed on your computer. Getting this list is essential because you must provide an accurate product name to successfully execute the uninstall command.
Type the following command to get the list:
product get name

Find the name of the program you want to uninstall from the list. You can uninstall the program by running this command:
product where name=”synergy hyperv backup” call uninstall

We checked one of our old Hyper-V Servers (Hypervisor mode) using Nessus and we came up with the following issue:

Remote Desktop Protocol Server Man-in-the-Middle Weakness

Description
The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials.
This flaw exists because the RDP server stores a publicly known hard-coded RSA private key. Any attacker in a privileged network location can use the key for this attack.

Solution
– Force the use of SSL as a transport layer for this service if supported, or/and
– On Microsoft Windows operating systems, select the ‘Allow connections only from computers running Remote Desktop with Network Level Authentication’ setting if it is available.

Plugin Details
Severity:Medium
ID:18405
Version:1.34
Type:remote
Family:General
Published:June 1, 2005
Modified:August 24, 2022

For more info here: https://www.tenable.com/plugins/nessus/18405

So here is how you can fix it. Issue the following command from Powershell:

(Get-WmiObject -class “Win32_TSGeneralSetting” -Namespace root\cimv2\terminalservices -ComputerName $env:computername -Filter “TerminalName=’RDP-tcp'”).SetUserAuthenticationRequired(1)
 

(make sure double quotes are properly pasted in your command line)

You can achieve this using PowerShell with the Set-VM cmdlet. The command to mark a VM to auto-start is:

Set-VM -Name ‘Your_VM_Name’ -AutomaticStartAction Start

To view the current settings for all VMs, you can use:

Get-VM | Select-Object Name, AutomaticStartAction

If you encounter an issue for reasons that are not immediately clear, you can proceed with the following steps:

Step 1:

Save the following powershell script to a location, for exampke : c:\scripts\StartYourVMName.ps1

# Wait for 90 seconds
Start-Sleep -Seconds 90

# Start the Hyper-V VM
Start-VM -Name YourVMName

Step 2.

Create a task schedule, from command line, to start the script when the server starts. It will run whether the admin logs or not:

schtasks /create /tn “StartYourVMName” /tr “powershell.exe -File C:\Scripts\StartYourVMName.ps1” /sc onstart /RU “administrator” /RP “password”

Reboot your server, and your virtual machine will start 90 seconds following the operating system’s startup.

Hyper-V lacks a built-in feature comparable to VMware’s boot order functionality. So here is how to do the same:

Step 1.

Save the following command to PowerShell script, for example c:\scripts\VMStartOrder.ps1
Change delay and VM names as you wish.

# Start the first VM
Start-VM -Name ‘VM1’

# Wait for 30 seconds
Start-Sleep -Seconds 30

# Start the second VM
Start-VM -Name ‘VM2’

# Wait for another 30 seconds
Start-Sleep -Seconds 30

# Start the third VM
Start-VM -Name ‘VM3’

Step 2.

Create a schedule task from command line. It will run whether the admin logs or not:

schtasks /create /tn “VMStartOrder” /tr “powershell.exe -File ‘C:\scripts\VMStartOrder.ps1′” /sc onstart /RU “administrator” /RP “password”

Reboot your server to test.