Hyper-V Program Manager
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.
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:
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:
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).
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: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=7d2f6ad7-656b-4313-a005-4e344e43997d 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:
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):
(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:
Now you will need to use HVRemote to enable remote management of Hyper-V on the desktop computer.
You can now open Server Manager on the desktop computer. To do this:
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:
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: archive.msdn.microsoft.com/HVRemote
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.
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.
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.