Category: Hyper-V

Hyper-V

Windows NT4 / 2000 Server and Workstation on a 2019 Hyper-V Cluster

Sometimes it’s necessary to install an old Operating System, but you really cannot (or don’t want to) get the old hardware out, even if it would still work.
I was in such a position that I had to install Windows 2000 Server. After locating the installation media, I decided it was a good idea to get it running on the 2019 Hyper-V cluster. This actually can be done, but there are a few hoops to jump through.

Update: This was written with Windows 2000 Adv. Server in mind, but I’ve since discovered the same procedure works for Windows NT4 with SP6a slipstreamed.

Read More “Windows NT4 / 2000 Server and Workstation on a 2019 Hyper-V Cluster”

Hyper-V

Force Remove Host from SCVMM 2016/2019 & Hyper-V Console

To remove from SCVMM:

Open PowerShell with administrative credentials:

PS C:\> $Credential = Get-Credential
PS C:\> $VMHost = Get-SCVMHost -ComputerName “<Hostname of Server here>”
PS C:\> Remove-SCVMHost -VMHost $VMHost -Credential $Credential

The Get-Credential cmd-let will open a prompt in which you have to supply credentials with the rights to remove the host. In the second line you specify the server. This doesn’t have to be the FQDN, the Netbios name will do.
The last line actually removes the server. This may take a few minutes, depending if the server responds or not. If the server does not respond, PowerShell waits for a time-out.

To remove from a Hyper-V console:

Open PowerShell with administrative credentials:

PS C:\> Get-VM
PS C:\> Remove-VM -name [“VM Name Here”] -force

Use this to remove VMs that are in the state of SavedCritical. The “Get-VM” command will show a list of VMs registered on this Hyper-V server. The Saved-Critical VMs will list there too. Make sure the -force is added or it won’t do the trick. If your machine name has spaces, use the quotes (without the square brackets of course].

This was tested on Server 2016 and Server 2019. It’s also expected to work on later server releases.