http://download.microsoft.com/download/C/1/C/C1CA233D-CA1A-4C4D-8240-B4AFC0FD3433/Windows6.1-KB958830-x64-RefreshPkg.msu

Hyper-V

https://www.microsoft.com/zh-CN/download/details.aspx?id=3702

https://www.microsoft.com/zh-CN/download/details.aspx?id=7887

Version of Hyper-V Tools Version of Hyper-V Windows Client Operating System
     

Remote Server Administration Tools for Windows 7 (http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=7d2f6ad7-656b-4313-a005-4e344e43997d)

Windows Server 2008 R2

Windows Server 2008 SP2

Windows Server 2008, with Hyper-V RTM update installed (KB950500)

Windows 7 Enterprise, Windows 7 Professional, or Windows 7 Ultimate editions)

Windows Server 2008 R2

Windows Server 2008 R2

Windows Server 2008 R2 (which versions?)

Update for Windows Vista Service Pack 2 Management Tools for Hyper-V (KB970203) http://www.microsoft.com/downloads/details.aspx?familyid=551A9B83-241B-4E86-B329-441374DDCF23&displaylang=en

Windows Server 2008 Service Pack 2 (SP2)

??

Windows Server 2008 32-bit or 64-bit, as follows:

For 32-bit, download and apply update NNN. For 64-bit, NNN

Windows Vista, download and apply update KB952627 http://support.microsoft.com/kb/952627

Windows Server 2008, with Hyper-V RTM update installed (KB950500)

Windows Vista Service Pack 1 (SP1) (Supported on Windows°Vista Ultimate with SP1, Windows°Vista Enterprise with SP1, and Windows°Vista Business with SP1) http://www.microsoft.com/downloads/details.aspx?familyid=BF909242-2125-4D06-A968-C8A3D75FF2AA&displaylang=en

Update for Windows Vista Service Pack 2 Management Tools for Hyper-V (KB970203) http://www.microsoft.com/downloads/details.aspx?familyid=551A9B83-241B-4E86-B329-441374DDCF23&displaylang=en

Windows Server 2008, with Hyper-V RTM update installed (KB950500)

Windows Vista Service Pack 2 (SP2)

Hyper-V Remote Management Update for Windows Vista for x64-based Systems (KB952627) http://www.microsoft.com/downloads/details.aspx?familyid=88208468-0AD6-47DE-8580-085CBA42C0C2&displaylang=en

Windows Server 2008, with Hyper-V RTM update installed (KB950500)

 

Installing the management tools

 

Before you install the management tools, you might need to obtain an update package that includes the tools. The table in the previous section identifies the operating systems for which the tools are distributed in an update package. The table also contains links to the update packages

To install the management tools on Windows 7 or Windows Vista SP1

 
  1. Download the update package and then double-click the .msu file.

  2. If you are installing the tools on a supported version of Windows Vista SP1, no additional installation steps are required, so you can proceed to the configuration instructions.

To install the management tools on Windows Server

 
  1. If you are installing a version that is distributed in an update package, do one of the following:

  2. Open Server Manager. (If Server Manager is not running, click Start, point to Administrative Tools, click Server Manager, and then, if prompted for permission to continue, click Continue.)

  3. In Server Manager, under Features Summary, click Add Features.

  4. On the Select Features page, expand Remote Server Administration Tools, and then expand Remote Administration Tools.

  5. Click Hyper-V Tools, and then proceed through the rest of the wizard.

Configuring the management tools

 

The configuration process consists of modifying various components that control access and communications between the server running Hyper-V and the computer on which you will run the Hyper-V management tools.

Note
No additional configuration is required if you are using the management tools on a computer running Windows Server 2008 and the same user account is a member of the Administrators group on both computers.

Configuring the server running Hyper-V

 

The following procedures describe how to configure the server running Hyper-V. When domain-level trust is not established, perform all the steps. When domain-level trust exists but the remote user is not a member of the Administrators group on the server running Hyper-V, you must modify the authorization policy, but you can skip the steps for modifying the Distributed COM Users group and the Windows Management Instrumentation (WMI) namespaces.

