WMI polliung not working for some servers in a new Orion instance

I am in the process of building out a new Orion 2022.4.1 instance and am finding that some Windows 2019 servers cannot be polled using the same credential that works in the old instance. Old polling engine is successful at polling, but the new polling engine is not. What should I check? Logs that might show what is going on?

Keep in mind that this is happening on only a few servers. Ideas anyone? Thanks so much for any pointers?

Find more posts tagged with

failure

WMI

Polling

Accepted answers

All comments

JaroslawLadyga

I meet that from time to time and my guess is the server's Windows Defender Firewall or general Microsoft security settings on the server.

marcrobinson

Agreed @JaroslawLadyga that windows firewall settings should be looked at. Consider using wireshark to monitor the traffic from the new polling engine - if the wmi call is refused by the target server, then its definitely firewall/security. There are some collector logs and DCOM errors in windows event logs that show up for WMI errors. But checking the firewall/security is usually quicker. If these servers are in a segregated vlan, make sure the new polling engine has access to it.

stevenstadel

WMI troubleshooting. Verify WMI connectivity for Orion Platform products (solarwinds.com)