Hyper-V Program Manager
The Hyper-V management tools (MMC snap-in and associated UI) are now available for download:
x86: Update for Windows Vista (KB949758) x64: Update for Windows Vista x64 Edition (KB949758)
These tools allow you to manage and interact with an installation of Hyper-V from your Vista computer in exactly the same manner that you do on a full installation of Windows Server 2008. Note that you need to have SP1 installed on Vista in order for this to work.
Also be aware that installing the Hyper-V management tools will create a shortcut for our MMC snap-in the "Administrative Tools" folder - which is not displayed under Vista by default. You need to enable this folder under the start menu properties to have it displayed.
Also note that you will need to enable WMI between your computer (per this article: http://msdn2.microsoft.com/en-us/library/aa389290(VS.85).aspx).
Are there any instructions on how to get this to work from a remote PC? I've added myself via Authorization Manager on the host PC, but still get this error on my Vista box:
"You do not have the required permission to complete this task. Contact the
administrator of the authorization policy for the computer "XXXXXX""
The use of Hyper-V RC0,I found that the use of VMBus Network Adapter download BitTorrent VMBus Network Adapter will take place Auto Disable.
download After about 30 minutes.
I'm getting the same as error mentioned above. When trying to connect to my Hyper-V server, I get the following error: "You do not have the required permission to complete this task. Contact the administrator of the authorization policy for the computer xxxx." My user account is a member of the local administrators group on the server, and I've also added myself to the administrators group within the authorization policy following your instructions in an earlier post. But still no luck...
I too am having problems. I have run through the following:
1. Added myself to the local admins account
2. Checked the DCOM security settings for the Hyper-V-related DCOM objects - Virtual Machine Management and Virtual Machine Worker Process
3. Checked the firewall settings on both ends of the connection to ensure that the necessary WMI and DCOM exceptions are enabled (I note that the update installs specific exceptions into the firewall, which is nice)
I can successfully connect my machine to the Hyper-V host and I can review and change the settings for the Hyper-V system.
What I can't do is access any of the virtual machines. None appear in the list, and if I try to create a new one the process fails.
The Hyper-V manager on my laptop (Vista x86, SP1, fully patched) fires up and I get a 'Connecting to Virtual Machine Management Service...' message in the Virtual Machines panel which sits there for ages. After a noticeable delay I get a message saying 'Cannot connect to the RPC service on computer '<computername>'. Make sure your RPC service is running.'
I have checked the RPC services on both ends of the connection and all are running fine.
I can also browse the folders of the hyper-v server when I run through the create new virtual machine wizard, so connections between the two machines are working to a fairly high degree.
At this point, I' run out of ideas, technet, masn and google articles to help. All assistance gratefully received!
As an interesting followup, we installed the update on a colleague's laptop running Vista x64. No config necessary - as soon as I added his account to the local admin group on the server everything fired into life. Is this a 32-bit versus 64-bit issue? Anybody here got it working with x86 vista?
I have the exact same experience as Rik. No way to get it working on x86, but just installed it on x64 and it worked right away. The link in the post to the WMI information does not work so I am guessing that the WMI configuration is the key but I have no idea what to do.
It doesn't work for me on x64 Vista. I've tried modifying all the DCOM items listed above with no joy.
My Hyper-V server is in Workgroup mode, as is my workstation. Is this more difficult without both the server and Vista workstation being in the same domain?
I just tried it from my x86 based laptop and cannot connect from it either. Same error as on my x64 machine. Both are Vista SP1 for what it's worth, in Workgroup mode.
I posted above, but just wanted to add that I'm using x64 Vista SP1 and it doesn't work. And the server, and my notebook are both in the same Workgroup (not domain joined.)
Wondering if this has anything to do with the problem for those of us not using a domain for the server and Vista box? I am using a nondomain account which has been added to the local Administrators group on the remote server...
However, UAC affects connections for nondomain user accounts. If you connect to a remote computer using a nondomain user account included in the local Administrators group of the remote computer, then you must explicitly grant remote DCOM access, activation, and launch rights to the account.
We are using domain accounts in all cases. All our machines are members of the domain - workstations and servers; both user accounts I have tried are non-admin accounts in the domain, added to the local admins group on the server. I have also tried the domain admin accountand my success/failure follows the same works on x64, fails on x86 as with non-admin accounts.
UAC is switched off on both laptops (we run development environments which bitch mightily if otherwise) and both user accounts are local admins on the workstations.
Stuart - with regards non-domain systems, I have a vague memory of a change that came through with server 2003 whereby if there was no domain then security policies prevented RDP between the systems as there was no trust relationship. A registry setting fixes the problem, but I can't remember what it was. I hit the problem with a windows-based system we were installing in an NDS organistion, with no AD or domain infrastructure. Sorry I can't be more specific.
I'm not at work right now, and it's late here in Blighty. I'll follow up on the non-domain RPC issue when I get into the office tomorrow and post again if I have any more success.
I had the same problem and was searching for a solution, when I came to this blog.
Both the server and the workstation is in a domain and the Hyper-V manager is started with Administrative rigths.
I didn't do anything to solve the problem, other than a refresh of the server and I had full access to it. Can't explain it, but it works.
John Howard has posted the full (long) steps required to fix the problems described in the comments above: http://blogs.technet.com/jhoward/archive/2008/03/28/part-1-hyper-v-remote-management-you-do-not-have-the-requested-permission-to-complete-this-task-contact-the-administrator-of-the-authorization-policy-for-the-computer-computername.aspx
Having read through that lot, I found that the steps in part 2 fixed it for me:
Specifically, I think it was the granting of remote access for ANONYMOUS LOGON whcih did it. I haven't had chance to check yet, but I bet that is enabled already on the x64 vista pc we got working initially.
Kudos to John for his incredibly detailed walkthroughs!
Still getting the RPC error even after following the steps in the blogs above. Could it be firewall related? My client PC is here at work behind a firewall, the Hyper-V server is co-located elsewhere and is not firewalled. I logged in as a member of a domain here at work, the server is standalone, no domains involved.