Well one way would be to schedule another task to check for a non-0 result code and possibly email you when that happens. I do not have a link for you, but I know I have done this in the past it was pretty easy, I think I just used the help to accomplish it.
-----Original Message----- From: Adam Meixler [mailto:ad...@interlink1.com] Sent: Monday, November 23, 2009 4:38 PM To: NT System Admin Issues Subject: Windows 2008 R2 Task Scheduler Hi, We're making the migration to R2 and are messing with the new 2008 task scheduler. It's loads better than what was available in 2003 but is there any way to find tasks which exit with a non-0 result code? All of the tasks seem to cause an event 201 whether successful or not. Though if the command does fail the details xml view does show a non-zero result code. How can I use this result code value in a custom event filter? Thanks!! p.s. has anyone written anything yet to flip 2003 tasks to 2008 XML tasks for import? ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
