Users Guide

WMI Troubleshooting Procedures | Troubleshooting
OMNM 6.5.3 User Guide 721
–Remote Enable
6 Click Advanced , and then select the user account that accesses this computer.
7 Click Edit , select This namespace and subnamespaces in the Apply to field, and then click
OK .
8 Click OK on the Advanced Security Settings for CIMV2 window.
9 Click OK on the Security for Root\CIMV2 window.
10 Click Services in the left navigation pane of Computer Management .
11 Select Windows Management Instrumentation in the Services result pane, and then click
Restart .
Disabling Remote User Account Control for Workgroups
If you are monitoring a target in a workgroup, you must disable remote User Account Control
(UAC). Although this is not recommended, it is necessary when monitoring a workgroup computer.
Disabling remote user account control does not disable local user account control functionality.
CAUTION:
The following modifies or creates a registry key. Changing the registry can have adverse effects on your
computer and may result in an unbootable system. Best practice is to back up your registry before
making these changes.
To disable remote UAC for a workgroup computer:
1 Log on to the host you want to monitor as an administrator.
2 Click Start > Run, and enter regedit .
3 Expand
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Poli
cies\System.
4 Locate or create a DWORD entry named LocalAccountTokenFilterPolicy and provide a
DWORD value of 1.
NOTE:
To re-enable remote UAC, change the DWORD value to 0.
Add a Windows Firewall Exception for Remote WMI Connections
If the target computer has Windows Firewall enabled, it must have a Remote WMI exception to
allow remote WMI traffic through (See
/msdn.microsoft.com/en-us/library/
aa389286(VS.85).aspx
). Follow these steps to add this exception:
1 Open a command shell (Click Start > Run , type cmd and then press [Enter]).
2 At the command prompt, type
netsh firewall set service RemoteAdmin enable
Press [Enter]
3 Typ e exit then press [Enter].
If adding the firewall exception did not solve your problem, see
Additional WMI Troubleshooting
below.