Solved: WMI: wmitrack.ini - using different namespaces

mfranz · ‎Oct 15, 2019

Hi,

I've just looked into a customer request for collecting display details. Data is available via WMI, so extending the wmitrack.ini seems logical.

Unfortunately the namespace (root\WMI) of the class differs from the default one (root\cimv2). Is there a way to extend the list of namespaces, the agent is looking into?

Best regards,

Markward

ChrisG · ‎Oct 15, 2019

As far as I know, the FlexNet agent is only able to gather WMI data from the root\cimv2 namespace.

(Did my reply solve the question? Click "ACCEPT AS SOLUTION" to help others find answers faster. Liked something? Click "KUDO". Anything expressed here is my own view and not necessarily that of my employer, Flexera.)

View solution in original post

ChrisG · ‎Oct 15, 2019

As far as I know, the FlexNet agent is only able to gather WMI data from the root\cimv2 namespace.

(Did my reply solve the question? Click "ACCEPT AS SOLUTION" to help others find answers faster. Liked something? Click "KUDO". Anything expressed here is my own view and not necessarily that of my employer, Flexera.)