How to Create a Hyper-V Cluster in Active Directory Domain with Windows Server 2025

Before creating the cluster, you need to prepare your Active Directory environment. This involves creating a dedicated organizational unit and pre-staging the Cluster Name Object (CNO) to avoid permission issues during cluster creation.

First, create an OU for your cluster objects. Open Active Directory Users and Computers and create a new OU called "Hyper-V Clusters".

Next, pre-stage the CNO as a computer object in this OU:

New-ADComputer -Name "HV-CLUSTER01" -Path "OU=Hyper-V Clusters,DC=yourdomain,DC=com" -Enabled $false -Description "Hyper-V Cluster Name Object"

Grant your cluster nodes permission to act on behalf of the CNO:

$ClusterNodes = @("HV-NODE01", "HV-NODE02")
foreach ($Node in $ClusterNodes) {
    $NodeAccount = Get-ADComputer $Node
    $CNO = Get-ADComputer "HV-CLUSTER01"
    Set-ADComputer -Identity $CNO -PrincipalsAllowedToDelegateToAccount $NodeAccount
}

Install the required Windows features on all cluster nodes. This step must be completed on each server that will participate in the cluster.

Run this command on each node to install Hyper-V and Failover Clustering:

Install-WindowsFeature -Name Hyper-V, Failover-Clustering -IncludeManagementTools -Restart

After the restart, configure the cluster service and Hyper-V settings:

Set-Service -Name ClusSvc -StartupType Automatic
Enable-VMMigration
Set-VMMigrationNetwork "192.168.2.0" -Priority 1
Set-VMHost -VirtualMachineMigrationPerformanceOption SMB
Set-VMHost -VirtualMachinePath "C:\ClusterStorage\Volume1\VMs"
Set-VMHost -VirtualHardDiskPath "C:\ClusterStorage\Volume1\VHDs"
Set-VMHost -EnableEnhancedSessionMode $true

These commands configure live migration to use SMB for better performance and set default paths for VMs and virtual hard disks on the cluster shared volume.

Proper network configuration is critical for cluster stability. You need separate networks for cluster heartbeat, management, and live migration traffic.

Configure network adapters on each node with static IP addresses:

# Management Network (Node 1)
New-NetIPAddress -InterfaceAlias "Management" -IPAddress "192.168.1.10" -PrefixLength 24 -DefaultGateway "192.168.1.1"
Set-DnsClientServerAddress -InterfaceAlias "Management" -ServerAddresses "192.168.1.5"

# Live Migration Network (Node 1)
New-NetIPAddress -InterfaceAlias "LiveMigration" -IPAddress "192.168.2.10" -PrefixLength 24

For Node 2, use .11 and .11 respectively. Repeat for additional nodes, incrementing the last octet.

Configure network adapter priorities to ensure proper traffic routing:

Set-NetIPInterface -InterfaceAlias "Management" -InterfaceMetric 10
Set-NetIPInterface -InterfaceAlias "LiveMigration" -InterfaceMetric 20

Disable NetBIOS on the live migration network to reduce broadcast traffic:

$adapter = Get-WmiObject -Class Win32_NetworkAdapterConfiguration | Where-Object {$_.Description -like "*LiveMigration*"}
$adapter.SetTcpipNetbios(2)  # 2 = Disable NetBIOS

Before creating the cluster, run the cluster validation wizard to identify potential issues. This step helps prevent cluster creation failures and ensures your hardware configuration meets Microsoft's requirements.

Run the validation test from one of the cluster nodes:

Test-Cluster -Node "HV-NODE01","HV-NODE02" -Include "Inventory","Network","System Configuration"

If you haven't configured shared storage yet, skip storage tests to avoid false failures:

Test-Cluster -Node "HV-NODE01","HV-NODE02" -Ignore "Storage"

Review the validation report carefully. Address any errors before proceeding. Common warnings you can typically ignore include:

• Missing shared storage (if not configured yet)
• Network adapter teaming warnings (if using different hardware)
• BIOS version differences (if functionality is equivalent)

For detailed validation results, check the report file:

