John Howard - Senior Program Manager in the Hyper-V team at Microsoft

Senior Program Manager, Hyper-V team, Windows Core Operating System Division.

Configure Hyper-V Remote Management in seconds

Configure Hyper-V Remote Management in seconds

  • Comments 282
  • Likes

Update 19th Nov - v0.3 now released! 

It has been a little quiet on the blog front, but sometimes, at least in this case, I hope I've come up with something worth waiting for. Announcing "HVRemote"...., a tool to "automagically" configure Hyper-V Remote Management. (Amazing what can be done with a few days vacation to kill before you lose them at the end of the year....).

I'm not going into the gory detail here as I've created a PDF containing the documentation, and a site on where you can download the tool and the documentation. All I ask, is that if you find the tool useful, drop me an email or a comment. Thanks!

What does the tool do: It reduces the manual configuration steps needed for Hyper-V Remote Management that I blogged about back in March this year 1, 2, 3, 4 and 5 down to one or two commands.

  • It can configure Full installations and Server Core Installations of Windows Server 2008 with the Hyper-V role enabled, plus configure Microsoft Hyper-V Server. It runs across all locales (I've tested English and Japanese) and it doesn't matter if the server is domain or workgroup joined.
  • It can configure Vista SP1 and Server 2008 configured with the Hyper-V Remote Management tools. Again, doesn't matter if the client is domain or workgroup joined.

Quick how-to:

1. Server: To give or remove a user access permissions:

       hvremote /add:domain\user                  or
       hvremote /remove:domain\user


2. Server & Client: Display current settings (server or client): (Screenshot is client side)

       hvremote /show


The other useful options are:

3. Find out all the command line options: hvremote /help or hvremote /?


and a couple of client side options:

4. Client: Add firewall exception for MMC: hvremote /mmc:enable
5. Client: Allow anonymous access to Distributed COM: hvremote /AnonDCOM:grant

I've tried this out with a a lot of test "guinea pigs" internally at Microsoft, and using the script literally dropped their remote configuration time down to seconds. Hopefully it will do the same for you.

But I must also point you to the disclaimer on my blog, the disclaimer in the documentation, and the license conditions at before use:

HVRemote and the associated documentation are provided "as-is". You bear the risk of using it. No express warranties, guarantees or conditions are provided. It is not supported or endorsed by Microsoft Corporation and should be used at your own risk.


  • John, you've outdone yourself! I do have to ask you though if you understand the concept of "vacation" though! Ha! Here's a drink to you!

  • Hi John,

    I'm back again with the same issues that we were discussing the last time we spoke (a few months back).  :(

    If you recall, I have a non domain connected Hyper-V Server that I'm trying to connect to from a non-domain connected laptop running Vista SP1 and the Hyper-V Management tool (and using HVRemote).

    The Hyper-V Server will not be a part of a domain because in the SMB world, with generally only one physical server, having the Hyper-V Server a member of a single DC domain which is a guest under the Hyper-V Server is not a good move.

    Also, the laptop will never be a part of the same domain that is hosted on the Hyper-V Server as the laptop belongs to our techs and the Hyper-V Server and its hosted SBS 2003|8 Server belongs to our client.

    Now, what I've done is as follows:



    1. Vista SP1, latest fixes/updates

    2. KB952627 Hyper-V Management Tool

    3. Add Local Administrative user: Hyper-V

    4. Local Hyper-V Password: "Password 123"



    1. Hyper-V Server 080912, Name = HyperVServer, Manual Windows Update, configure Region, Date and Time

    2. Enable RDP (more secure clients only)

    3. Add Local User: Hyper-V

    4. Local Hyper-V Password: "Password 123"

    I've downloaded, extracted and copied (via USB Key) HVRemote.wsf to the C:\HVRemote folder on both the laptop and the Hyper-V Server.

    I've followed the documentation in your PDF and performed the following actions:



    1. cscript hvremote.wsf /mode:server /add:Hyper-V

    1a. Result: successful (all reports = OK)

    2. Reboot Hyper-V Server



    1. cscript hvremote.wsf /mode:client /AnonDCOM:grant

    1a. Seemed to be successful

    2. cscript hvremote /mode:client /FirewallHyperVClient:Enable

    2a. Made no changes as this was already the setting

    3. Rebooted the laptop.

    4. Opened Hyper-V Manager and connected to HyperVServer

    4a. Failed: The Computer 'TechLaptop' failed to perform the requested operation.

    Also, as a side note, unless I run "netsh firewall set service remoteadmin enable" on the server, I cannot connect to it via "Computer Management" and even after I've run this, Computer Management makes a connection but fails to allow me to connect to WMI Control with the following error: 'Failed to connect to \\HyperVServer because "WMI: Access denied"'.

    This error was exactly what we were talking about a few months back when I was unable to connect to the Hyper-V Server (that time running under WS2K8 Ent Core, this time running Hyper-V Server), so there still seems to be something wrong with the instructions/operation of HVRemote, or something major that I'm unable to see and am totally missing here.

    I'd *like* to be able to actually add guests to my Hyper-V Server and to be able to manage them, it would be a nice use of a Hyper-V Server.  ;)

    (PS, The "Windows Malicious Software Tool x64 - November 2008" was shown as needed when I ran the initial WU scan, yet it failed to install.  On subsequent attempts, it also fails to install.  Any idea why this is failing to install on a brand spanking new Hyper-V Server install?)

  • Hilton - you also need to run hvremote /mmc:enable on the client as well (if it wasn't enabled)

    I think the best way to try to solve this is if you can email me (preferred) using the link at the top or post up

    - the output of hvremote /show /debug:verbose on both the client and the server

    - ipconfig /all from the server AND the client

    - output of ping <server> from client (will fail, but I want to check the IP addresses are correct and there's no a DNS issue)

    - output of ping <client) from the server

    - Verify through wbemtest: On the client start/run wbemtest; hit connect and enter \\servername\root\cimv2. Also try using IP addresss ie \\ip.dotted.add.ress\root\cimv2 of the server. Does that connect?

    (TBH - I've no idea about the WU update. There's nothing unique to Hyper-V Server in terms of how updates are applied. Let's get the remote management working first - I'll see who I can find to help with WU seperately).



  • Hi John,

    I ran the /mmc:Enable switch on the client - same issue after running this.  There's no DNS issues here, but I'll email all of the info you asked for.  The WMI Tester seems to connect (at least all boxes show as selectable), so I assume that means it is working.

    The WU was just an additional query as an extra because I noticed it.  If you can find someone who can answer it, it would be good, though - definitely not as important as not being able to see the Hyper-V Server to manage it, tho!  :)

  • (To followup for others...) I got the information from Hilton and a TS session onto the boxes. In this case, the laptop was domain joined rather than non-domain as mentioned above, and the server was in a workgroup. The missing piece was needing to run cmdkey on the client in this scenario.



  • Mijn vorige blogpost over het installeren van Microsoft’s Hyper-V Server 2008 was een lap tekst met plaatjes

  • Just the other day my colleague - John Howard - made a new tool available to the world.&#160; HVRemote

  • John Howard из компании Microsoft, который является Senior Program Manager в группе разработки Hyper-V,...

  • While working on the next version of HVRemote yesterday evening, one of the things I wanted to address

  • G'day John

    Just wanted to put my 2 bobs worth in and thank you like many have already, for the GREAT Tool. I just tested it here and it worked a treat.



  • Thank you for producing this tool.

    Is the managment tool safe to use over WAN? ie. To manage a host in a datacentre?

    As I understand it I would be sending unencrypted mmc packets across the internet. Is that risky?

  • Thank you for producing this tool.

    Is the managment tool safe to use over WAN? ie. To manage a host in a datacentre?

    As I understand it I would be sending unencrypted mmc packets across the internet. Is that risky?

  • I&#39;ve seen folks disabling the Windows Firewall on Hyper-V Server and on Windows Server Core in order

  • Daniel - my recommendation if you need to manage a secure environment over an insecure network such as the Internet would be to publish the management tools over a TS Gateway such as (part 2 also), or to have a secured RDP session to the server using something like ISA protecting it. However, you may have captured mouse mode if Integration Services are not installed on guests.

    I'm not sure that the credentials are passed unencrypted (I'll have to verify that, but don't think so), it's more the range of ports you need open also.

    Another alternative is to use SCVMM where they tunnel management commands using WSMan rather than native WMI.



  • Народ начал активно устанавливать и использовать виртуализацию Hyper-V, особенно бесплатный Microsoft

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment