← Back to dashboard

Microsoft Hyper-V Integration

Audience: operator · Profile: demo · Read this when: your VMs live on Hyper-V and you want them managed from here.

What is it?

The Hyper-V integration connects the dashboard to a Windows host running Microsoft Hyper-V via WinRM (Windows Remote Management). It executes PowerShell Hyper-V module cmdlets remotely — no agent required on the host — and adds a Hyper-V tab to the dashboard where you can list all VMs, inspect their state and configuration, and control power.

Use cases

• On-premises Windows Server management — control VMs on Windows Server Hyper-V hosts alongside cloud resources from a single dashboard.
• Dev/test lab management — start and stop VMs on a Windows 10/11 developer workstation running Hyper-V.
• Unified on-prem + cloud view — see Hyper-V VMs next to AWS EC2, Azure VMs, Proxmox, and vSphere resources in one screen.

Prerequisites

Setup

Step 1 — Enable WinRM on the Hyper-V host

Open PowerShell as Administrator on the Hyper-V host and run:

Enable-PSRemoting -Force

This enables the WinRM service, sets it to start automatically, and creates a default HTTP listener on port 5985.

For a workgroup (non-domain) host, also run:

Set-Item WSMan:\localhost\Client\TrustedHosts -Value "<dashboard-ip>" -Force

Replace <dashboard-ip> with the IP or hostname of the machine running the dashboard container.

Step 2 — Create a service account (optional but recommended)

Using a dedicated local account avoids giving the dashboard full Administrator access:

# Create a local account
$pw = ConvertTo-SecureString "ChangeMe123!" -AsPlainText -Force
New-LocalUser -Name "dashboard-svc" -Password $pw -FullName "Dashboard Service" -PasswordNeverExpires

# Add to the Hyper-V Administrators group (read + power control)
Add-LocalGroupMember -Group "Hyper-V Administrators" -Member "dashboard-svc"

# Add to Remote Management Users so WinRM accepts the account
Add-LocalGroupMember -Group "Remote Management Users" -Member "dashboard-svc"

For a domain-joined host, use an Active Directory service account instead of a local account and ensure it is a member of the Hyper-V Administrators built-in group on each host.

Step 3 — Enable and configure in the dashboard

Turning it on sets the hyperv_enabled feature flag, and the Hyper-V page appears in the navigation at /hyperv.

Turn it on in Settings → Integrations → Microsoft Hyper-V.

Then add the connection on the Connections tab of the Remote Agents page (/connections) → Add connection, kind Hyper-V. That is where connection details have lived since a dashboard could hold more than one of each kind; see Multiple connections.

Click Save. No container restart is required. For a Hyper-V the dashboard cannot reach, tick Reached through a remote agent instead; see Over a remote agent.

The old Settings → Integrations → Microsoft Hyper-V fields (hyperv_host, hyperv_port, hyperv_username, hyperv_password, hyperv_transport, hyperv_use_ssl, hyperv_verify_ssl) are read only as a fallback while no Hyper-V connection exists, and were copied into the first connection on upgrade. Editing them after that changes nothing.

Step 4 — Verify

The Hyper-V link appears in the navigation menu (the ☰ button in the top bar). Click it — you should see your VMs listed within a few seconds.

What it enables in the dashboard

Tags. Hyper-V has no native tag concept, so VMs here show no tag chips. See Cloud VMs — Tags and labels.

Scheduling power. On a connection bound to a remote agent, the bulk power toolbar's Schedule tick books the operation for a time or a change window. A directly dialled connection cannot be booked, and each of its VMs is refused by name. See Scheduling.

Integration Services

Integration Services (IS) is the Hyper-V equivalent of VMware Tools. When IS are installed and running inside the guest, the dashboard can:

• Show IP addresses for the VM
• Perform graceful shutdown (the Shutdown button is disabled when IS are absent)

To install IS in a Linux VM, ensure the hyperv-daemons package is installed:

# Debian / Ubuntu
apt-get install -y hyperv-daemons

# RHEL / Rocky / AlmaLinux
dnf install -y hyperv-daemons

# SUSE
zypper install -y hyper-v

Windows guest VMs include IS built-in on modern Windows versions. If IS appear as "not installed" on a Windows VM, run Windows Update inside the guest.

The dashboard shows the IS state as: - Up to date — IS running and current (graceful shutdown available) - Update available — IS running but outdated (graceful shutdown still works) - Not installed — IS absent (graceful shutdown button disabled)

Power operations reference

Auth transport options

For most setups, NTLM over HTTP (port 5985) is the right choice. Switch to HTTPS if the network between the container and the Hyper-V host is untrusted.

HTTPS / WinRM over SSL (optional)

To use WinRM over HTTPS (port 5986), the Hyper-V host needs a certificate. For a lab, you can create a self-signed cert and bind it to the WinRM listener:

