How to remotely manage hyper-V server R2 SP1 configuration in the Working Group Environment win 7 (2)

The last article mentioned that connecting to the hyper-V server using the hyper-V Remote Management tool on win7 fails, so this article will solve this problem:

I. First, create the same account and password on the hyper-V server and win7 respectively, and the specific operations will not be described in detail.

2. Go to the Microsoft website to download the hvremote. WSF script. The download link is http://archive.msdn.microsoft.com/HVRemote/Release/ProjectReleases.aspx? Releaseid = 3084 (it is not a common problem to configure remote management of hyper-V servers in a working group environment. The necessary permissions must be activated for servers and clients. Fortunately, Microsoft provides related scripts)

3. Open the download link and download hvremote. WSF. You can also download hvremote documentation to learn about the installation instructions. copy the WSF file to any disk on Windows 7 and hyper-V servers for storage. I put it on disk D. perform the following steps to perform the Configuration:

1. Go to the hyper-V server disk D and run cscript hvremote. WSF/Add: User Name (the user name is the same account name created in step 1. Here I will demonstrate it with new)

2. Run the command on win7, go to the disk D where hvremote. WSF is located, and run the cscript hvremote. WSF/MMC: enbale command to add a firewall policy.

3. Execute cscript hvremote. WSF/anondcom: grant on win7. This command allows anonymous access to the DCOM component.

4. After the preceding three commands are executed on hyper-V and win7 respectively, restart hyper-V and win7.

After the server and client are restarted, we open the win7 hyper-V remote management tool and try to connect to the server. However, the RPC error occurs again. See:

Why? See the next breakdown:How to remotely manage hyper-V server R2 SP1 configuration in the Working Group Environment win 7 (3)