Configuring Remote Management of Hyper-V Server - in a workgroup

Configuring Remote Management of Hyper-V Server - in a workgroup

Rate This
  • Comments 26

I have received a number of questions about how to go about setting up remote management of our free Hyper-V server (not the one that is part of Windows).  So I thought I would sit down and write up a set of blog posts to talk about how to do this.  Today I am going to talk about how to remotely manage a Hyper-V server from a Windows 7 desktop when in a workgroup environment.

I am going to assume that you have already installed Hyper-V server and have configured the server name, workgroup name and networking appropriately (in my case – the server name is “Server1” and the workgroup name is “WORKGROUP” – not very original, I know).  Also, I am not going to be talking about the other aspects of setting up a Hyper-V server (e.g. configuring automatic updates, enabling remote desktop, etc…).  I am just focusing on how to get remote management working.

Server Configuration

The first thing you will need to do is to go to the Hyper-V server and run SConfig.cmd (this is configured to run automatically when you log into a Hyper-V server – if you have changed this you can start it manually.  It is in the Windows\System32 folder on the server).  Once you are in SConfig.cmd you will need to:


  1. Select option 4 on the SConfig menu (labeled Configure Remote Management)
  2. Then select options 1 (Allow MMC Remote Management) and 2 (Enable Windows PowerShell)

  3. After you enabled Windows PowerShell you will be asked to reboot.
  4. After the reboot – go back into SConfig and select option 4 again
  5. Select option 3 (Allow Server Manager Remote Management)
    1. Note that Server Manager Remote Management requires that you have PowerShell enabled first – so you cannot shuffle this ordering around to try and avoid the reboot.
  6. Select option 5 to Return to main menu

Next, I am going to assume that you are not logged into your Windows 7 computer with the “Administrator” account (which is disabled by default) so you will need to create a second account on the Hyper-V Server.  To do this you will need to go into SConfig and:

  1. Select option 3 (Add Local Administrator)
  2. When prompted for an account name – enter the user name that you are using on the Windows 7 desktop (in my case – “Benjamin”).
  3. You will then be asked for a password – and again you should use the same password as you are using on the Windows 7 desktop (no – I am not going to tell you my password)


Next – to enable remote (but read-only) access with device manager – run this command from the command prompt as well: reg add HKLM\Software\Policies\Microsoft\Windows\DeviceInstall\Settings /v AllowRemoteRPC /t reg_dword /d 1 (once again that is a single command).


Finally you will need to restart the server one last time (you can use option 13 on the Sconfig menu).

Desktop Configuration

Now it is time to go and configure the desktop computer. 

The first thing to do is to download and install the Remote Server Administration Toolkit.  You can download it from here: and install it by just running it and following the prompts.

After you have done this you will need to enable the correct remote management tools.  To do this:

  1. Open the Start menu
  2. Open Control Panel
  3. Select Programs and Features (or just Programs depending on the Control Panel view that you are using)
  4. Select Turn Windows features on or off
  5. Find Remote Server Administration Tools and Check Hyper-V Tools (under Role Administration Tools) and Server Manager under the top level list
  6. Click OK


In most workgroup configurations you will not have reliable name resolution for remote computers (i.e. you need to use the IP address).  However – many of the server management tools require that name resolution be working reliably.  If you are using a fixed IP address on the Hyper-V server – you can make this work by editing the “hosts” on the desktop computer (note – you can skip this step if you can ping the Hyper-V server using its name and have it resolve to an IP address correctly):

  1. Open the Start menu
  2. Click on All Programs and then on Accessories
  3. Right click on Notepad and select Run as administrator
  4. Once Notepad has opened, use the File menu to Open… a file
  5. Navigate to the “Windows\System32\Drivers\etc” folder on the system drive
  6. Change the file name option from Text Documents (*.txt) to All Files
  7. Open the “hosts” file
  8. At the end of this file – add an entry for your server.  The format is basically the IP address of the server followed by the name of the server.
  9. Save the file and exit Notepad.

(Here is the hosts file from my desktop – after I have modified it for my server)


You will need to enable the use of WinRM to connect to your Hyper-V server.  To do this you will need to:

  1. Open the Start menu
  2. Click on All Programs and then on Accessories
  3. Right click on Command Prompt and select Run as administrator
  4. Type in winrm quickconfig and hit enter.  You will then need to say ‘y’ (yes) to a couple of prompts
  5. Type in winrm set winrm/config/client @{TrustedHosts="RemoteComputerName"} and hit enter
    1. Substitute “RemoteComputerName” with the name or IP address of your Hyper-V server.  In my test environment my desktop computer could not resolve the name of my server – so I just opted to use the IP address.  I could also have edited the hosts file on my desktop and used the server name.
  6. While we are here – we should also open the firewall on the client side to allow us to remotely manage the servers storage by running this command: netsh advfirewall firewall set rule group="Remote Volume Management" new enable=yes


