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
(120)
Add to favorites
10/24/2016
E-mail Twitter del.icio.us Digg Facebook
Sign in to ask a question


  • 555-555-0199@example.com
    1 Posts | Last post October 12, 2017
  • ERROR: This OS release is unsupported.
    1 Posts | Last post September 08, 2017
  • ERROR: This OS release is unsupported.
    1 Posts | Last post August 29, 2017
    • 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
  • 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
  • Connection to server
    5 Posts | Last post February 14, 2017
    • I'm trying to connect to the server using Hyper V manager on my laptop win 10. I get a name resolution click Ok and then get the error message:
      WinRm-Cilent can't process the request . There is also something about Trusted Hosts as well, that the list is not authorized.
      
      Can anybody assist please.
      
      many thanks.
      
      Regards
      
      Shaun
    • I got it working on win-10 adding :
      after getting the istructions done about hvremote..
      -client-side win10: you must 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 *
      if still not working:
      -server-side: try to enable PSRemoting by typing Enable-PSRemoting
      -- restart the service Restart-Service WinRM
      
      Hope it helps!
    • Endry04 hi,
      
      thanks for that I will try it and see what happens.  But it won't be for another two weeks.
      
      Regards
      
      Shaun
    • Endry04 hi,
      
      OK thanks for the commands, and now it works.
      
      Cheers mate.
      
      Regards
      
      Shaun
    • Endry04 hi,
      
      I've now got another problem. I tried to start the VM but got this message:
      
      "VM could not be started because the hypervisor is not running"
      
      I have tried "bcdedit /set hypervisorlaunchtype auto" but that did not help.
      
      Any ideas please.
      
      Many thanks.
      
      Regards
      
      Shaun
  • hvremote in hyper-v 2016
    1 Posts | Last post January 25, 2017
    • I'm trying hyper-v 2016 in workgroup(not domain), how can I cionfig remote access account like using hvremote in hyper-v 2012, thx
  • How can I fix this on Server 2008?
    8 Posts | Last post December 15, 2016
    • 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. 
  • Win10 and HyperV Server 2016 support
    1 Posts | Last post December 12, 2016
    • Hi
      
      Any chance this script could be updated please to support Windows 10 Client and HyperV Server 2016?
      
      Many thanks in advance
  • Want to Connect Win 10 Client to Server 2012 R2
    3 Posts | Last post December 07, 2016
    • I'd like to add my voice to the group requesting updating your HVRemote tool to work with Windows 10.
      I'm struggling to connect a Hyper-V Windows 10 Client to a 2012-R2 Server.
      I ran the tests outlined in the "HVRemote Documentation 1.08.pdf" file, and I can't see any errors. However, I still get the error "You do not have required permissions to complete this task. Contact the administrator of the server".
    • Same issue here and reverting the client to 8.1 is not an option for me.
      
      However, I have found I can manage my Hyper-V 2012 R2 server from a Win 10 Pro PC by using the free version of 5nine Manager: http://www.5nine.com/5nine-manager-for-hyper-v-free.aspx
      
      The free version is limited to 1 Hyper-V server, but this is fine for my home lab.
      
      
    • First, check the name of the server (host of hyper-v) really do this, and the host file in Windows/System32/Drivers/etc folder. 
      
      Second, try this...NOTE: my host of hyper-v is named "HyperLAB"
      
      # 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 HyperLAB
      
      - From DOS cmd -
      
       winrm set winrm/config/client @{TrustedHosts="HyperLAB"} 
  • Failed to obtain local computer information troubleshooting
    1 Posts | Last post October 13, 2016
    • Hi!
      We have a big Problem with our Hyper-V Manager on a 2012 R2 Server. We tried to start your hvremote script on this Server and we get the following error message: Failed to obtain local computer information -2147217389
      
      Is there any chance to resolve this problem?
      
      Please help...
      
      Thank you!
1 - 10 of 36 Items