This is a how to guide to monitor WMI with KNM.
WMi can be used to monitor many monitors for Windows machines. The monitors are:
- Active Directory
- Bandwidth Utilization
- CPU Utilization
- Directory Property
- Disk Utilization
- File Change
- Log File
- Memory Utilization
- Process Status
- Swap File Utilization
- Windows Performance
- Windows Service Status
- WMI Query
Before you can assign WMI monitors to Windows assets, you must make sure that WMI is enabled on the machine. To do this, please check the following.
Make sure the Windows Management Instrumentation service is running.
Verify that WMI is enabled for the account you want to use to monitor it
Open the Computer Management window on the device. Expand Services and Applications. Right click WMI Control and select Properties. In the Security tab, highlight Root and click the Security button. Make sure Remote Enable is checked for the user or user group you want to use.
Make sure your firewall accepts inbound requests to the WMI service
Run this command in the command prompt:
netsh advfirewall firewall set rule group="windows management instrumentation (wmi)" new enable=yes
To test that WMI works, open run on a Windows machine and type:
This is a built in Windows utility to make WMI queries directly to the machine. When you first run the utility, click the Connect... button.
To test WMI locally, click the Connect button again. To monitor WMI from another device, use this format in the Namespace text field:
where <ip_address> is the IP of the machine you want to test WMI.
Once connected, click the Enum Classes... button and select the Recursive radial button.
If successful, you will be able to monitor the device using WMI.
Enabling WMI on the asset in KNM
To enable WMI on the asset in KNM, click the Edit link on the right side of the screen to enter the Edit Asset page. Then go to the Advanced tab and make sure the option Use WMI is checked.
If you want to monitor WMI on the agent machine where the gateway is installed, the Use WMI option MUST BE DISABLED. This is because the gateway does not need to authenticate WMI when using localhost.