# Create a self-signed cert valid for 3 years
$cert = New-SelfSignedCertificate -DnsName "hyperv.corp.local" `
    -CertStoreLocation Cert:\LocalMachine\My `
    -NotAfter (Get-Date).AddYears(3)

# Create an HTTPS listener
New-WSManInstance WinRM/Config/Listener `
    -SelectorSet @{Address="*"; Transport="HTTPS"} `
    -ValueSet @{CertificateThumbprint=$cert.Thumbprint}

# Open the HTTPS port in the firewall
New-NetFirewallRule -Name "WinRM HTTPS" -DisplayName "WinRM HTTPS" `
    -Protocol TCP -LocalPort 5986 -Action Allow

In the dashboard: set Port to 5986, enable Use HTTPS, and disable Verify SSL (for self-signed), or enable it if using a CA-signed cert.

Troubleshooting

Hyper-V tab is missing — verify HYPERV_ENABLED=true and that the stack restarted after the change (or that you saved via Settings → Integrations).

"no hyperv connection is configured — add one on the Connections page" — add a Hyper-V connection on the Connections tab of the Remote Agents page (/connections).

"pywinrm is not installed" — run pip install pywinrm inside the container or rebuild the image: docker compose build app.

"Connection refused" (port 5985) — WinRM is not listening. Run Enable-PSRemoting -Force on the host. Check the firewall:

Get-NetFirewallRule -Name "WINRM-HTTP-In-TCP*" | Select Enabled

"401 Unauthorized" — username or password is wrong, or NTLM is blocked. Verify credentials with: Test-WSMan -ComputerName hyperv.corp.local -Credential (Get-Credential).

"WinRM cannot process the request" (workgroup host) — add the dashboard server's IP to TrustedHosts on the Hyper-V host:

Set-Item WSMan:\localhost\Client\TrustedHosts -Value "*" -Force

(Replace * with the specific dashboard IP for a more restrictive setting.)

"Access is denied" on power operations — the account is not in the Hyper-V Administrators group. Add it:

Add-LocalGroupMember -Group "Hyper-V Administrators" -Member "dashboard-svc"

IP addresses not showing — install hyperv-daemons (Linux) or update IS (Windows) inside the guest. IP discovery requires Integration Services.

Slow VM list — each refresh opens a WinRM connection and runs a PowerShell script. On hosts with many VMs (50+), the list script may take 5–10 seconds. The dashboard shows a spinner during the load.

Multiple connections

Connection details used to live in Settings as a single set of fields, so there could only ever be one Hyper-V host. They now live on the Connections tab of the Remote Agents page (/connections), which holds as many as you like — a second Hyper-V host at another site, or the same one under a read-only and a privileged service account.

• The default connection is what every page and API call uses when not told otherwise. The first connection of a kind becomes the default automatically.
• Pass ?connection_id=<id> to any /api/hyperv endpoint to target a specific one.
• Job-backed operations (deploys, power verbs) record the connection at enqueue, so changing the default while one is queued cannot redirect it.

Your existing Settings values were copied into the first connection on upgrade. The old panel is still there, read-only, with a banner pointing here — editing it no longer changes what the dashboard connects to. It is kept so that rolling back to a previous image still works.

Over a remote agent

Hyper-V is not available over a remote agent. WinRM is SOAP with NTLM/Negotiate, and a real authentication stack is the one transport the agent's deliberately minimal dependency set cannot provide — it installs requests, PyYAML and cryptography and nothing else, which two audit tests enforce because that restraint is the security argument.

So a Hyper-V host has to be somewhere the dashboard can reach. Every other hypervisor here can go through an agent; see remote agents.

A remote agent's discovery scan will report WinRM on 5985/5986, but marked possible only: nearly every domain-joined Windows Server answers there and the overwhelming majority are not hypervisors. Only credentials can tell you which is which.

When the connection is reached through an agent

The dashboard has no route to an agent-bound connection — that is the point of binding it to an agent — so this page cannot query it live. It shows the last synced inventory instead, with a banner saying so and how old it is. Live-only figures (CPU usage, uptime, disk) are blank there rather than zero: they were never measured, and a fabricated 0 is worse than an empty cell.

Power actions still work: they are dispatched to the agent as jobs and appear on /jobs with Live Output, exactly like a discovery scan. Start, Force Off, Shutdown and Restart all map to a verb; Pause, Resume and Save do not, and are refused with a 501 naming what is available rather than approximated onto a neighbouring operation — see the verbs.

Shutdown is the one that needs the guest. It runs bare Stop-VM, which shuts down through the guest operating system — not -TurnOff (the power cut) and not -Force, which on Stop-VM means "regardless of any unsaved application data". The synced inventory carries no Integration Services state, so the button is offered rather than hidden — and no "⚠ No Integration Services" badge is shown either, since the sync never measured it — and the host is what answers if Integration Services is not running.