Hyper-V Server 2008 Remote Management

robertbp · 2012-07-09T04:20:12.000Z

I have a weird issue. I can’t remotely manage my Hyper-V 2K8 server. I’ve gone through the setup, both on the machine to manage from (Server 2008R2) & the machine to manage, via the Server Manager script & manual commands. It tells me it completes succesfully, Powershell does it’s thing but it doesn’t work.

Here’s where it gets weird - I can use the VM Manager succesfully. Server Manager, Device Manager - nothing. Can’t connect.

Here’s hoping someone can help - it’s a new deployment & it’s really bugging me.

tylerbeazley7018 · 2012-07-09T04:29:56.000Z

Service pack installed?

Had similar issues on a R2 host, installing the service pack worked wonders.

robertbp · 2012-07-09T04:52:34.000Z

I assume you mean on Server 2008R2? Yup - fully patched. On that note - are there any updates for Hyper-V Server? It doesn’t seem to be a patching product.

mattbartle · 2012-07-09T05:43:37.000Z

Hyper-V server does get updates just like any other Windows server.

Do you get the menu when you log in? There’s an option there to check for and install updates.

Also, have you tried shutting off the firewall on the Hyper-V server just to see if that’s the issue?

bthorp · 2012-07-09T05:44:24.000Z

By default it has the firewall on, for starters. You should get familiar with the commands to allow ports or set up a GPO for the firewall ports you want open.

What type of remote management are you doing? Remote Server Console? Hyper-V Manager? Both are blocked, and RSC is disabled by default. The best one is that you cant enable most of these if its managed in the domain or after joining the domain.

PROTIP: Install core tools to make your life less like hell. http://coreconfig.codeplex.com/

christophero · 2012-07-09T05:57:43.000Z

This guy should likely fix all of your Hyper-V remote management woes:

http://archive.msdn.microsoft.com/HVRemote/

alexgoodside6589 · 2012-07-09T08:05:05.000Z

You’re not alone with your issue. I had the same problem and what is important to open the corect ports and settings in the Advanced Firewall settings on the Hyper-V server to be able to manage it remotely. For remote managment I use RSAT for Windows 7. Once installed they can be enabled in the “Control Panel / Programs & Features / Turn Windows Features on”. In there go to RSAT and enable the Hyper-V management.

Now, what I did was the following:

a) disable the firewall via command line on the Hyper-V server

b) install Coreconfig on the Hyper-V server which gives you a GUI to change Advanced Firewall settings

c) now you can also remotely manage your firewall

d) go to the advanced firewall settings and change the settings to allow for remote access etc (do not know off by heart which settings)

e) IMPORTANT re-enable the FIREWALL

NOTE: on your Win 7 machine you can also connect to your Hyper-V server via your Computer management console for disk management etc; also via command line (net use \hyper-v server\c$ z:) you can add the c: drive (or any other on the server to your local machine to copy files back and forth quicker)

I used the hvremote.wsf but it does not fix all your problems ALLOW ALL RELEVANT RPC FIREWALL SETTINGS on the Hyper-V server.

Fire me an email for a step by step guide if you need it. This is just a quick overview. I am on holiday after all:)

johnwhite · 2012-07-09T12:50:53.000Z

Crap. Seriously? Why do admins have to go through contortions for basic configuration issues?

StorageNinja · 2012-07-09T13:50:35.000Z

John White wrote:

Crap. Seriously? Why do admins have to go through contortions for basic configuration issues?

Version 3’s going to KILL the competition… with confusion.

robertbp · 2012-07-10T03:36:07.000Z

mattb314 wrote:

Hyper-V server does get updates just like any other Windows server.

Do you get the menu when you log in? There’s an option there to check for and install updates.

I’d assumed it must, I was just unsure because it wasn’t showing up in my WSUS (it has - eventually). Not sure how I overlooked the option on sconfig.

mattb314 wrote:

Also, have you tried shutting off the firewall on the Hyper-V server just to see if that’s the issue?

Tried that, no difference.

robertbp · 2012-07-10T03:38:36.000Z

Brian Thorp wrote:

By default it has the firewall on, for starters. You should get familiar with the commands to allow ports or set up a GPO for the firewall ports you want open.

What type of remote management are you doing? Remote Server Console? Hyper-V Manager? Both are blocked, and RSC is disabled by default. The best one is that you cant enable most of these if its managed in the domain or after joining the domain.

PROTIP: Install core tools to make your life less like hell. http://coreconfig.codeplex.com/

I’ve done all the prep work. Local commands, GPO, ports tested & confirmed. As I said - the VM Manager console works so it can connect. Non of the server OS management options do though (Computer manager, server manager, device manager, etc).

robertbp · 2012-07-10T03:40:21.000Z

ChristopherO wrote:

This guy should likely fix all of your Hyper-V remote management woes:

http://archive.msdn.microsoft.com/HVRemote/

Chris - you’re a genius! Thank you.

Got his script, ran it both ends rebooted the Hyper-V server & it works! If I’m reading his output correctly, the user account wasn’t authorised locally in WMI.

christophero · 2012-07-10T06:07:29.000Z

I’m not the genius - that author is. I’m just another Hyper-V admin who was terribly frustrated by the steps required to remote administrate Hyper-V and fortunately found that guy’s work!

robertbp · 2012-07-10T09:06:42.000Z

No arguments. Still. thanks for sharing such an awesome resource.

bthorp · 2012-07-10T11:21:20.000Z

Again, you must:

allow it to pass through the firewall (or against best practice, shut it off completely.)
Enable remote management*

Note that Enabling remote management is easier with core configuration as its a few things to enable. I have full device management (read only) remotely on my hyper-v servers.

Hyper-V Server 2008 R2 is a custom Windows Server 2008 R2 Core build that has two things special about it; one, it expires something like 32 years from now, and two that it comes out of the box with the hyper-v role enabled and working - a PITA to set up by hand.

If you are having lots of trouble I’d suggest looking/waiting for 2012 since it has a hybrid mode that lets you install the gui, configure everything (NIC Teaming is one i’m excited for) and then uninstall it and let it run with less patches needed / overhead.

It has a TON of hyper-v enhancements some I think are totally necessary for hyper-v to be serious in the world.

robertbp · 2012-07-11T01:10:17.000Z

Brian Thorp wrote:

Again, you must:

allow it to pass through the firewall (or against best practice, shut it off completely.)

Again - done & disabled to test.

Brian Thorp wrote:

Again, you must:

Enable remote management*

Did that too. Still gave me a hard time.

Thanks though - the link ChristopherO provided set me straight.