Note
The following procedures assume that you have installed the Hyper-V role on the server. For instructions about installing the Hyper-V role, see Install the Hyper-V Role on a Full Installation of Windows Server 2008 or Install the Hyper-V Role on a Server Core Installation of Windows Server 2008.

To configure the Hyper-V role for remote management on a full installation of Windows Server 2008

 
  1. Enable the firewall rules for Windows Management Instrumentation. From an elevated command prompt, type:

    netsh advfirewall firewall set rule group=“Windows Management Instrumentation (WMI)” new enable=yes

    The command has succeeded when it returns the following message: “Updated 4 rules(s). Ok.”

    Note
    To verify that the command succeeded, you can view the results in Windows Firewall with Advanced Security. Click Start, click Control Panel, switch to Classic View if you are not using that view, click Administrative Tools, and then click Windows Firewall with Advanced Security. Select inbound rules or outbound rules and then sort by the Group column. There should be three inbound rules and one outbound rule enabled for Windows Management Instrumentation.

  2. The next steps configure the authorization policy for the server running the Hyper-V role. If the user who requires remote access to the server running Hyper-V belongs to the Administrators group on both computers, then it is not necessary to configure the authorization policy.

    Note
    The instructions for configuring the authorization policy assume that the default authorization policy has not been modified, including the default location, and that the account you are configuring for remote access requires full administrative access to the Hyper-V role.

  3. Click Start, click Start Search and type azman.msc. If you are prompted to confirm the action, click Continue. The Authorization Manager MMC snap-in opens.

  4. In the navigation pane, right-click Authorization Manager and click Open Authorization Store. Make sure that XML file is selected. Browse to the %system drive%\ProgramData\Microsoft\Windows\Hyper-V folder, select InitialStore.xml, click Open and then click OK.

    Note
    The Program Data folder is a hidden folder by default. If the folder is not visible, type: <system_drive>\ProgramData\Microsoft\Windows\Hyper-V\initialstore.xml

  5. In the navigation pane, click Hyper-V services, and then click Role Assignments. Right-click Administrator, point to Assign Users and Groups, and then point to From Windows and Active Directory. In the Select Users, Computers, or Groups dialog box, type the domain name and user name of the user account, and then click OK.

  6. Close Authorization Manager.

  7. Next, you add the remote user to the Distributed COM Users group to provide access to the remote user. Click Start, point to Administrative tools, and click Computer Management. If User Account Control is enabled, click Continue. Component Services opens.

  8. Expand Local Users and Groups, and then click Groups. Right-click Distributed COM Users and click Add to Group.

  9. In the Distributed COM Users Properties dialog box, click Add.

  10. In the Select Users, Computers, or Groups dialog box, type the name of the user and click OK.

  11. Click OK again to close the Distributed COM Users Properties dialog box. Close Component Services.

  12. The remaining steps grant the required WMI permissions to the remote user for two namespaces: the CIMV2 namespace and the virtualization namespace. Click Start, click Administrative Tools, and then click Computer Management.

  13. In the navigation pane, click Services and Applications, right-click WMI Control, and then click Properties.

  14. Click the Security tab, click Root, and then click CIMV2. Below the namespace list, click Security.

  15. In the Security for ROOT\CIMV2 dialog box, check to see if the appropriate user is listed. If not, click Add. In the Select Users, Computers, or Groups dialog box, type the name of the user and click OK.

  16. On the Security tab, select the name of the user. Under Permissions for <user or group name>, click Advanced. On the Permissions tab, verify that the user you want is selected and then click Edit. In the Permission Entry for CIMV2 dialog box, modify three settings as follows:

    • For Apply to, select This namespace and subnamespaces.
    • In the Permissions list, in the Allow column, select the Remote Enable check box.
    • Below the Permissions list, select the Apply these permissions to objects and/or containers within this container only check box.
  17. Click OK in each dialog box until you return to the WMI Control Properties dialog box.

  18. Next, you repeat the process for the virtualization namespace. Scroll down if necessary until you can see the virtualization namespace. Click virtualization. Below the namespace list, click Security.

  19. In the Security for ROOT\virtualization dialog box, check to see if the appropriate user is listed. If not, click Add. In the Select Users, Computers, or Groups dialog box, type the name of the user and click OK.

  20. On the Security tab, select the name of the user. Under Permissions for <user or group name>, click Advanced. On the Permissions tab, verify that the user you want is selected and then click Edit. In the Permission Entry for virtualization dialog box, modify three settings as follows:

    • For Apply to, select This namespace and subnamespaces.
    • In the Permissions list, in the Allow column, select the Remote Enable check box.
    • Below the Permissions list, select the Apply these permissions to objects and/or containers within this container only check box.
  21. Click OK in each dialog box and then close Computer Management.

  22. Restart the server to apply the changes to the authorization policy.