Now you will need to use HVRemote to enable remote management of Hyper-V on the desktop computer.

  1. Download HVRemote from
  2. Open the Start menu
  3. Click on All Programs and then on Accessories
  4. Right click on Command Prompt and select Run as administrator
  5. Change to the directory where you saved HVRemote
  6. Type in cscript hvremote.wsf /mode:client /anondcom:grant /firewallhypervclient:enable /mmc:enable and hit enter.


You can now open Server Manager on the desktop computer.  To do this:

  1. Open the Start menu
  2. Click on All Programs and then on Administrative Tools
  3. Click on Server Manager
  4. You will be automatically prompted for the name of the server that you want to connect to.

After you enter your server name – you should have full access to manage your Hyper-V server:


The only caveat here is that Performance monitor still connects to the local computer.  You can, however, add individual counters from the remote server one at a time.  One thing that tripped me up on this issue is that after entering the server name you need to select the Select counters from computer: drop down and hit enter:



Leave a Comment
  • Please add 7 and 5 and type the answer here:
  • Post
  • I forgot to say my client computer is Windows 7 professional.

    I put comment without my name just minute ago.

  • Mmm. Really easier to use the script. You can find it here:

  • Seriously? I don't have to stand on my head, do a rain dance anything, else on top of this? Could Microsoft make this any more complicated?

    No one at Microsoft thought about how to make management of a thin virtual server easier? And let's not forget about backup! Try setting that up on server core remotely! Amazingly idiotic.

  • Ben,

    Please write a version for Hyper-V 2012 in a standalone environment? Many of the newer commands appear to have changed a bit.

    Thanks in advance


  • How can I install missing drivers (for my Highpoint RocketRAID 620 PCI card) that is installed in my Fujisu TX100 S2 server running the MS Hyper-V Server 2008 R2 OS?  I have successfully performed all the steps above and can remotely manage my server from my Windows 7 Ultimate desktop computer. DO use command line or may I install hardware drivers from the Server Manager or the HYPER-V Remote Management console on my Windows 7 PC?

  • I almost got it to work, but getting Access Denied. Running Hyper-V 2008 R2 on the server, Win 7 Pro x64 client, both are workgroup. On the Hyper-V Manager on my Win 7, I added the server, it connects but says access denied. So any time I try to change hyper-v settings, virtual networks, etc I can't save anything.

    Any help appreciated!  mrh7184 _at_ gmail _dot_ com    use subject = Hyper-V

  • Also, any idea on how to do network teaming with Intel

  • Ben, is there a way to configure this to work is the server is in workgroup and client is on domain? I would like to try this out in our Dev Lab, but putting the server on the domain means I have to jump through hoops with the networking guys so the group policies don't affect the server. All of us in the dev team use win7 laptops on the domain. I want to show the bossman how easy it is and how much time we could save by using snapshots instead of ghosting a drive each time we want to test a setting on one of our previous releases. I've followed the walkthrough step by step, but the instructions are for a workgroup/workgroup relationship. I've used the hvremote script as instructed and set the client to resolve the server's name in hosts. I still get the RPC unavailable message. I get some functionality of the hyperv manager but cannot create new VMs. Is it possible for it to work as I mentioned? Thanks for the time. And, thanks for the awesome walkthrough.

    Jack Schlee

  • I can successfully remotely manage my Hyper-V Server 2012 Core in a workgroup environment. I can also remotely manage the disks on the Hyper-V server.

    I wrote a quick 12-step tutorial (article and video) showing exactly what I did to get this working.

    Hopefully this can help others who found this to be a very frustrating task.


  • Hi

    I have a question

    Can I remotely manage Hyper-V 2012 R2 from pc with installed Windows 7 X64 Enterprice?

    I tried to do it as from manual for Hyper-V 2008, but there is a problem in cscript (cscript hvremote.wsf /mode:client /anondcom:grant /firewallhypervclient:enable /mmc:enable), it doesn't works((

    Also server manager doesn't work, it can be used only to manage only computers that are running Windows server 2008

  • This is a great article. Thank you!

Page 2 of 2 (26 items) 12