Hyper-V Server 2008(workgroup) managed from Hyper-V MMC Vista x64(workgroup too) - How it worked for me

I've installed the free Hyper-V Server 2008 on a server, and there was no domain available, so I've left it in the local workgroup.

I had Vista x64 Ultimate installed on a laptop(workgroup too). I've downloaded the Windows Vista Service Pack 1 Management Tools update for the release version of Hyper-V and installed it on that laptop in order to manage the Hyper-V Server 2008 from it.

As you may know, we can't connect to the Hyper-V Server by IP address. The name of the Hyper-V Server was hypervstd. So I've added an entry for this name on the C:\Windows\System32\drivers\etc\HOSTS file on the laptop:

hosts

You can edit the HOSTS file on the Hyper-V Server too from the CMD window, just type "notepad.exe hosts" while you are in the C:\Windows\System32\drivers\etc\ folder to add an entry for the name of the machine on which the Hyper-V MMC is installed(you need a static IP address on this machine for that). Although it worked for me without doing that.

So:

- the Hyper-V Server 2008 and the Vista x64 laptop are members of the same workgroup(I've observed that might work if they are members of different workgroups).
- I've added a local administrator on the Hyper-V Server with the same user name and password as the user logged on the Vista laptop.
- the HOSTS files were prepared.

And now I can connect. However, I was getting the error "Access denied. Unable to establish communication between: ‘HYPERVSTD’ and ‘the name of the laptop’ " within the Virtual Machines area of the Hyper-V MMC.

hyperv_mmc

I've followed Step 7 from John Howard’s tutorial(for my Vista laptop), which is:

1. Click Start, Run, type DCOMCNFG. Click OK.
2. Expand Component Services, expand Computers. Right-click on My Computer and click on Properties.
3. Click on COM Security.
4. In the Access Permission area, click Edit Limits.
5. Select ANONYMOUS LOGON in the Group or User Name area. Then set the Permissions for ANONYMOUS LOGON to Allow for Remote Access.

dcom

And things started to work fine for me.

Comments (4) -

  • Martijn

    2/6/2009 12:09:03 AM |

    Didn't work for me... still getting the same error, even after rebooting the client. Firewalls are disabled on both ends, to ensure they aren't causing something else.

  • adimcev

    2/6/2009 11:38:01 AM |

    Hi Martijn,

    I'm sorry to hear that, I know it's frustrating.
    Are you stuck at the error with Access Denied. Unable to... ?
    Have you double-checked all of the above steps ?
    I know it doesn't help you me saying this, but personal I haven't had any issues till now after I did what I've described above.

    Adrian

  • Ted

    4/17/2009 5:17:19 PM |

    Thanks, that was the last thing I had to do before it actually worked.  First I had to disable the firewalls.

  • Mike

    4/9/2010 1:48:58 AM |

    Worked, great thanks, Mike

Comments are closed