To configure the Hyper-V role for remote management on a Server Core installation of Windows Server 2008

 
  1. Enable the firewall rules on the server for Windows Management Instrumentation. From an elevated command prompt, type:

    netsh advfirewall firewall set rule group=“Windows Management Instrumentation (WMI)” new enable=yes

    The command has succeeded when it returns the following message: “Updated 4 rules(s). Ok.”

  2. Next, you modify the Distributed COM permissions to provide access to the remote user. Type:

    net localgroup “Distributed COM Users” /add <domain_name>\<user_name>

    where <domain_name> is the domain that the user account belongs to and <user_name> is the user account you want to grant remote access to.

  3. Next, you connect remotely to the server running the Server Core installation so you can modify the authorization policy and the two WMI namespaces, using MMC snap-ins that are not available on the Server Core installation.

    Log on to the computer on which you will run the Hyper-V management tools, using a domain account that is a member of the Administrators group on the computer running a Server Core installation. (If you need to add this user, see the instructions inInstall the Hyper-V Role on a Server Core Installation of Windows Server 2008.)

    Note
    The instructions for configuring the authorization policy assume that the default authorization policy has not been modified, including the default location, and that the account you are configuring for remote access requires full administrative access to the Hyper-V role.

  4. Click Start, click Start Search and type azman.msc. If you are prompted to confirm the action, click Continue. The Authorization Manager snap-in opens.

  5. In the navigation pane, right-click Authorization Manager and click Open Authorization Store. Make sure that XML file is selected and type:

    \\<remote_computer>\c$\ProgramData\Microsoft\Windows\Hyper-V\initialstore.xml

    where <remote_computer> is the name of the computer running the Server Core installation.

    Click Open and then click OK.

  6. In the navigation pane, click Hyper-V services, and then click Role Assignments. Right-click Administrator, point to Assign Users and Groups, and then point to From Windows and Active Directory. In the Select Users, Computers, or Groups dialog box, type the domain name and user name of the user account, and then click OK.

  7. Close Authorization Manager.

  8. The remaining steps grant the required WMI permissions to the remote user for two namespaces: the CIMV2 namespace and the virtualization namespace. Click Start, click Administrative Tools, and then click Computer Management.

  9. In the navigation pane, click Services and Applications, right-click WMI Control, and then click Properties.

  10. Click the Security tab. Click Root and then click CIMV2. Below the namespace list, click Security.

  11. In the Security for ROOT\CIMV2 dialog box, check to see if the appropriate user is listed. If not, click Add. In the Select Users, Computers, or Groups dialog box, type the name of the user and click OK.

  12. On the Security tab, select the name of the user. Under Permissions for <user or group name>, click Advanced. On the Permissions tab, verify that the user you want is selected and then click Edit. In the Permission Entry for CIMV2 dialog box, modify three settings as follows:

    • For Apply to, select This namespace and subnamespaces.
    • In the Permissions list, in the Allow column, select the Remote Enable check box.
    • Below the Permissions list, select the Apply these permissions to objects and/or containers within this container only check box.
  13. Click OK in each dialog box until you return to the WMI Control Properties dialog box.

  14. Next, you repeat the process for the virtualization namespace. Scroll down if necessary until you can see the virtualization namespace. Click virtualization. Below the namespace list, click Security.

  15. In the Security for ROOT\virtualization dialog box, check to see if the appropriate user is listed. If not, click Add. In the Select Users, Computers, or Groups dialog box, type the name of the user and click OK.

  16. On the Security tab, select the name of the user. Under Permissions for <user or group name>, click Advanced. On the Permissions tab, verify that the user you want is selected and then click Edit. In the Permission Entry for virtualization dialog box, modify three settings as follows:

    • For Apply to, select This namespace and subnamespaces.
    • In the Permissions list, in the Allow column, select the Remote Enable check box.
    • Below the Permissions list, select the Apply these permissions to objects and/or containers within this container only check box.
  17. Click OK in each dialog box and then close Computer Management.

  18. Restart the computer running a Server Core installation to apply the changes to the authorization policy.

