Hyper-converged solution in Windows Server
  • Introduction
  • Intro
    • Introduction
    • Requirements
    • Topology
  • Preparing the servers
    • Server 1: The Domain Controller
    • Prepping the 2 HC servers
    • Server 2: HyperConvergence 1
    • Server 3: HyperConvergence 2
  • Set up the Fail over cluster with storage spaces direct
    • Test the cluster
    • Build the cluster
    • Add a cluster witness
    • Clean the disks
    • Enable storage spaces direct
    • Create cluster-volumes
  • Setup Hyper-V and test
    • The next steps
    • Edit Hyper-V Paths
    • Create a High Available VM
    • Test it
    • Where to go from here
  • Extra
    • Add a 3rd node
Powered by GitBook
On this page

Was this helpful?

  1. Setup Hyper-V and test

Create a High Available VM

PreviousEdit Hyper-V PathsNextTest it

Last updated 5 years ago

Was this helpful?

Via the Cluster configuration manager, you can create a high available VM. After selecting a node, everything proceeds as you would normally configure a VM, only now it's immediatly High Available.

I'm not sure myself what caused this option to appear. Is it the cluster manager detecting the Hyper-V services on the nodes?

I'm installing a Generation 1, Windows 7 machine of which the iso is already copied to the clustered volume. After which you get a "VM-ception": Windows 7-VM on a Server 2016-VM on a Windows 10 host.