Ordyn

Appearance

Microsoft Hyper-V VMs ​

The VMs tab shows Microsoft Hyper-V virtual machines reported by a Windows Hyper-V host endpoint.

The tab is available on endpoints marked as an Ordyn hypervisor host in Edit endpoint.

Collection ​

Use the Collect Microsoft Hyper-V VM inventory job step, or the endpoint inventory recollect action, to refresh the tab.

The agent collects Hyper-V data through the Windows Hyper-V WMI/CIM provider. It does not use PowerShell for inventory collection.

Hyper-V inventory is Windows-only. On non-Windows endpoints, the capability is not available.

VM List ​

The VM table shows:

  • VM name
  • VM ID
  • guest endpoint match
  • VM state
  • CPU count
  • assigned memory
  • uptime
  • generation
  • snapshots/checkpoints

The action menu can issue power-management and snapshot instructions when the endpoint is connected and the user has permission.

Available direct actions:

  • start
  • shut down
  • reboot
  • stop
  • create snapshot
  • delete snapshot
  • apply snapshot

Every power or snapshot action requires confirmation.

Shutdown vs Stop ​

Shut down requests a graceful guest shutdown. Use it when the guest operating system should shut down cleanly.

Stop turns the VM off without guest shutdown. Treat it as the force-off option.

Snapshots ​

The VM list shows Hyper-V snapshots, also called checkpoints, reported by the Hyper-V WMI/CIM provider.

Supported snapshot actions:

  • Create snapshot creates a full Hyper-V snapshot with the provided name.
  • Delete snapshot removes the snapshot through Hyper-V. Hyper-V merges checkpoint data as part of that operation.
  • Apply snapshot reverts the VM to the selected snapshot. Current VM state can be lost.

Ordyn does not delete .avhdx files directly. Snapshot removal is always delegated to Hyper-V.

Guest Endpoint Identification ​

Ordyn tries to match each VM to an endpoint.

The preferred match source is SMBIOS/DMI UUID because it is more stable than hostname or network naming.

Fallback matching uses VM network adapter MAC addresses.

Identification states:

  • identified
    • exactly one endpoint matched
  • ambiguous
    • multiple endpoints matched the same evidence
  • unidentified
    • no endpoint matched

When a VM is identified, the VM table links to the guest endpoint. The guest endpoint overview can also show which Hyper-V host and VM it belongs to.

Ordyn does not automatically link ambiguous matches. Fix duplicate endpoint identity data or stale inventory first, then recollect inventory.

Job Steps ​

Hyper-V power operations can also be authored as job steps:

  • Start Microsoft Hyper-V VM
  • Shut down Microsoft Hyper-V VM
  • Reboot Microsoft Hyper-V VM
  • Stop Microsoft Hyper-V VM
  • Create Microsoft Hyper-V VM snapshot
  • Delete Microsoft Hyper-V VM snapshot
  • Apply Microsoft Hyper-V VM snapshot

The editor uses a VM combobox populated from inventoried Hyper-V VMs. The selected value is the Hyper-V VM ID. Snapshot job steps target snapshots by templated snapshot name. Delete removes all snapshots on the selected VM with an exact matching name; apply requires exactly one matching snapshot.

See Available Tasks for the job-step reference.

Infrastructure Hosts ​

If the Hyper-V host itself runs or hosts Ordyn infrastructure, mark it in Edit endpoint as an Ordyn hypervisor host.

You can also select the Ordyn infrastructure endpoints hosted by that hypervisor. This relationship is used as operator-facing topology and recovery context for infrastructure maintenance flows.

For normal Hyper-V hosts that do not host Ordyn infrastructure, the VMs tab and Hyper-V job steps still work without selecting hosted Ordyn infrastructure endpoints.