Orion Server Reporting - Using WinRm as a primary polling method failed

Good morning and Happy Monday:

I am new to this forum and new to Solar Winds - well not really - used to use it about 15 years ago. I keep getting the following alert:

Using WinRM as primary polling method failed, secondary method via WMI/RPC will be used instead.

Not sure what this means. WinRm is running on the Orion Server - should I just remove this monitor from the Orion Server only?

Thank you!

Find more posts tagged with

Accepted answers

All comments

jm_sysadmin

WinRM can be configured to replace WMI. its typically used for PowerShell remoting, but it can do a lot more as well.

Take a look at: https://thwack.solarwinds.com/resources/b/geek-speak/posts/what-is-winrm-how-do-you-configure-it
There is a free tool to configure it on a bunch of devices at once.

If you don't want to, you are mostly fine. Some AppInsight monitors (AD and Exchange) won't get all their data, and some parts of Orion like SCM leverage it.

mbeauregard

Thank you for your response. I should have been more specific. The error is coming from the Orion Server itself. All the servers/objects I am monitoring are not having any issues with WinRM. My Orion Server that is running the Orion Application is reporting the error - the WinRm on the Orion Server is running and configured.

xtraspecialj

Where are you seeing this error? In a log file maybe? Also, WinRM requires configuration on both ends. It needs to be configured on the Orion server where you need to make sure you have the TrustedHosts setting configured to allow communication to all nodes being monitored. It also needs to be setup on each Windows node you are monitoring with SAM. So in this case, even though WinRM may be configured on your Orion server, is it configured on all of your target nodes being monitored?