blog.iabsolute.com

While setting up a Hyper-V server for Wayne and Justin to work with some VMs to troubleshoot the SBS 2003 to 2008 replication error, we ran into a roadblock with getting the Hyper-V Manager connected to the Hyper-V Server 2008 box:

Virtual Machines

Access denied. Unable to establish communication between ‘Hyper-V Server’ and ‘Hyper-V Manager’.

This is puzzling since the workstation has been connected to this particular Hyper-V server many times using other network profiles. The profile we created for the Microsoft folks was seemingly giving us the connection issue.

The fix took a bit of searching to find and needed to be accomplished on the Windows Vista system where the Hyper-V Manager was installed:

Close the Hyper-V Manage

Click Start and type: %windir% [Enter].

A Windows Explorer window will open to the Windows directory.

Type: dcomcnfg in the Search Windows field at the top right hand of the Explorer window.

You will see the following in your search results:

1. Right click on dcomcnfg and Run As Administrator.
   • Authenticate with the local admin credentials if UAC prompts for credentials, or Continue if it does not.
   • Open the Component Services node, then the Computers node, then right click on My Computer and click on Properties.
   • Click on the COM Security tab.
   • You will see the following

1. • Click the Edit Limits button under Access Permissions.
   • Enable Remote Access for Anonymous Logon
   • Before and after shot:

1. Click Apply and OK.
2. Close the Component Services console and the Windows Explorer window.
3. Start the Hyper-V Manager and continue through the UAC.

The virtual machines, if any, will show up in the Hyper-V Manager console after that.