Hyper-V Remote Management Configuration Utility (HVRemote)

HVRemote reduces the manual configuration steps needed for Hyper-V Remote Management down to a few simple commands, and can diagnose common configuration errors.

 
 
 
 
 
4.7 Star
(125)
Add to favorites
10/24/2016
E-mail Twitter del.icio.us Digg Facebook
Sign in to ask a question


  • client in domain cannot find server not in domain
    1 Posts | Last post Thu 10:18 PM
    • We usually manage our HYPER-V 2012 R2 servers that are in no domain with a client that is also not in the domain, using the same local accounts.
      
      But now I try to somehow Restart a VM from a Win10 client in the domain.
      I did all usually stuff and the server and client find each other with "/show /target" and also with a simple ping.
      But when I try a "Get-VM -Computername hv1" it cannot be found:
      
      Get-VM : Der folgende Fehler ist bei Verwendung der Kerberos-Authentifizierung aufgetreten: Der Computer "HV1.domain.local" konnte nicht gefunden werden.
      In Zeile:1 Zeichen:1
      + Get-VM -Computername "hv1"
      + ~~~~~~~~~~~~~~~~~~~~~~~~~~
          + CategoryInfo          : NotSpecified: (:) [Get-VM], VirtualizationException
          + FullyQualifiedErrorId : Unspecified,Microsoft.HyperV.PowerShell.Commands.GetVM
      
      If anybody stills reads this and has an advice, please tell me.
      
  • Using HVRemote under Win10/Hyper-V Server 2019
    2 Posts | Last post July 10, 2019
    • I am getting this message on both systems:
      
      ***** ERROR: This OS release is unsupported. Use the /override parameter to
      *****        force HVRemote to assume Windows 8.1/Windows Server 2012 R2 behaviour.
      *****        This may fail and have unintended side effects.
      
      Is it safe to use /override?
    • My bad, didn't notice posts from the last year.
      I'll try to stick with this one ^^
      "Got it working w 10 and 2016. Never used HVremote"
  • Live Migration
    1 Posts | Last post December 08, 2018
    • Documentation states that Live migration only works for domain joined hosts, or hosts in domains with trust.  If I am on the source server, and connect to my destination host in hyper-v manager in a workgroup using this script, would live migration then work, since at this point trust between the hosts should be established?
  • How can I fix this on Server 2008?
    9 Posts | Last post March 19, 2018
    • e:\TOOLS>cscript hvremote.wsf /add:nodeadmin
      Microsoft (R) Windows Script Host Version 5.8
      Copyright (C) Microsoft Corporation. All rights reserved.
      
      
      Hyper-V Remote Management Configuration & Checkup Utility
      John Howard, Hyper-V Team, Microsoft Corporation.
      http://blogs.technet.com/jhoward
      Version 0.7 7th August 2009
      
      INFO: Computername is NODE1SRV
      INFO: Computer is in workgroup SRV
      INFO: Current user is NODE1SRV\Administrator
      INFO: Assuming /mode:server as the role is installed
      INFO: Build 7601.18247.amd64fre.win7sp1_gdr.130828-1532
      INFO: Detected Windows 7/Windows Server 2008 R2 OS
      ***** OpenAuthorizationStore failed: Failed to query registry
      ***** 0
      ***** Giving up as could not open the authorization store
    • Odd. First, can you try with the latest version of HVRemote just in case.
      
      Second, can you confirm if HKLM\Software\Microsoft\Windows NT\CurrentVersion\Virtualization exists, and if so what the value of ServiceApplication and StoreLocation are (they should be present). And a follow on - whether the file pointed to by StoreLocation exists - it should point to [SystemDrive:]\ProgramData\Microsoft\Windows\Hyper-V\InitialStore.xml
    • Virtualization exists, but value of ServiceApplication and StoreLocation doesn't
      The latest version of HVRemote don't work on my server. 
      Script stops on
      
      e:\TOOLS\HVRemote>cscript hvremote.wsf /add:nodeadmin
      Microsoft (R) Windows Script Host Version 5.8
      Copyright (C) Microsoft Corporation. All rights reserved.
      
      
      Hyper-V Remote Management Configuration & Checkup Utility
      John Howard, Hyper-V Team, Microsoft Corporation.
      http://blogs.technet.com/jhoward
      Version 1.08 9th Sept 2013
      
      INFO: Computername is node1srv
      INFO: Computer is in workgroup SRV
      INFO: OS is 6.1.7601 64-bit Microsoft Hyper-V Server
      _
       
      and nothing happens.
      
      
    • I found already added user. is it possible to add another user or i must delete it first?
    • If this is 2008 R2 (as indicated by the previous output) and those registry keys do not exist, there is a problem in some way with that installation. Can you run from an elevated command line:
      
      reg query "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Virtualization"
      
      and post the output.
      
      For the last post of yours, can you post back the output but adding /debug:verbose so I can determine where the script is getting stuck (give it a few minutes to timeout just in case it's simply long running for some other reason).
      
      No, you can just keep adding users arbitrarily.
    • Microsoft Windows [Version 6.1.7601]
      Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
      
      c:\ProgramData>reg query "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Virt
      ualization"
      
      HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Virtualization\G
      uestInstaller
      
      c:\ProgramData>
    • There is something very wrong there with your installation if this is being run from the server. If the contents of that registry don't exist. There should be a bunch of stuff including the store location. Is there any way they could have been deleted accidentally?
    • this registry does not exist on my hyperV server and i cant connect to Hyper-V Manager form another Server. Help plz. 
    • ;-)
  • 555-555-0199@example.com
    3 Posts | Last post March 19, 2018
  • Got it working w 10 and 2016. Never used HVremote
    2 Posts | Last post March 19, 2018
    • Like many of you I spent too long getting this configured. I tried so many guides I 100% remember all the changes I made.
      
      Windows 10 1709 in domain
      Latest Windows 2016 Hyper-v in Workgroup
      
      Did the DCOMcnfg > COM Security > Access Permission > ANONYMOUS LOGON > Allow Local and Remote access(client)
      
      Enabled PS-Remoting on both (client and server)
      Set-Item WSMan:\localhost\Client\TrustedHosts  –Value * (client)
      
      Did this on the server, but it probably isn't required:
      Set-ItemProperty –Path HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System –Name LocalAccountTokenFilterPolicy –Value 0 -Type DWord
      
      The final pieces I think made the difference is 
      
      (On the client) gpedit > Computer Configuration > Admin > System > Credentials Delegation > Allow delegating fresh credentials (Enable) and in the servers list add both wsman/servername and wsman/servername.domain.com
      
      (On the client) gpedit > Computer Configuration > Admin > System > Credentials Delegation > Allow delegating fresh credentials with NTLM-only server authentication (Enable) and in the servers list add both wsman/servername and wsman/servername.domain.com
      
      When launching the Hyper-V Management console, type servername in "Another computer" field and check the box that says "Connect as another user" Enter servername\Administrator and the password. https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/manage/remotely-manage-hyper-v-hosts
      
      Then I was able to finally connect!
      
      
      
      
      
      
      
      
    • ;-)
  • ERROR: This OS release is unsupported.
    3 Posts | Last post March 19, 2018
    • Hello John,
      
      I download Hyper-V core from Microsoft and installed.
      I download hvremote.wsf from your url.
      When I run "cscript hvremote.wsf /add:administrato" command, I received below error.
      with /override swict alos not help.
      Kindly advise me.
      
      
      INFO: HVRemote complete
      PS C:\hvremote> cscript hvremote.wsf /add:administrator
      Microsoft (R) Windows Script Host Version 5.812
      Copyright (C) Microsoft Corporation. All rights reserved.
      
      
      Hyper-V Remote Management Configuration & Checkup Utility
      John Howard, Hyper-V Team, Microsoft Corporation.
      http://blogs.technet.com/jhoward
      Version 1.08 9th Sept 2013
      
      INFO: Computername is nsap-hpv001
      INFO: Computer is in workgroup WORKGROUP
      INFO: OS is 10.0.14393 64-bit Microsoft Hyper-V Server 2016
      INFO: Assuming /mode:server as the role is installed
      *****
      ***** ERROR: This OS release is unsupported. Use the /override parameter to
      *****        force HVRemote to assume Windows 8.1/Windows Server 2012 R2 behaviour.
      *****        This may fail and have unintended side effects.
      PS C:\hvremote>
      
      
      Thank you.
      
      Kind regards,
      
      Ko Ko
    • The release notes clearly state that server 2016 and windows 10 are not supported
    • ;-)
  • The operation on computer "name" failed.
    2 Posts | Last post March 19, 2018
    • I was running into the error above when attempting to connect to my host from Hyper-V Manager.  I've successfully add my user as an administrator and joined the host to the domain, but now I'm stuck.  I found the tool you developed and thought that may lead me down a new path to success, but I don't see anything wrong :(
      
      It looks to me that everything passed, but the script output was too much for this post so it's here instead https://pastebin.com/BhByvLV7
    • ;-)
  • ERROR: This OS release is unsupported.
    1 Posts | Last post September 08, 2017
  • Remote Access with no Admin Account in same domain
    1 Posts | Last post February 27, 2017
    • Hi all,
      i have a Windows 2012 R2 Server with Hyper-V enabled. My workstation is a Windows 10 Enterprise. Both computer are in the same domain. Remote managing the server from my workstation with my local user account was working. Then I removed my account from the servers local administration group because of security measurements. Now I am not able to connect to the server anymore via Hyper-V Management. I already did the following:
      on server:
      -) cscript hvremote.wsf /mode:server /add:AT\G-AT_Admins
      -) Enable-PSRemoting
      on my workstation:
      -) enable Windows Remote Management manually on services.msc (I set it as automatic start)
      -) Open an elevated powershell console and type: Set-Item WSMan:\localhost\Client\TrustedHosts -Value *
      -) # start WinRM service
      PS> Start-Service WinRM
      
      # enable the local account token filter policy
      PS> Set-ItemProperty –Path HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System –Name LocalAccountTokenFilterPolicy –Value 1 -Type DWord
      
      # now you can add all computers to your TrustedHosts list
      PS> Set-Item WSMan:\localhost\Client\TrustedHosts  –Value ATKRIFPS01
      
      - From DOS cmd -
      
       winrm set winrm/config/client @{TrustedHosts="ATKRIFPS01"} 
      
      But I still get the error:
      You do not have the required permission to complete this task.
      
      I am running out of ideas. Can somebody help me please?
      
      Regards,
        Thomas
1 - 10 of 41 Items