WMI Plugin

The WMI plugin requires device specific configuration and is therefore disabled on new devices by default. The WMI plugin enables you to monitor Windows Management Instrumentation data. WMI data includes: CPU usage, ASP.NET, hard drive usage, and memory usage monitors. WMI data can appear in graphs, TopN reports, thresholds, and other workflows. You can mix match WMI and SNMP to create logical thresholds.

To poll WMI metrics from a device, you must create a WMI proxy server that communicates with SevOne NMS and you must enable the device to send WMI data to the WMI proxy server. The WMI plugin polls the WMI object types you enable on the Object Types page. Perform the following steps to enable the WMI plugin for each device from which you want to poll WMI metrics. Please refer to section Enable WMI in SevOne NMS System Administration Guide for details.

Note: FYI
Internal testing shows that the proxy service can handle 500 client load with 4500 objects.
The WMI Proxy server used was Window Server 2012 VM with 4 vCPUs, 8GB RAM, and 40GB Hard Drive.
  1. From the navigation bar, click the Devices menu and select Device Manager.
  2. Either add a device with the WMI plugin or edit a device to enable the WMI plugin.
  3. triangledown - Click the plugin drop-down (displays SNMP by default) and select WMI.
  4. Select the WMI Capable check box.
  5. Click the Proxy drop-down and select the WMI proxy server from which to poll WMI data for the device. If the applicable WMI proxy does not appear in the drop-down list, click the WMI Proxies Can Be... link to access the Cluster Manager > Cluster Settings tab where you create and edit WMI proxies.
  6. In the Username field, enter the user name the proxy needs to authenticate onto the device.
  7. In the Password field, enter the password the proxy needs to authenticate onto the device.
  8. In the Workgroup/Domain field, enter the workgroup (or domain) for the device.
  9. Click the Authentication drop-down and select the authentication level to use to access the device. This is typically set to Default. You may need to experiment here and select an Advanced authentication method. Settings that work in most environments are Default or Packet.
  10. Click the Impersonation drop-down and select the impersonation level to use to access the device. This is typically set to either Default or Impersonate.
  11. Select the Use NTLM check box if your network uses the NT LAN Manager suite of Microsoft security protocols. Kerberos has replaced NTLM as the default authentication protocol in an Active Directory based single sign-on scheme. Leave clear if your network uses Kerberos.