Hi,
A customer needs to enable the WMI (Windows Management Instrumentation) feature on each machine where PcVue is running.
PcVue 15.2
Windows 10 Pro 22H2
Windows Server 2019 Standard
Do you know if it is compatible with PcVue? Any experience?
Thank you!!
Claudia
Hi Claudia,
Depends on the customer expectation.
If the goal is to activate WMI on hosts where PcVue is intalled to monitor some OS-level metrics, including generic metrics about running process and host ressources, there is no reason PcVue would be an issue.
In addition, and just in case, be aware that the processes of PcVue do not expose product-specific metrics to WMI. Would be good to expose our audits/system vars via WMI, but this is not yet the case.
In this field, you may hear about Prometheus also, a tool designed to aggregate such metrics and perform computation on them (stats, trends, alerts..).
Any feedback on that is welcome, not enough feedback from product users (and their IT teams) to engage in this evolution that would facilitate the monitoring for product users in production.
Thank you
WMI and Prometheus are used more and more as a replacement of the SNMP Agent (as we know it in PcVue) to centralize metrics related to activity on computer hosts in a networked system.
Hi Benoit,
Thank you for your answer!
With this tool they want to collect information on updates, OS versions, applications, etc. to manage vulnerabilities and updates on the machines.
Indeed, I will tell the customer that in the case of PcVue they will not be able to collect such data, but for the rest of the app you will be able to use WMI. And, if possible, share his experience with us.
BR,
Claudia
I am not an expert in this, but the kind of information you mention are the basics. These are typically information the OS knows about. Our installation packages are based on Windows Installer, anything about the installed packages, date of install, version, install path... is typically known by the OS (you see them in the OS Settings, they are for sure exposed via WMI). The customer should have no issue to get them.
Basic metrics related to resource usage also. Think allocated memory or nb of threads for the Sv32.exe or Hds.exe process, and anything you have access to via the Task Manager or Perfmon is also exposed through OS generic metrics with WMI.
What you will not get via WMI is the kind of metrics that only Sv32.exe knows about. Think Networking connection status, connection duration, BACnet or any other driver connection status, amount of memory or threads used by a given manager within the process... All of this could be exposed via WMI if we had implemented an extension. But it is not the case (yet).


