Task scheduler ONEVENT Schedule Frequency.

W

Wake-Up-Jeff

The vista task scheduler schtasks.exe provides the facility to take an
action when an event has been recorded in the Windows event log.

This facility is only really useful if the triggered action has access to
aspects of the event, such as date, time and event message. Is there any way
to get this information passed to the triggered action from the event log
entry?

I can't see a way, either by using the command line schtasks.exe, or the
task scheduler GUI.
 
J

Jon

Wake-Up-Jeff said:
The vista task scheduler schtasks.exe provides the facility to take an
action when an event has been recorded in the Windows event log.

This facility is only really useful if the triggered action has access to
aspects of the event, such as date, time and event message. Is there any
way to get this information passed to the triggered action from the event
log entry?

I can't see a way, either by using the command line schtasks.exe, or the
task scheduler GUI.

Don't know of way of doing that, but since you know the event id / log that
triggered it, the task that runs can process the Event Logs for the most
recent event with that particular event id.
 
W

Wake-Up-Jeff

Jon said:
Don't know of way of doing that, but since you know the event id / log
that triggered it, the task that runs can process the Event Logs for the
most recent event with that particular event id.
Agreed. But I think that is a little clumsy.
In this case, it would be better to use WMI, which at least gives you the
event detail when the event is triggered.
I would prefer to use the scheduler, as it gives a nice interface, and it
provides a really rich environment for event triggers.
 
J

Jon

Wake-Up-Jeff said:
Agreed. But I think that is a little clumsy.
In this case, it would be better to use WMI, which at least gives you the
event detail when the event is triggered.
I would prefer to use the scheduler, as it gives a nice interface, and it
provides a really rich environment for event triggers.



Not ideal, I agree. It's a pity there's not more information being passed as
argument to the task triggered by the event, although it's quite possible
that there's hidden option that's not been documented, similar to the
$(Arg0) that you can pass to a program etc. Would be interested too in
knowing it, if there is. Would be nice if someone from MS could shed some
light on the issue.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top