Hyper-V virtual machines in Edgely Console

Add a Windows host running Hyper-V over WinRM, then start, stop, save and checkpoint its virtual machines and open their desktops, with nothing installed on the host.

Applies to
Edgely Console
Updated

Also in the app Edgely Console: Documentation tab, Platforms, Hyper-V

Edgely manages the virtual machines of a Windows host running Hyper-V, over WinRM, the same remote PowerShell the WinRM terminal uses. Nothing is installed on the host.

Adding the Host

  1. On the host, in an administrator PowerShell, run winrm quickconfig once: it starts WinRM and opens port 5985 in the firewall. Edgely does not encrypt WinRM messages over HTTP, so for port 5985 also run Set-Item WSMan:\localhost\Service\AllowUnencrypted $true (only on a network you trust); over HTTPS (5986) nothing more is needed. See WinRM.
  2. In Edgely, Platforms > New Platform, choose Hyper-V.
  3. Give the host's name or address, and the port: 5985 (HTTP, the default) or 5986 (HTTPS, if the host has a certificate for WinRM; turn off Verify SSL for a self-signed one).
  4. Choose a password credential of an account that may manage Hyper-V: an administrator, or a member of Hyper-V Administrators.

Double-click the platform, or click Open, to open its explorer in a tab.

The Explorer

The left column lists the virtual machines with their state, CPU use and memory. Select one to see its uptime, generation and the addresses its integration services report, and to act on it:

ActionWhat it doesOffered when
StartStarts the VMOff or saved
Shut downAsks the guest to shut down (integration services), after a confirmation. A guest that cannot take the request (no operating system, its integration services not running or still starting) is not touched: the explorer says so, and Turn off stops itRunning
Turn offCuts the power, after a confirmationRunning or paused
SaveSaves the VM's memory to disk and stops itRunning
Pause / ResumeFreezes and thaws the VMRunning / paused
RestartResets the VM, after a confirmationRunning
Open desktopOpens the guest's desktop over RDP, at its first addressRunning

Open desktop connects to the guest's own address on port 3389: a saved connection to that address opens with its credential, otherwise an unsaved one asks for one. The guest must allow Remote Desktop. Hyper-V's own console (VMConnect, port 2179) is not available yet.

Checkpoints

The Checkpoints section lists the selected VM's checkpoints.

  • New checkpoint takes one, named as you choose (letters, digits, spaces and - _ . ( ) :).
  • Apply brings the VM back to a checkpoint, after a confirmation: what changed since is lost unless another checkpoint keeps it.
  • Delete removes a checkpoint after a confirmation; the VM keeps its current state.

When Something Fails

The explorer says why, in the host's words: the account may not manage Hyper-V, the Hyper-V PowerShell module is missing on the host, the VM cannot do that in its current state. A host that does not answer offers Try again.

Something missing or wrong?

Documentation gaps are bugs. Tell us which page you were reading and what you expected to find.

Send feedback →

Product names, logos and brands mentioned on this page are the property of their respective owners. They are used for identification and comparison only, and their use does not imply any affiliation with or endorsement by them.