6 thoughts on “ProHVM v.2.60

  • June 27, 2017 at 5:23 am
    Permalink

    Hi,

    I downloaded HVTools2.60.zip and successfully extracted the files in the zip file. However, when I executed Hyper-V_Tools_Setup_2.60.02.01.exe from the ZIP file, I encountered “Checksum mismatch” error generated by Astrum Installer.

    Please advise. Thanks.

    Reply
  • June 27, 2017 at 10:04 am
    Permalink

    Hi Joseph,
    Please try again! The installer is replaced…

    Thank you!

    Reply
  • June 27, 2017 at 4:30 pm
    Permalink

    Hi,

    The new installer worked. However I noticed “C:\Windows\Hyper-V Tools Uninstaller.exe”, the file associated to the shortcut “Hyper-V Tools Uninstaller” does not exist. Also, are there any reasons that the files are installed in C:\Windows instead of its own directory?

    Thanks.

    Reply
    • June 27, 2017 at 4:56 pm
      Permalink

      Hello Joseph!

      We are working on a new setup that will adress the issues mentioned by you!

      The reason for the .exe to be in the windows dir is that ProHVM is intended for core installations. By placing it there it is easily started from anywhere by calling “hvm” from a command prompt.

      Note that there really is not much installed. The HVM.exe can be copied to a USB and run from there!

      Reply
  • July 6, 2017 at 6:14 am
    Permalink

    Hi,

    We are trying out the latest release of ProHVM with our Hyper-V Core 2016 Installation, but it is failing to connect and list the VMs.
    Does the application require any configuration in order to the connect to the Host?
    Using the native Microsoft Hyper-V manager we have successfully manage to connect remotely to the Host.

    Kindly advise.

    Thanks,
    Luigi

    Reply
    • July 6, 2017 at 8:32 am
      Permalink

      Hi Luigi,
      Check that WMI communication is enabled in the firewall. Disable the firewall on the host temporarily to see if that is the problem. Also, enable remote management on the host.
      Check that the credentials you provide in ProHVM has sufficient rights to manage Hyper-V. Use Domain\Username for domain accounts.

      Reply

Leave a Reply

Your email address will not be published. Required fields are marked *