Hyper-V Remote Administration Tools
Microsoft released the Hyper-V Remote Management tools for Windows Vista earlier this week. This is an important release to effectively managing a remote Hyper-V server now that in Hyper-V RC0 mouse movement is no longer being captured in a virtual machine connection when connected to a Hyper-V RC0 server via terminal services (Remote Desktop). Microsoft reportedly blocked capturing the mouse due to erratic mouse movement in terminal services. However, I never experienced these mouse issues in my lab environment with Hyper-V Beta.
If you’re looking to manage your server with a mouse your options are to either be in front the physical server on the console session, use the Hyper-V MMC console from another Windows Server 2008 server or a Windows Vista PC with the new Hyper-V Remote Management tools. The alternative is to learn to control the VMs using just the keyboard via terminal services, YUCK! Talk about being caught in a bag and can’t get out.
Download the Vista tools:
x86: Update for Windows Vista (KB949758)
x64: Update for Windows Vista x64 Edition (KB949758)
So far I have not gotten the Hyper-V Remote Management tools for Vista working in my lab environment. Currently, I am getting the error “Cannot connect to the RPC service on computer ‘<computername>’. Make sure your RPC service is running.”
Possible issues are….
-
The Hyper-V server and Vista PC are in a workgroup and there could be authentication issues.
-
The firewall on the Hyper-V server is not properly configured.
-
Ben Armstrong talks about enabling WMI between the computers on his blog post.
-
??
Update 3/27/08 8:15AM CDT: After getting the Hyper-V server and the Vista PC added to the active directory domain, I now get the message “You do not have the required permission to complete this task. Contact the administrator of the authorization policy for the computer <computer name>” when trying to connect to the server via Hyper-V Manger in Vista. Disabling the firewall on the server didn’t resolve this issue.
Update 3/27/08 11:28AM CDT: I finally got the Hyper-V Manger running in Vista. For me the key to success was the following:
-
Make the Hyper-V server and Vista both a member of the same domain.
-
Added the user id in which I logged in on my Vista PC as a member of the local administrators group on the Hyper-V server.(This is not necessary if the Hyper-V Manager is started with “Run as Administrator” on a Vista PC signed on as a local user with UAC turned ON. See this blog post.) -
Make sure “Hyper-V” and “Hyper-V Management Clients” firewall group exceptions are enabled (exceptions ON by default). No other firewall exceptions seemed to be needed (i.e. Remote Administration or Windows Management Instrumentation)
- Restart the Hyper-V server.
-
Make sure the DCs are up and running.
Update 3/31/08 10:24AM: Running the Hyper-V Manager in Vista really doesn’t help with the mouse control issue. Yes, the mouse is there, but it is unusable until the Integration Services are installed in Windows Server 2003 VM or an Update is applied to Windows Server 2008 VM. Seems like I will have to get use to using the keyboard to get the Integration Services or the Update installed in the VMs.
I cannot make this work without both machines being the same domain. I have tied several things on my own as well as attempted to follow suggestions from around the Net.
Seems to be a “real” issue.
Raansoon
March 27, 2008 at 11:19 pm
Hello,
Recently I installed Win2008 RC1 SP1 v.735 64Bit with Hyper-V (version 6.0.6001.17101) so after configuring the VHD when the system boots up and when the logon screen appears I cant use the mouse neither keyboard, but on the underneath tab I can see a message “To release your mouse press CTRL+ALT+LEFT ARROW – I tried to do this but I cant use the mouse and keyboard.
Secondly the screen of the VM PC is quit big and it is not fitting into the screen,
So could you please help me in this regards – is there any patch or hotfix to slove this issue…
Note: I checked this URL http://download.microsoft.com/download/e/4/8/e48d5cff-53d2-4eed-85bf-4af50e25b78c/relnotes.htm it says check the Integrated Services” i checked but i coudnt find much intersting stuff.
Waiting for your response
Mohammed Salhauddin
March 31, 2008 at 7:47 am
Mohammed Salhauddin:
I would start off updating your environment with Windows Server 2008 RTM. The evaluation version can be found here: http://technet.microsoft.com/en-us/evalcenter/cc137123.aspx
Then downloaded the latest version of Hyper-V which is RC0 here: http://www.microsoft.com/downloads/details.aspx?FamilyId=DDD94DDA-9D31-4E6D-88A0-1939DE3E9898&displaylang=en
Even after doing so, you will notice that the new version of Hyper-V no longer accepts mouse movement in the VM if you use Remote Desktop to get the Hyper-V server.
If you are in front of the physical server, you will have mouse and keyboard control. Howerver, the mouse movement may be erratic until you get Integration Services installed in Windows Server 2003 VM or get the following update installed on a Windows Server 2008 VM: http://www.microsoft.com/downloads/details.aspx?FamilyId=B7464B44-821D-4A7C-9D9C-7D74EC14437C&displaylang=en
You will need to get comfortable controlling windows with a keyboard in order to get the Integration Services or the Update installed.
Note: the easiest way to get the update installed in a Windows Server 2008 VM is to make an ISO image containing the update and mounting it to the VM.
Drew
March 31, 2008 at 9:03 am
Checkout John Howards blog posts on how to get Hyper-V working in a WORKGROUP scenario.
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’
PART1 – 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
Part 2 – 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
Part 3 – http://blogs.technet.com/jhoward/archive/2008/03/30/part-3-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
Drew
March 31, 2008 at 9:10 am
I have the same issue regarding remote management of my hyper-v server in a workgroup environment… Been looking all over the net, and no one seems to know what the problem is
Martin
November 8, 2008 at 2:10 pm
One day Microsoft will learn to make things simple. It should be a snap to connect to the hyper-v server and get to work, but no, all I get is;
Cannot connect to the RPC service on computer
I’ve made all the adjustments different guru’s have suggested to no avail.
Mathew
November 13, 2008 at 3:22 am
Tried thsi as well and just gets the rpc error. I gues this application is still broken. Could be resolve issue for me since i dont have a dns server. But requiering dns server for a local test virtualization machine is just plain retarded if thats the case. Since when did ip connection become a problem? Only MS can create such crap.
Bserz
March 13, 2009 at 6:12 pm