New answers tagged scheduled-task
No, Scheduled Tasks in Server 2003 do not make use of the Event Log. They log to a text file, SchedLgU.txt under \Windows\Tasks\. The simplest way I've found to generate emails based on that log is with PowerShell. Select-String "\* error" should be able to find any failures in the log, and after that, it's just a matter of triggering an email when that's ...
One issue here is that if the task doesn't run because the server is hosed, any monitoring on that server will also fail. Check out https://cronitor.io. It's a simple monitoring service for scheduled jobs and sounds like it's exactly what you're looking for.
check out https://cronitor.io -- you can monitor a single cron job for free. When your jobs run, they ping Cronitor and if Cronitor doesn't get pinged at the right times it will send you an alert.
I'm coming from a web development background, so my initial instinct for part (a) is to write a separate Node program that performs all these tasks in succession. Is that all there is to it, or is there a better way? Nothing wrong with that. You schedule it with cron to run it on the desired scheduled.
Top 50 recent answers are included