![]() ![]() If you specify the custom event trigger settings, you can specify an XML event query or custom event filter to query for events that will fire the task. You choose which log contains the event, the publisher name, and the event ID. Basic settings fire based on a single event from a specific event log. You can choose either a basic event trigger or custom event settings. On an Event-This trigger causes a task to run when specific events are created in an event log. On Idle-The settings for tasks set to run when the computer is idle are set on the Conditions tab. This type of trigger runs whenever the system starts and the only settings are the advanced ones, which are described later in the chapter. At Startup-There are no specific settings for tasks configured to run at startup. ![]() At Log On-Tasks scheduled to run when At Log On is set for any user or for a specific user or group of users. For reoccurring tasks, the start time can be configured along with reoccurring options to completely customize when the task will run. On a Schedule-Triggers for a schedule allow tasks to run on a specific date (one time), Daily, Weekly, or Monthly. The following describes the various trigger types and the settings that can be configured for each type. With more than one trigger, the task will launch when any of the conditions in any of the triggers is met. As noted earlier, each task can contain multiple triggers. Triggers can be based on time, events, or various system states. Understanding Trigger Options and Settings The first thing to consider when configuring a task is what triggers will cause the task to execute. ![]() The upcoming sections explain the options when creating tasks. They include general settings, triggers, actions, conditions, and additional settings. When creating a task, there are five tabs of options that must be configured. Tasks are created by selecting Create Basic Task, Create Task, or Import Task from the Actions pane in the Task Scheduler snap-in. The new user interface is displayed in Figure 33.15.įIGURE 33.15 The Task Scheduler user interface. With Windows Server 2008 R2, Task Scheduler has been moved from Control Panel to Administrative Tools. By improving on the Task Scheduler’s functionality, it has become a very powerful and extensive development and activation tool for automating and assisting with troubleshooting tasks. Task conditions eliminate ambiguous situations by providing criteria-based functions. When a task is triggered, it will only run if specific defined conditions are met. An additional functionality is task conditions. When a task is running multiple actions, up to 32 can be performed. Examples of actions include starting a program or sending an email. An action represents the work being performed as the task is being executed. Multiple triggers can be associated with a task as defined by an administrator. Tasks are initiated by triggers that are based on an event or time. Understanding Task Scheduler Scheduling tasks involves triggers and actions. This is a great feature because administrators can be automatically notified when a specific event transpires. As such, a task can be triggered based on an event captured in the event log. One of the most compelling new features of the Task Scheduler is that it fully integrates with Event Viewer. Windows Server 2008 R2 improves upon the previous version of the Scheduled Task tools included in Windows Server 2003 by allowing scheduled jobs to run more securely and with greater predictability. These things together assist administrators in the areas of logging and debugging. curring tasks into a central location, administrators gain insight into system functionality and control over their Windows Server 2008 R2 infrastructure through automation. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |