Today I have seen on the documentation page of Nagios a new tutorial that talks about deploying a NSClient++ to your servers with the help of SCCM 2007.
The document covers all the steps of the deployment from the creation of the .msi package to the deployment verification of the package. All the stages are covered with screen captures. This type of deployment offers multiple advantages like selecting the hours of the installation or how much bandwidth should be used and makes updating the software package a breeze and I recommend it over other ways to install the client.
This is a sketch article in which I want to do a brief description of how to install a Windows WMI proxy and do the checks via WMI in your windows network.
The WMI Proxy is basically a Windows Server / Workstation that has NRPE_NT or NSClient++ (you need to change a bit the configurations) installed and from which with an administrative user can do checks to the windows network via the WMI.
WMI is also used as a check for some other products including but not limited to: SCCM, SCOM, Spiceworks, etc.
In this article I wish to mark some advantages / disadvantages of having a WMI proxy in your Nagios setup.
To WMI or not to WMI….
First we need to explain what exactly a WMI proxy is. Basically this machine is a Linux/Windows machine with a Nagios client installed that runs as a service. This WMI proxy has some scripts (I will detail them in my next post) capable to check other Windows servers with the help of the WMI repository located on each Windows server. The same technique is applied with success by SCCM, SCOM, SpiceWorks, etc.