Monitoring Windows is made possible via WMI and the available Opsview Agent. Additionally you can choose to use any version of NSClient++ to monitor your Windows servers.
You can choose from OS level monitoring down to application specific monitoring by applying any of the 'OS ' Windows' Host Templates to your Windows Host.
WMI ' The following Host Templates can be used for WMI monitoring:
- OS ' Windows Server 2008 WMI ' Base
- OS ' Windows Server 2008 WMI ' DNS
- OS ' Windows Server 2008 WMI ' Exchange
- OS ' Windows Server 2008 WMI ' IIS Server
- OS ' Windows Server 2008 WMI ' Terminal Services
*These checks will also work with Windows Server 2012
In order to monitor your systems via WMI you'll need to configure a user that has access to the appropriate WMI classes you're looking to monitor. General instructions for configuring a read-only WMI user in Windows can be found here. You can also use Active Directory or other directory managed user accounts to configure the permissions for WMI. The directions differ depending on your implementation of your directory server and your Windows Server configuration. The directions are similar to authorizing a local user, but should you encounter any issues you should check with your directory server vendor to double check configuration settings.
Windows Firewall will need to be configured to allow access if it is in use. You can do this by choosing the predefined option 'Windows Management Instrumentation (WMI)' when adding a new Inbound Rule to Windows Firewall.
Another utility that can help diagnose WMI connectivity issues is WMI Explorer. It is freely available and allows you to browse the available classes for a given user on your server. This can help narrow down permission issues and also ensure the classes you are looking to monitor are properly configured and available on your systems. It can be downloaded from https://wmie.codeplex.com/.
Windows Agent ' The following Host Templates can be used for monitoring Windows Server using the available agents:
- OS ' Windows Base
- OS ' Windows Advanced
- OS ' Windows Event Log
On the host you're looking to monitor you'll need to install the agent by downloading and running the installer. Configuration and download instructions for the Opsview Agent can be found here.
Once it is installed and running you can use any of the above host templates to run checks on your Windows Server hosts. You can also modify any of the checks or create new checks to use 'check_nrpe' to execute custom written checks on your hosts.
In the Opsview Monitor UI:
- Create a new host within "Menu => Settings => Host Settings" for your Windows Server
- Add the Host Template(s) from the list above depending on whether you're using WMI or the Agent
- Configure the host variable 'WINCREDENTIALS' and add in your WMI user's username and password to the appropriate fields
For the Opsview Agent or NSClient++:
Optional: Configure the host variable(s) 'NRPE_CERTIFICATES' and 'NRPE_CIPHERS' if you plan on using certificate based security between Opsview and the monitored host
- Submit Changes
- Perform a configuration reload within 'Menu => Settings => Reload'