Don't monitor Windows services following a server reboot

The NT_ServiceDown Knowledge Script can generate a number of ‘false’ service down alerts following a server reboot. This occurs if the Job executes before the server has completed rebooting and monitored services have yet to start. In order to address this behaviour I have modified the KS to include two additional parameters under General Settings:

·         Don’t monitor services following reboot?

o   Minimum uptime before commencing monitoring

If the first parameter is enabled then the KS gets the value of the System Uptime performance counter and compares it to the threshold in minutes defined in the second parameter. If it’s below the threshold it causes the KS to exit gracefully without monitoring any services. Once server uptime exceeds the threshold, service monitoring commences as normal.

Note: this modification has been made to version 7.6.276 of the KS.

NetIQ does not test or validate any software, code or other materials provided in, on or through NetIQ Cool Solutions (collectively, "Materials"), so please use caution when downloading or accessing any Materials from Cool Solutions and ensure that you have reasonable and current security, spyware and anti-virus measures in place on your computer and/or network prior to downloading. Additionally, do not use any Materials downloaded from Cool Solutions in any production environment without first testing the Materials to ensure they are compatible with your version of NetIQ software or any other hardware or software present in your network or environment. Cool Solutions is not a substitute for authorized NetIQ support and should not be used as such. NETIQ COOL SOLUTIONS AND ANY MATERIALS ARE PROVIDED ON AN AS-IS, AS-AVAILABLE BASIS WITHOUT ANY WARRANTY OF ANY KIND. By downloading this file, you are agreeing to these terms of use. To report a problem please contact: Your use of Cool Solutions is governed by the Cool Solutions Terms and Conditions.


How To-Best Practice
Comment List