$Report = Get-ChildItem "$env:TEMP\*Validation*.htm" | Sort-Object LastWriteTime -Descending | Select-Object -First 1
Invoke-Item $Report.FullName

With validation complete, create the failover cluster. This step establishes the cluster infrastructure and makes your nodes work together as a single highly available system.

Create the cluster without storage initially (we'll add storage in the next step):

New-Cluster -Name "HV-CLUSTER01" -Node @("HV-NODE01","HV-NODE02") -StaticAddress "192.168.1.100" -NoStorage

Configure cluster networks with appropriate roles:

# Set management network role
Get-ClusterNetwork | Where-Object {$_.Address -like "192.168.1.*"} | Set-ClusterNetwork -Name "Management" -Role ClusterAndClient

# Set live migration network role
Get-ClusterNetwork | Where-Object {$_.Address -like "192.168.2.*"} | Set-ClusterNetwork -Name "LiveMigration" -Role ClusterOnly

Configure cluster properties for optimal Hyper-V operation:

# Set cluster heartbeat settings
(Get-Cluster).SameSubnetDelay = 1000
(Get-Cluster).SameSubnetThreshold = 10
(Get-Cluster).CrossSubnetDelay = 1000
(Get-Cluster).CrossSubnetThreshold = 10

# Enable cluster shared volumes
Enable-ClusterS2D -Confirm:$false

Shared storage is essential for VM high availability. Configure your iSCSI, SAN, or SMB storage to be accessible from all cluster nodes, then add it to the cluster.

If using iSCSI storage, configure the initiator on each node:

# Configure iSCSI initiator (run on each node)
Set-Service -Name MSiSCSI -StartupType Automatic
Start-Service MSiSCSI
New-IscsiTargetPortal -TargetPortalAddress "192.168.3.100"
Connect-IscsiTarget -NodeAddress "iqn.2024-01.com.company:storage.target1"

Add available shared disks to the cluster:

# Discover and add shared storage
$SharedDisks = Get-ClusterAvailableDisk
$SharedDisks | Add-ClusterDisk

# Convert to Cluster Shared Volumes
$ClusterDisks = Get-ClusterResource | Where-Object ResourceType -eq "Physical Disk"
$ClusterDisks | Add-ClusterSharedVolume

Format the CSV volumes if they're new disks:

# Format CSV volumes (only for new disks)
Get-ClusterSharedVolume | ForEach-Object {
    $CSVPath = $_.SharedVolumeInfo.FriendlyVolumeName
    if ((Get-Volume -Path $CSVPath).FileSystem -eq "Unknown") {
        Format-Volume -Path $CSVPath -FileSystem NTFS -AllocationUnitSize 65536 -NewFileSystemLabel "CSV$($_.Id)"
    }
}

Create directory structure for VMs:

New-Item -Path "C:\ClusterStorage\Volume1\VMs" -ItemType Directory -Force
New-Item -Path "C:\ClusterStorage\Volume1\VHDs" -ItemType Directory -Force

Quorum configuration determines how the cluster maintains consensus when nodes fail. For a two-node cluster, you need a witness to prevent split-brain scenarios.

For clusters with shared storage, configure a disk witness:

# Create a small disk for quorum (1GB minimum)
$QuorumDisk = Get-ClusterAvailableDisk | Where-Object {$_.Size -lt 5GB} | Select-Object -First 1
if ($QuorumDisk) {
    $QuorumDisk | Add-ClusterDisk
    Set-ClusterQuorum -DiskWitness $QuorumDisk.Name
}

Alternatively, configure a file share witness if you have a separate file server:

# Configure file share witness
Set-ClusterQuorum -FileShareWitness "\\fileserver.domain.com\ClusterWitness\HV-CLUSTER01"

For cloud deployments, you can use a cloud witness (Azure storage account):

# Configure cloud witness (requires Azure storage account)
Set-ClusterQuorum -CloudWitness -AccountName "yourstorageaccount" -AccessKey "your-access-key"

Verify quorum configuration and test failover scenarios:

# Check quorum status
Get-ClusterQuorum

# Test quorum by simulating node failure
Stop-ClusterNode -Name "HV-NODE02" -Force
Get-ClusterNode  # Should show NODE01 as Up, NODE02 as Down
Start-ClusterNode -Name "HV-NODE02"

Now create virtual machines that can automatically failover between cluster nodes. This is the primary benefit of your Hyper-V cluster setup.

Create a new VM on the cluster shared volume:

# Create a new VM
$VMName = "TestVM01"
New-VM -Name $VMName -MemoryStartupBytes 2GB -Path "C:\ClusterStorage\Volume1\VMs" -NewVHDPath "C:\ClusterStorage\Volume1\VHDs\$VMName.vhdx" -NewVHDSizeBytes 40GB

# Configure VM settings
Set-VM -Name $VMName -ProcessorCount 2 -DynamicMemory -MemoryMinimumBytes 1GB -MemoryMaximumBytes 4GB
Add-VMNetworkAdapter -VMName $VMName -SwitchName "External"

# Make the VM highly available
Add-ClusterVirtualMachineRole -VMName $VMName

Test live migration between nodes:

# Start the VM
Start-VM -Name $VMName

# Check current owner
Get-ClusterGroup -Name $VMName | Select-Object Name, OwnerNode

# Perform live migration
Move-ClusterVirtualMachineRole -Name $VMName -Node "HV-NODE02"

# Verify migration completed
Get-ClusterGroup -Name $VMName | Select-Object Name, OwnerNode

Test failover scenarios by simulating node failures:

# Test automatic failover
$CurrentOwner = (Get-ClusterGroup -Name $VMName).OwnerNode
Stop-ClusterNode -Name $CurrentOwner -Force

# Wait for failover (should be automatic)
Start-Sleep -Seconds 30
Get-ClusterGroup -Name $VMName | Select-Object Name, OwnerNode, State

# Restart the failed node
Start-ClusterNode -Name $CurrentOwner

Configure VM monitoring for automatic restart on failure:

# Enable VM monitoring
Add-ClusterVMMonitoredItem -VirtualMachine $VMName -Service "Spooler"
Get-ClusterVMMonitoredItem -VirtualMachine $VMName

Set up monitoring and maintenance procedures to ensure your cluster remains healthy and performs optimally over time.

Configure cluster logging for troubleshooting:

# Enable cluster logging
Get-ClusterLog -Destination "C:\ClusterLogs" -TimeSpan 60

# Configure automatic log collection
Set-ClusterParameter -Name ClusterLogLevel -Value 3
Set-ClusterParameter -Name ClusterLogSize -Value 1024

Set up performance monitoring:

# Create performance counter data collector
$DataCollectorSet = "Hyper-V Cluster Performance"
logman create counter $DataCollectorSet -f bincirc -max 500 -c "\Hyper-V Hypervisor\*" "\Cluster CSV File System\*" "\Process(vmms)\*" -si 00:01:00

Configure cluster-aware updating for automated patching:

# Install Cluster-Aware Updating feature
Install-WindowsFeature -Name RSAT-Clustering-CmdInterface, RSAT-Clustering-PowerShell

# Configure CAU self-updating mode
Add-CauClusterRole -ClusterName "HV-CLUSTER01" -MaxFailedNodes 0 -RequireAllNodesOnline

# Set update schedule (first Tuesday of each month at 3 AM)
Set-CauClusterRole -ClusterName "HV-CLUSTER01" -StartDate "2026-04-01 03:00:00" -DaysOfWeek Tuesday -WeeksOfMonth First

Create maintenance scripts for regular health checks:

# Cluster health check script
function Test-ClusterHealth {
    $Results = @{}
    $Results.ClusterStatus = (Get-Cluster).State
    $Results.NodeStatus = Get-ClusterNode | Select-Object Name, State
    $Results.ResourceStatus = Get-ClusterResource | Where-Object State -ne "Online" | Select-Object Name, State, OwnerNode
    $Results.CSVStatus = Get-ClusterSharedVolume | Select-Object Name, State
    $Results.QuorumStatus = Get-ClusterQuorum
    return $Results
}

# Run health check
$Health = Test-ClusterHealth
$Health | ConvertTo-Json -Depth 3