Toolkit: Use event triggers to monitor Windows servers


  • Provided by TechRepublic Premium
  • Published July 16, 2014
  • Topic TechRepublic Premium
  • Format PDF
Event triggers are a handy and free way to alert IT staff of potential Windows server problems. There’s a saying in IT that your users should be the last ones to notice when a critical system or service is down. Smart technological management has emphasized for many years the importance of being proactive rather than reactive, but it’s not always easy to quantify just what “proactive” means. Do you need to physically inspect servers or network hardware for signs of impending failure? Look at CPU and memory usage on an hourly basis? Comb through endless event or error log entries trying to predict what will happen tonight, tomorrow, next week or next year? Obviously none of these are realistic concepts in the 24x7x365 world of IT administration.

System monitoring tools such as Nagios and Zabbix are available to watch over your network and servers, and log gathering utilities such as Splunk make it easier to wade through log files in one centralized location. Both of these kinds of tools can be highly customized, can provide short and long term trending data, and can send out alerts. However, Windows servers (as of Windows 2008) provide a simple and easy method to monitor event logs. This is set up through the Task Scheduler, which provides a powerful interface to run commands when specific events are recorded.

Find out how to set these up with Tech Pro Research's custom event triggers toolkit to allow you to start monitoring your environment. Included in the toolkit is a pdf explaining how to use the included customized .XML file which contains many pre-formatted critical events for Active Directory and Exchange environments.

People Also Downloaded