Configuring Windows Vista SP1

 

The following procedure describes how to configure Windows Vista SP1 when domain-level trust is not established.

To configure Windows Vista SP1

 
  1. Log on to the computer running Windows Vista SP1.

  2. Enable the firewall rules for Windows Management Instrumentation. From an elevated command prompt, type:

    netsh advfirewall firewall set rule group=”Windows Management Instrumentation (WMI)” new enable=yes

    The command has succeeded when it returns the following message: “Updated 8 rules(s). Ok.”

    Note
    To verify that the command succeeded, you can view the results in Windows Firewall with Advanced Security. Click Start, click Control Panel, switch to Classic View if you are not using that view, click Administrative Tools, and then click Windows Firewall with Advanced Security. Select inbound rules or outbound rules and then sort by the Group column. There should be six inbound rules and two outbound rules enabled for Windows Management Instrumentation.

  3. Enable a firewall exception for the Microsoft Management Console. From an elevated command prompt, type:

    Netsh firewall add allowedprogram program=%windir%\system32\mmc.exe name="Microsoft Management Console"

  4. Start Hyper-V Manager to verify that you can connect remotely to the server. Click Start, click the Start Search box, type Hyper-V Manager and press ENTER. If you are prompted to confirm the action, click Continue. In Hyper-V Manager, under Actions, click Connect to Server. Type the name of the computer or browse to it, and click OK. If Hyper-V Manager can connect to the remote computer, the computer name will appear in the navigation pane and the results pane will list all the virtual machines configured on the server.

Hyper-V Tools for win7的更多相关文章

  1. windows server 2008 r2 企业版 hyper v做虚拟化的相关问题处理

    windows server 2008 r2 企业版 hyper v做虚拟化的相关问题处理 今天在dell r710 上用windows server 2008 r2企业版hyper v 做虚拟化,添 ...

  2. 设置Hyper V

    1.打开服务器管理器 2.添加角色和功能 3.安装类型 -> 基于角色或基于功能的安装 4.服务器选择 -> 下一步 5.服务器角色 勾选"Hyper V"

  3. HYPER -V 独立安装的 2016版本 中文版 下载好慢啊

    HYPER -V 独立安装的 2016版本 中文版 下载好慢啊

  4. Hyper V NAT 网络设置 固定IP / DHCP

    Hyper V 默认的Default Switch同时支持了NAT网络以及DHCP,虚拟机能够访问外网. 但使用过程中发现这个IP网段经常变化,而且Hyper V没有提供管理其NAT网络与DHCP的图 ...

  5. HYPER V 文件共享 复制文件 共享硬盘 来宾服务

    虚拟机的设置   -->  集成服务 –> 来宾服务  勾选    文件就可以在本地机器和虚拟机上来回复制了. 他可让 Hyper-V 管理员在运行虚拟机的同时将文件复制到虚拟机,且无需使 ...

  6. win10自带虚拟机Hyper V联网

      在控制面板里打开程序和功能     打开启用或关闭windows 功能     勾选Hyper-V     在windows 管理工具打开Hyper-V 管理器   打开虚拟交换机管理器     ...

  7. 自带hyper -v 或者 Vmware安装Linux centos

    centos系统存在网盘,链接: https://pan.baidu.com/s/1A5ywyLjIegcftaT_xCvPbA 密码: n6v4 https://blog.csdn.net/nanc ...

  8. 在Windows 10 系统上启用Hyper V遇到的错误:0x800f0831

    Hyper-V是微软的一款虚拟化技术,是微软第一个采用类似Vmware和Citrix开源Xen一样的基于hypervisor的技术. 在Windows 10的powershell命令里,输入如下的命令 ...

  9. docker入门、LXC、windows container 和 Hyper知识基础、实用情况

    虚拟机与容器 很明显可以看出两者在操作系统级别上的隔离和进程上的隔离的区别,VM因为隔离级别更高明显更重. linux容器主要技术特点: 文件系统隔离:每个容器都有自己的root文件系统 进程隔离:每 ...

