VT Technology Management Utilities for Hyper-V build 3.0.0.90

This release includes bug fixes, updated functionality for managed hosts discovery and persistence as well Guest Console View mouse support for virtual machines without integration services installed.

Managed Hosts Discovery and Persistence
  • A list of the managed Hyper-V hosts is currently saved between sessions.
  • Managed hosts can be added by typing host name or address directly into Guest List View drop down box. Multiple hosts can be added as a semicolon separated list via 'Define View' dialog ('View|Select...'). 'Define View' dialog also supports discovery of all currently running Hyper-V hosts via Active Directory.
  • Managed hosts can be removed by using 'Define View' dialog.
Guest Console View Enhancements
  • This build includes fixes for mouse functionality in Guest Console View for virtual machines that have integration services installed as well as mouse support for virtual machines without integration services. In later case mouse will be captured in Guest Console View and can be released using a hot key configured via Options (Tools|Options) dialog.
  • Mouse support for virtual machines without integration services works only for interactive console sessions and does not work via RDP.

vtUtilities version 3.0.0.61 Release notes

vtUtilities version 3.0.0.45 Release notes

vtUtilities version 3.0.0.37 Release notes

vtUtilities version 3.0.0.12 Release notes

vtCommander version 2.5 Release notes

Installation

vtUtilities run only on 64-bit version of Windows. It is recommended that you download and read the latest version of the User Guide prior to installing vtUtilities. Download and run vtUtilities bootstrapping executable that will guide you through the installation process. You will be able to start vtUtilities from a command console by typing ‘vtUtilities’ on the Windows Server core and the Hyper-V Server intstallations after that.

Uninstallation

You can remove and/or reinstall vtUtilities by running its bootstrapping utility with the ‘/remove’ command line argument.


Please give us your feedback!