What are some best practices, tools sets within the Windows 2003 server that I can utilize to monitor failed application services?

We basically have some 3party software that has a few services that it runs. I also want to be notified if the IIS server goes down as well.

I am not interested in obtaining other software for this. If I have to figure out and script in, I would rather do it that way.

Thanks for your input.

link|improve this question
feedback

migrated from superuser.com Jun 12 '11 at 4:47

This question came from our site for computer enthusiasts and power users.

2 Answers

IMHO the best way to do this given the constraints you mention is eventtriggers.exe.

You create a trigger for the event you want to monitor, which then calls a mailer script of some kind.

Look at this excellent article for more details.

and the technet article.

link|improve this answer
very interesting..will definitely take a look at this. Thanks! – user51666 Jun 11 '11 at 1:08
feedback

You can script the Windows WMI monitors, see for example

http://exchange.nagios.org/directory/Documentation/Nagios-XI-Documentation/Monitoring-Windows-With-WMI/details

link|improve this answer
feedback

Your Answer

 
or
required, but never shown

Not the answer you're looking for? Browse other questions tagged or ask your own question.