We have a new monitoring tool : Zenoss
Some notes :
Somewhat unclear overview
VERY bad documentation
Not particularily user-friendly
Conclusion : if I did not have to, I would not use it
Zenoss and IIS
It is not easy to set up IIS monitoring, and there is NO good explanation in (sparse) documentation.
It is necessary to install a Windows Management Framework for WIN Server 2003 (it has a Windows PowerShell 2.0, WinRM 2.0, BITS 4.0 in it).
You have to set up one user under AD, for monitoring purposes, for all WIN servers, and it has to be a member of a local Administrators group.
WinRM Service has to be enabled :
Allow automatic configuration of listeners -> Enabled -> Under IPv4 filters input “*” without the quotation marks
Allow Basic authentication -> Enabled
Allow unencrypted traffic -> Enabled
Windows Remote Shell has to be enabled :
Allow Remote Shell Access -> Enabled
Specify maximum number of processes per Shell -> Enabled -> MaxProcessesPerShell = 2147483647
Specify maximum number of shells per user -> Enabled -> MaxShellsPerUser = 2147483647
Specify shell Timeout -> Enabled -> ShellTimeOut = 2147483647
For IIS to be “seen” in Zenoss, „IIS Management Scripts and Tools“ has to be installed :
Select Start > Administrative Tools > Server Manager
Server Manager appears. Select Web Server (IIS) under Roles, and click Add Role Services
And of course WinRM, WinRS, and AD user from above…..
When adding a new server, it MUST go under pod Device Class : /Server/Microsoft/Windows (or nothing will work as it should!)
Pod Configuration Properties configure the following :
zWinRMUser, zWinRMPassword, zWinKDC (it is a IP address or the name for your AD server)
Add modules that are needed, and supported by WinRM (under Modeler Plugins)
When all configuration and changes are done, do the “Model Device” and study the output carefully!
After this, under “Monitoring Templates” a Template for IIS should show up.