Ok, I have time now to pick up my 2 suggestions.
The first idea I have involved a product I have used for 3 years now, IPMonitor. You can find out info on it at www.ipmonitor.com
It is a monitoring program that monitors Windows servers very well. You can monitor just about anything you would want to using IPMonitor. HTTP, FTP, file space, Active Directory, SMTP, etc. So many things!
Anyway, one thing you can do is monitor a remote server's Event Viewer logs for specific Event IDs. If the event occurs on the target machine, IPMonitor will detect it, and it can trigger an alert. NET SEND popups, e-mails, log file creation, and other things can be triggered by IPMonitor detecting an event.
You can also even Restart a server if a specific event is detected. And I think this is the best way for you. I run this on a couple of my most important servers. If a monitored item fails on them, I have IPMonitor e-mail me, and then restart the servers.
Anyway, IPMonitor has a built-in restart server capability. Nothing els is needed. Just set up what to look for, and the alert thresholds, and to have it restart the remote server if the alert threshold is reached.
IPMonitor has a 30 day full functional trial period. So, you can download it and try it.