HVRemote was developed by
John Howard , Senior Program Manager in the Hyper-V team at Microsoft Corporation, November 2008. To contact me, follow the blog hyperlink above and use the email option. If you find a bug or want to suggest an improvement, please drop me an email or add a comment to the blog post announcing this tool. Of course, I’d love to hear from you if you find it useful.
1. Add a user rights to remotely access Hyper-V. On the server, from an elevated command prompt, run:
cscript hvremote.wsf /add:domain\user (if machine is in a domain) or cscript hvremote.wsf /add:user (if machine is in a workgroup)
2. Add a firewall exception for the Microsoft Management Console on the client if using Vista or Windows 7 client (not needed on Windows Server 2008 or Windows Server 2008 R2). On the client, from an elevated command prompt, run:
cscript hvremote.wsf /mmc:enable
3. Allow anonymous DCOM access on the client if the client and server are both in workgroups, or the client and server are in
untrusted domains (this is not needed for trusted domains or the same domain). On the client, from an elevated command prompt, run: cscript hvremote.wsf /anondcom:grant
4. Reboot server
and client if this is the first time some reconfiguration has been done.
5. Display current configuration and verify common configuration problems On the client, from an elevated command prompt, run:
cscript hvremote.wsf /show /target:servercomputername On the server, from an elevated command prompt, run:
cscript hvremote.wsf /show /target:clientcomputername
Hyper-V Remote Management Configuration Steps
Server side configuration (i.e. the machine running the Hyper-V role) consists of the following steps:
1) WMI Security permissions to the root\cimv2 namespace
2) WMI Security permissions to the root\virtualization namespace
3) Permission to the Authorisation policy store
4) Windows Firewall configuration for Hyper-V rules
5) Distributed COM remote access permission
6) (Optional) Windows Firewall configuration for WMI administration rules
7) (Optional) Disable IPSec policy if connection from management clients would be blocked
Client side configuration (i.e. the machine running Hyper-V Manager and Virtual Machine Connection) consists of the following steps:
1) Windows Firewall configuration for Hyper-V Remote Management Client rules
2) (In some scenarios:) ANONYMOUS LOGON remote DCOM access
3) (In some scenarios:) cmdkey for credentials.
4) Windows firewall exceptions for management tools