随机推荐

  1. 对象存储 - Swift 原理 及 Swift+keystone+dashboard 架构搭建

    1. 原理介绍 Swift 架构.原理及功能: http://www.cnblogs.com/sammyliu/p/4955241.html 总结的很详细也很全面,受益匪浅,感谢分享. 2. keys ...

  2. 【 总结 】linux中test命令详解

    test命令在bash shell脚本中经常以中括号([])的形式出现,而且在脚本中使用字母来表示比符号表示更专业,出错率更低. 测试标志 代表意义 文件名.文件类型 -e 该文件名是否存在 -f 该 ...

  3. python的一致性(1)sorted和len

    每个语言,都有自己的特性,而一致性,是python语言特性重要的一个环节. 比如排序,我们不是aaa.sort(),而是 sorted(aaa),比如len,不是aaa.length(),而是len( ...

  4. hdu 1411(四面体的体积)

    校庆神秘建筑 Time Limit: 2000/1000 MS (Java/Others)    Memory Limit: 65536/32768 K (Java/Others)Total Subm ...

  5. AC日记——[FJOI2007]轮状病毒 bzoj 1002

    1002 思路: 打表找规律: dp[i]=dp[i-1]*3-dp[i-2]+2; 套个高精就a了: 代码: #include <cstdio> #include <cstring ...

  6. 直接利用本地git上传项目到github

    http://m.blog.csdn.net/article/details?id=50441442 本文将详细介绍如何托管你的项目到github上   转载请标明出处: http://blog.cs ...

  7. 位运算和enum中的位运算

    1.位逻辑非运算 ~ 位逻辑非运算是单目的,只有一个运算对象.位逻辑非运算按位对运算对象的值进行非运算,即:如果某一位等于0,就将其转变为1:如果某一位等于1,就将其转变为0. 比如,对二进制的100 ...

  8. [CF480E]Parking Lot

    题意:给一个$n\times m$的网格,初始时有些地方不能选,给$k$个询问$(x,y)$,每次令$(x,y)$不能选,然后询问最大子正方形的边长 如果按原题来做,禁止选一个点对答案的影响是极其鬼畜 ...

  9. python之装饰器、生成器、内置函数、JSON

    一.装饰器: 装饰器,器在这里的意思是函数,也就是装饰函数.作用是给其他函数添加新功能,它可以不改变原有的函数,原来的函数和原来一模一样,什么都不需要改变,只需要在函数外部加上调用哪个装饰器就可以了, ...

  10. 利用Java位运算符,完成Unsigned转换(无符号)

    方案二:利用Java位运算符,完成Unsigned转换. 正常情况下,Java提供的数据类型是有符号signed类型的,可以通过位运算的方式得到它们相对应的无符号值,参见几个方法中的代码: publi ...