... and the client being in a workgroup and the server being in a different one.  :)

I'll run through all of this stuff tomorrow or the day after, when I get time to get back to this and see how it all goes.  But there's nothing here that's much different from the previous info that's leaving Ryan and myself in the situation where WMI Control shows "Root" and no namespaces under it.

Anyway, I'll see what happens when I try this all again!

Thanks for your efforts.  I just wonder if Microsoft really intended such a convoluted procedure to manage a Core box...

John this is great. Actually this is a real scenario environment.

You're great!

Hi

Have to begin with saying. Great blog ! :D

I have the same issue here. Followed you instruction down to the line, but the same happens. I can't see anything else than --Root. So i'm looking forward to the solution :)

//Michael A

John,

Thanks for the this great guide!  I'm still amazed how people figure this stuff out.

I think I may have found a mistake in Step 4.  In step 4 you say "See step 5 in part one for more information" but when I went to look at it, none of the screen shots matched up.  I did some looking and found the similar screenshots in Step 4 of Part 1.  

Is this correct?

Thanks Again,

-Howard

John,

Makes for really good reading

But I am stuck at Step 4

Step 4. Allow authenticate users to remote WMI namespaces (on server)

See step 4 in part one for more information. Here is where I’m using the “Remote Hyper-V Admins” group I created previously. As before, make sure you do this TWICE, once for Root/CIMv2 and again for Root/Virtualization.

the WMI just keeps tellimg me access denied

any ideas

John,

It is Martin yes (I still type looking at my fingers not the screen)

the client is a Domain Vista Box and the Core server in a workgroup so I am trying to run the mmc from the snap in on the client this is when I connect the computer management snap in then browse to WMI, then when I right click it comes up access denied.

as I am not very big on command line stuff (but trying to learn) it is very frustrating I have copied all 5 of the walkthrough's onto paper to get all the steps in the right order.

Thanks in Advance

Martin

Don't forget, you can also use RemoteApp on the 2008 server where hyper-v is installed. You can pubish both the vmconnect and the virtmgmt. My laptop is not part of the domain, and i have no problems connecting.

Hey Bev,

Neat trick using RemoteApp, except for one problem:  Hyper-V Connect to Virtual Machine doesn't work with Terminal Services.  How did you resolve that?

Hi John,

Thanks for the great series of articles on configuring machines to remotely manage Hyper-V!

Using your articles as a guide, I figured out how to do the 6th scenario:  workgroup client talking to domain bound server.  Notes are here:  http://dannythorpe.com/2008/06/21/hyper-v-remote-management-workgroup-vista-client-to-domain-bound-server/

-Danny

I'm trying to setup Hyper-V manager in a domain environment but I'm getting a slightly different error message to those you have covered here. When I open Hyper-V Manager on the client, I get the message:

"Access denied. Unable to establish communication between 'CLIENT' and 'SERVER'."

This appears in the Virtual Machines panel. The client and server are connect to the same unmanaged switch with no firewalls other than the window firewall in default configuration on both machines. My user is a local machine administrator on both machines (with UAC running). Other services such as remote desktop between the machines works without problems.

I followed the steps in Part 4 of your guide, except for the WMI Control section, as when I inspected the settings the

user already had the necessary access due to being a server local machine administrator.

The two operations I can perform successfully in Hyper-V manager from the client are using the Hyper-V Settings and the Virtual Network Manager features, but everything else fails with the above message, usually at the end of a wizard.

Thanks for any help you can offer.