2.5.2 For Hyper-V

(a) Environment settings required for connection

The following settings are required in order to set WMI:

• User account settings

  To use WMI, you must have accounts for the PFM - RM host and the monitored host.

  • Account for the PFM - RM host

    To set up an account, specify the appropriate values for HostUserID, HostPassword, and HostDomain, as shown in Table 2-5. You specify this account when you set up an instance.

    If you run PFM - RM for Virtual Machine in a cluster system, set up an account for the PFM - RM host in such a manner that the same user name and password can be used to log on to both the running system and the standby system.

    If Hyper-V on a PFM - RM host is included in the target hosts to monitor their instances, use either of the following users with the instance settings:

    1. Built-in Administrator user

    2. Member of Performance Log Users or Performance Monitor Users group and Hyper-V Administrators group

    Also, in a domain environment, specify the computer name of the PFM - RM host for HostDomain (it might be different from the host name in the hosts file or DNS system).

  • Account for the monitored host

    To set up an account, specify the appropriate values for UserID, Password, and Domain, as shown in Table 2-8. You specify this account when you set up the monitoring target.

    The account to be used either following User.

    For Domain account user :

    1. Domain Administrator's user.

    For Local account user :

    1. Built-in Administrator's user.

    2. Member of Administrators group^#.

    3. Member of Performance Log Users or Performance Monitor Users group and Hyper-V Administrators group.

    If you monitor Hyper-V on a PFM - RM host, do not specify the account for the monitoring-target host (UserID, Password, and Domain).

  #

  If used member of the administrators group(other than Built-in Administrator's account user), UAC restricts the permissions, causing the user to log on as a general user. As a result, performance information might not be acquired due to denial of access.

  To prevent this, disable UAC or execute the following command on the monitoring target:

  reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v LocalAccountTokenFilterPolicy /t REG_DWORD /d 1 /f

  To override the settings specified by the above command and restore the previous status, execute the following command:

  reg delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v LocalAccountTokenFilterPolicy /f

• WMI service settings

  Set the monitored host's WMI service startup to a setting other than Disabled. If it is set to Disabled, performance data cannot be collected.

(b) Setting DCOM

This subsection describes how to set DCOM on the PFM - RM host and the monitored host.

• Setting on the PFM - RM host

To set DCOM on the PFM - RM host:

1. In Windows, choose Start, and then Run.

2. Enter dcomcnfg.exe, and then click the OK button.

   The Component Services window appears.

   

3. Click Component Services, then Computers to expand the tree.

   

4. Choose My Computer and then, from the right-click menu, choose Properties.

   The My Computer Properties dialog box appears.

   

5. Choose the Default Properties tab, and then select Enable Distributed COM on this computer.

   

6. Click the OK button.

   The My Computer Properties dialog box closes.

7. Restart the host.

   This is necessary only when the Enable Distributed COM on this computer setting has been changed.

• Setting on the monitored host

  This subsection describes how to set DCOM on the monitored host.

To set DCOM on the monitored host:

1. In Windows, choose Start and then Run.

2. Enter dcomcnfg.exe, and then click the OK button.

   The Component Services window appears.

3. Click Component Services, then Computers, to expand the tree.

4. Choose My Computer and then, from the right-click menu, choose Properties.

   The My Computer Properties dialog box appears.

5. Choose the Default Properties tab, and then select Enable Distributed COM on this computer.

   

6. Select the COM Security tab and then, in Access Permissions, click the Edit Limits button.

   

   The Access Permission dialog box appears.

   Check if the user who connects to the monitored host or the group to which this user belongs is displayed in Group or user names.

   If the user or its group is not displayed, click the Add button and add the user or the group.

7. In Group or user names, select the user that connects to the monitored host or the group to which this user belongs.

   Check that the check box for Allow is selected for Remote Access. If this check box is cleared, select it.

   

8. Click the OK button.

   The Access Permission dialog box closes.

9. Select the COM Security tab and then, in Launch and Activation Permissions, click the Edit Limits button.

   

   The Launch and Activation Permission dialog box is displayed.

   Check if the user who connects to the monitored host or the group to which this user belongs is displayed in Group or user names.

   If the user or its group is not displayed, click the Add button and add the user or the group.

10. In Group or user names, select the user that connects to the monitored host or the group to which this user belongs.

    Check that the check boxes for Allow are selected for Remote Launch and Remote Activation. If these check boxes are cleared, select them.

    

11. Click the OK button.

    The Launch and Activation Permission dialog box closes and the My Computer Properties dialog box is displayed.

12. Click the OK button.

    The My Computer Properties dialog box closes.

13. Restart the host.

    This is necessary only when the Enable Distributed COM on this computer setting has been changed.

(c) Setting a firewall

If the Windows firewall is enabled, you must perform this setting.

To set a firewall:

1. In Windows, choose Start and then Run.

2. Enter gpedit.msc, and then click the OK button.

   The Local Group Policy Editor window is displayed.

   

3. Click Computer Configuration, Administrative Templates, Network, Network Connections, and Windows Firewall in this order to expand the tree.

   

4. Click Standard Profile^# and then, in the right-hand pane, from the right-click menu of Windows Firewall: Allow inbound remote administration exception, choose Properties.

   The Windows Firewall: Allow inbound remote administration exception Properties dialog box is displayed.

   

   #

   If the host is a domain environment, click Domain Profile instead.

5. Choose the Setting tab, and then select Enabled.

6. Click the OK button.

   The Windows Firewall: Allow inbound remote administration exception Properties dialog box closes.

(d) Setting a WMI namespace

To set a WMI namespace:

1. In Windows, choose Start and then Run.

2. Enter wmimgmt.msc, and then click the OK button.

   The wmimgmt - [Console Root\WMI Control (Local)] window is displayed.

   

3. Choose WMI Control (Local) and then, from the right-click menu, choose Properties.

   The WMI Control (Local) Properties dialog box is displayed.

   

4. On the Security page, click Root and then CIMV2, and then select CIMV2.

   

5. Click the Security button.

   The Security for ROOT\CIMV2 dialog box is displayed.

   Check if the user who connects to the monitored host or the group to which this user belongs is displayed in Group or user names. If the user or its group is not displayed, click the Add button and add the user or the group.

6. In Group or user names, select the user that connects to the monitored host or the group to which this user belongs.

   Check if the check boxes for Allow are selected for Enable Account and Remote Enable. If these check boxes are cleared, select them.

   

7. Click the OK button.

   The Security for ROOT\CIMV2 dialog box closes and the WMI Control (Local) Properties dialog box is displayed.

8. On the Security page, click Root and then Virtualization, and then select Virtualization.

   

9. Click the Security button.

   The Security for ROOT\virtualization dialog box is displayed.

   Check if the user who connects to the monitored host or the group to which this user belongs is displayed in Group or user names. If the user or its group is not displayed, click the Add button and add the user or the group.

10. In Group or user names, select the user that connects to the monitored host or the group to which this user belongs.

    Check if the check boxes for Allow are selected for Enable Account and Remote Enable. If these check box are cleared, select them.

    

11. Click the OK button.

    The Security for ROOT\virtualization dialog box closes and the WMI Control (Local) Properties dialog box is displayed.

12. On the Security page, click Root, virtualization, and V2, and then select V2. (In Windows Server 2012 R2 or later)

13. Click the Security button. (In Windows Server 2012 R2 or later)

    The Security for ROOT\virtualization\v2 dialog box is displayed.

    Check if the user who connects to the monitored host or the group to which this user belongs is displayed in Group or user names. If the user or its group is not displayed, click the Add button and add the user or the group.

14. In Group or user names, select the user that connects to the monitored host or the group to which this user belongs. (In Windows Server 2012 R2 or later)

    Check if the check boxes for Allow are selected for Enable Account and Remote Enable. If these check boxes are cleared, select them.

15. Click the OK button. (In Windows Server 2012 R2 or later)

    The Security for ROOT\virtualization\v2 dialog box closes and the WMI Control (Local) Properties dialog box is displayed.

16. Click the OK button.

    The WMI Control (Local) Properties dialog box closes.

17. In the wmimgmt - [Console Root\WMI Control (Local)] window, from the File menu, choose Exit to close the window.