Managing Hyper-V Server 2008 R2 in a Workgroup

2 Jun

I setup a new Hyper-V server at home last night. The install itself was straight forward, I’m basically trying to run even less servers to keep the old energy bills down. It’s a shame there is no USB support in Hyper-V, otherwise I’d convert my Media Centre box over to Hyper-V also. (I currently have 2 dual PCI freeview tuners in my media server, but could be tempted to change these to cheap USB ones from ebay down the line if I could VM it, freeview HD anyone?)

Anyway, I only have a basic workgroup at home, I figured a domain would be a bit OTT, but I literally spent hours getting my netbook (running Win 7) and the server (running Hyper-V Server 2008 R2) to talk.

I added the Remote Server Administration Tools and then added in the Hyper-V Management components. Everytime I tried to connect to my Hyper-V server, I got “You do not have the required permission to complete this task. Contact the administrator of the authorization policy for the computer “COMPUTER”.

After a bit of googling, the guide here turned out to be pretty useful, although it was late and I can’t remember the exact steps I took, so you’ll have to follow them yourself! It was basically a case of logging into my netbook as administrator with same password that was used on the Hyper-V server.

I’ll going to change my Hyper-V server over to run Server 2008 R2 pretty soon, so all the Hyper-V Management GUI will be on the box itself and remove any headaches, I’ll just RDP into it.

PS, if you run into any “Access Denied” errors running the HWRemote.wsf script this is beacuase this is a Windows security mechanism. On the machine where you downloaded HVRemote, in Windows Explorer, right-click on the file and select properties. On the general tab at the bottom of the page, there will be a message saying “Security: This file came from another computer and might be blocked to help protect this computer”. To the right of that is an Unblock button. You need to click that to allow HVRemote to work.”