Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Overview

In NMIS version 8.6.0 we've added support for collecting data from Windows systems using the Windows Management Instrumentation infrastructure (or short WMI).
This this page describes how to approach modelling devices for WMI, and where WMI modelling differs from modelling for SNMP.

...

Besides using the standard Widows models that NMIS ships with as examples, you will likely also need to consult the online WMI reference documentation for determining what is available in the WMI universe where and how to tell NMIS about it.

WMI Troubleshooting

wmi is supposed to accept a user in the following format: 

  • domain/username
  • username@domain
  • username

In the inside, NMIS calls the windows wmic client using the following parameters:

Code Block
/usr/local/nmis8/bin/wmic --delimiter=rvqbfzsfzd -A /tmp/authfile //HOST_IP "select * from win32_operatingsystem"

To test this exactly command, a file /tmp/authfile with the following information is needed:

Code Block
username = user
password = name

We should not expect the same data as the one collect by SNMP. WMI can work without snmp, but WMI data structure is different. We should probably expect data in the interfaces, system and systemHealth sections.

Even though, the model should be discovered automatically, the same as in SNMP. 

WMI Modelling in a nutshell

Let's examine an example model:

...

  • It is not possible for a systemHealth section to have both snmp and  wmi sections.
    This is because only one index per systemHealth section is supported, but wmi and snmp can not share that single index.
  • At this time, collection of the following types of statistics from WMI is not supported:
    Network Interfaces
    Environment Data
    CBQoS Data
    Calls
    Server-type processor and load information
  • NMIS does not yet support service tests for WMI-sourced process information.
  • Collection of indexed WMI sections is not optimised for maximum efficiency yet.
    query results are reused to some extent but not universally, and further optimisations are planned.
  • The GUI model editor does not support editing of WMI sections yet.

...