Appearance
Microsoft Hyper-V VMs
Use a Windows Hyper-V host's VMs tab to inspect virtual machines, manage power and checkpoints, change VM settings, and open consoles.
Host scope
Use these workflows on standalone Hyper-V hosts. Support for failover clusters, Cluster Shared Volumes (CSV), System Center Virtual Machine Manager (SCVMM), and live migration is not verified.
Before you start
Use an approved Windows Hyper-V host with a connected Agent and current VM inventory.
Assign Hyper-V Operator and Endpoint Viewer in the Hyper-V host's tenant or folder. Platform Admin also supports these operations. Access to a guest alone does not provide host management or console access.
Collect inventory
Run Collect Microsoft Hyper-V VM inventory on the host, or use the recollect action on the VMs tab. Collect again when changes made outside Ordyn are missing.
VM list and details
Inspect VM state and resource allocation in the VMs tab. Right-click a VM to access its management actions and Operation history.
Operation progress
Open Operation history from the VM's context menu or an identified guest's Hyper-V controls to review active operations and recent results. After an interrupted connection, check the outcome before retrying.
Wait for an active operation to finish before submitting another manual change to the same VM, including when an automated job is changing it.
Power actions
Use the VM's power actions to start, shut down, reboot, or stop it. Shut down requests a graceful guest shutdown and depends on the guest operating system and Hyper-V integration services.
Stop turns the VM off without a guest shutdown. Prefer Shut down when the guest should close cleanly.
To run a power action on several VMs, select them with the checkboxes. Review any skipped VMs before confirming. A failure on one VM does not stop the action on the others.
Snapshots and checkpoints
Use Manage snapshots to create, apply, or delete checkpoints. Applying a snapshot discards changes since that snapshot. A running VM is powered off without guest shutdown and restarted after successful restoration; a VM that is already off stays off. Inspect the VM before restarting it if restoration fails.
Snapshot names can be duplicated. Select the intended checkpoint carefully and follow the job task guidance for automated selection.
Hyper-V checkpoint age alerts
Create Hyper-V checkpoint age too high under Alert Rules and assign it to a guest endpoint. Set the age limit in hours to alert when one of that guest's checkpoints is older than the limit.
The guest must be identified on a host in the same tenant. Collect Hyper-V inventory before using the rule and schedule regular collection on the host. Maximum inventory age controls how long a collection remains usable and defaults to 24 hours; choose a limit that suits your collection schedule.
Inspect checkpoints in the rule's evaluation details. If inventory becomes unavailable or stale, collect it again.
Modify a VM
Choose Modify virtual machine to rename the VM, change its memory, or manage its DVD drives. Turn the VM off before changing memory or adding or removing a DVD drive.
Under Memory, set Startup RAM in MiB. Enable Dynamic Memory to configure minimum and maximum RAM.
To mount media, choose Insert ISO on an empty DVD drive and select an approved, clean ISO file or operating-system install media configured in Ordyn. ISO media can be inserted or ejected while the VM is running when Hyper-V permits it. Eject the media before removing a DVD drive.
Console access
Select Open console on a VM and allow browser popups. The host needs a connected Agent and an available Relay assigned through its tenant or folder. The guest needs neither an Agent nor a network connection to the browser.
The viewer uses VMConnect Basic Session. A competing local Basic Session client can disconnect it; close competing VMConnect windows when troubleshooting.
Use relative pointer mode if ordinary pointer tracking does not work, and press Escape to release capture.
Sessions have a 15-minute idle timeout and a four-hour maximum duration. Select Keep open when prompted to continue monitoring an idle VM. Reconnect after a session ends. One host supports up to four active consoles.
See Desktop Connections for network requirements.
Actions on mapped guest endpoints
Open an identified guest endpoint to use its Hyper-V controls without navigating back to the host. The host requirements and roles also apply here.
Guest endpoint identification
Collect hardware inventory on guests and Hyper-V inventory on the host to identify managed guests. Identification requires one matching system UUID. Correct duplicate or stale identities and recollect when a match is ambiguous.
Host jobs can use {{ endpoint.hyperv_guest_endpoint_ids }} to target identified guests. See Composing Jobs for host-and-guest maintenance.
Job tasks
Use Hyper-V tasks to automate inventory, power, and checkpoint operations.
Ordyn infrastructure hosts
For a host running Ordyn infrastructure, configure its infrastructure role before planning infrastructure maintenance.
Powering on guest endpoints
Choose Power on from a guest endpoint's Power menu and select Automatic or Hyper-V to start it through its host. Jobs can use Power on endpoints before running or the Power on endpoint step.
The host must be connected and the guest must have a current, unambiguous identification. Resolve host connection or guest identification problems before retrying; this action does not power on the host.
A successful VM start does not confirm that the guest Agent has connected. Use a wait step when a job needs the guest to be connected before continuing.