Hi Dojo,
We are using the Microsoft Platform protocol to monitor some servers and we are seeing the WMI data not being returned correctly for VMs that are running Server 2019. This is resulting in the Services table, whilst initially populating with data, suddenly loosing all of it's rows of data, which means that alarms do not work correctly.
Where we are using the same version of the protocol on a Server 2016 VM, we do not see this issue and all data is correctly returned. Both VMs are being accessed with the same service account and are in the same VLAN.
Performing local queries with Windows Management Instrumentation Tester works fine when performing a manual query.
Has anyone seen this behavior or have any suggestions as to how to resolve?
Hi Dave,
Please could you let us know which version of the connector are you using?
I performed a quick test using 1.1.3.17 and the connector is able to populate correctly the Service Table.
Hi Dave,
I tested version 6.0.0.3 and I was not able to reproduce this issue.
In case you are still facing this issue, please could you contact Techsupport team (techsupport@skyline.be)? In that way we can investigate in more detail this issue.
Hi Miguel,
We are seeing this behavior when using 6.0.0.2
Strangely, I duplicated the element and set the copy to 1.1.3.10 and it seemed to work correctly – how we require some of the additional functionality that is present in 6.0.x
Looking in more detail it feels like occasionally the data is getting through. Every so often the Services table does populate. So I don’t know if something is blocking some of the responses or the responses are taking too long and are perceived as not received.
Dave