Hyper-V Management Tools available for Vista SP1
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: https://msdn2.microsoft.com/en-us/library/aa389290(VS.85).aspx).
Cheers,
Ben
Comments
Anonymous
March 25, 2008
The comment has been removedAnonymous
March 25, 2008
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. Why?Anonymous
March 25, 2008
The comment has been removedAnonymous
March 26, 2008
The comment has been removedAnonymous
March 26, 2008
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?Anonymous
March 26, 2008
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.Anonymous
March 26, 2008
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?Anonymous
March 26, 2008
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.Anonymous
March 26, 2008
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.)Anonymous
March 26, 2008
The comment has been removedAnonymous
March 26, 2008
The comment has been removedAnonymous
March 28, 2008
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.Anonymous
March 30, 2008
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.aspxAnonymous
March 30, 2008
Having read through that lot, I found that the steps in part 2 fixed it for me: http://blogs.technet.com/jhoward/archive/2008/03/28/part-2-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 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!Anonymous
April 17, 2008
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.Anonymous
April 11, 2011
links are broken, where are these programs nowAnonymous
April 11, 2011
links are broken, where are these programs now