In Part One, we discussed the new User Interface, Triggers and Task Conditions. Today we’re going to discuss Flexible Actions and Triggers, Security and Reliability. So, let’s get started … For flexible actions and triggers, prior to Windows Vista and Windows Server 2008, a task was launched based on a single trigger and that job could only include one action. One of the most common scenarios we encounter is a task that launches a script that launches another script and so on – and somewhere inside all of these nested and linked scripts, a failure occurs. With the new changes, this scenario is mitigated. Multiple triggers can now be attached to any given task. For example, a given error condition might be indicated only if three different events occur. An administrator can easily define a task that will launch only if all three of these events occur.
|