Help needed, simple instructions to start monitoring agentless windows

I have a redhat icingaweb2 server, monitoring solaris and redhat servers using nagios plugins (ssh_check).
its using the default icinga (local / non AD) user and i have added ssh keys to all linux/solaris servers so icinga can ssh straight in with root privs to run nagios checks.
Now i need to start monitoring our windows servers. i need to do it agentless. does someone have an easy set up guide ? including user config ?
current config has been set up by editing config files under /etc/icinga2/conf.d (hosts files, ssh check files etc). I have lots of experience supporting and configuring unix servers, but not much windows experience.


Why agentless? Security concerns? Icinga or simply NSClient++ definitely make things easier on me. Although given how you’re using ssh for all *nix systems, I suppose the equivalent is that newer versions of Powershell support remote login. I’m not a Windows guy so I can’t break this down too specifically, but if you’ve got a dedicated Windows admin hanging around, they’d probably have a blast with this.

Here’s Microsoft’s documentation on it:

Also, if you want to run this from your Redhat boxes, Powershell does seem to be available on Linux now, but if it were me, I’d set up a satellite running Windows.


I’m not sure if WMI is still a thing, SNMP is deprecated since server 2012 to my knowledge. Having an agent on Windows ensures secure communication and on-demand checks from Icinga satellites/masters. This is best practice for such a scenario.


1 Like

WMI is still a thing and even Server 2019 supports it.
If you can secure and minimize the privileges of the WMI user, then it is a fairly good solution.

Check the following for help:


1 Like

Many thanks. Agentless as ive been told to by my boss (guess we have too many servers to install and manage agents on). wmi looks like it may work, will play around with it and see if i can get it working.

I would look into using director with the Icinga2 Powershell module. It’s a breeze to get the agent installed once you get going. Even kicking off the script manually only takes a minute or so.

I have about 80 servers and we’re planning on automating with SCCM.

thanks all. I managed to get wmi working with plugin by following link from George.