Defining Settings
The Settings tab displays additional global settings for the task and allows you to define these settings. All settings on this page are optional. If you do not specify these settings, designated default values will be applied to the task.
To configure global settings using the Settings tab, click the Settings tab and configure the desired settings as described in Table below.
Global Settings Defined on the Settings Tab
Setting | Description |
Allow Task To Be Run On Demand | Defines whether the task supports Run Now functionality that allows tasks to be run on demand from the user interface or
command-line utilities. Default value: Selected |
Run Task As Soon As Possible After A Scheduled Start Is Missed | Configures the task to run immediately if the service detects that a scheduled activation was missed; for example, the computer was
turned off when the trigger condition occurred. Default value: Cleared |
If The Task Is Already Running, Then The Following Rule Applies | Configures the action to be taken if the trigger for a task fires while an instance of that task is already running. Options include
Do Not Start A New Instance, Stop The Existing Instance, Run A New Instance In Parallel, and Queue A New Instance. Default value: Do Not Start A New Instance |
If The Task Fails | Use this setting to restart a task if the task fails to run. (The last run result of the task was not a success.) The user specifies the
time interval that takes place between task restart attempts and the number of times to try to restart the task. Default value: Cleared |
Restart Every | Enabled only by selecting the If The Task Fails option. Specifies how often a retry should be attempted. Options in the list include Indefinitely, 1 Minute, 5 Minutes, 10 Minutes, 15 Minutes, 30 Minutes, and 1 Hour. Default value: 1 Minute You can also enter other values using the following formats: <ss> s[econds] <mm>[:<ss>] m[inutes] <hh>[:<mm>:<ss>] h[ours] |
Attempt To Restart Up To | Enabled only if you select the If The Task Fails option. Specifies the number of times to restart the task upon failure. |
Stop The Task If It Runs Longer Than | Configures the task to stop if it has been running for longer than the specified time. Default value: Selected |
<Execution Time Limit> | Enabled only if you select the Stop The Task If It Runs Longer Than check box. Configures the task to be stopped after the specified
amount of time specified by Execution Time Limit. Options include 1 Hour, 2 Hours, 4 Hours, 8 Hours, 12 Hours, 1 Day, and 3 Days. Default value: 3 Days You can also enter other values using the following formats: <ss> s[econds] <mm>[:<ss>] m[inutes] <hh>[:<mm>:<ss>] h[ours] |
If The Running Task Does Not End When Requested, Force It To Stop | If this setting is selected, the task will be forced to stop if the task does not respond to a request to stop. Default value: Selected |
If The Task Is Not Scheduled To Run Again, Delete It | Configures the task to be deleted if it is not scheduled to run again. Default value: Cleared |
After | Enabled only if you select the Delete Task option. Specifies the amount of time to wait, after the task completes its last run,
before deleting it. Options include Immediately, 30 Days, 90 Days, 180 Days, or 365 Days. Default value: 30 Days You can also enter other values using the following formats: <ss> s[econds] <mm>[:<ss>] m[inutes] <dd> d[ays] <mm> months |
In this tutorial:
- Windows 7 Desktop Maintenance
- Performance Monitoring
- Improvements to Performance Monitoring in Windows 7
- Using Performance Monitor
- Real-Time Performance Monitoring
- Performance Monitor Logging
- Creating a Data Collector Set
- Configuring a Data Collector Set
- Using Data Manager to View Performance Data
- Starting and Stopping Data Logging
- Viewing Performance Data
- Comparing Performance Monitor Logs
- Performance Monitor User Rights
- Remote Data Collection
- Using Windows PowerShell for Performance Monitoring
- Resource Monitor
- Overview Tab
- CPU Tab
- Memory Tab
- Disk Tab
- Network Tab
- Reliability Monitor
- How Reliability Monitor Works
- Windows Performance Tools Kit
- Event Monitoring
- Understanding the Windows Event Architecture
- Channels
- Improvements to Event Monitoring in Windows 7
- Using Event Viewer
- Understanding Views
- Viewing Event Logs
- Saving Event Logs
- Configuring Event Subscriptions
- Considerations for Workgroup Environments
- Creating a New Subscription
- Using the Windows Events Command-Line Utility for Event Monitoring
- Using Windows PowerShell for Event Monitoring
- Using Task Scheduler
- Improvements to Task Scheduler in Windows 7
- Understanding Tasks
- Understanding the Task Scheduler Architecture
- Understanding Task Scheduler Security
- Credentials Management
- Securing Running Tasks
- Understanding AT and Task Scheduler v1.0 Compatibility Modes
- Understanding the Task Scheduler Snap-in
- Understanding Default Tasks
- Creating Tasks
- Defining Triggers
- At Startup Trigger
- On Connection To AND Disconnect From User Session Triggers
- On Workstation Lock AND Unlock Triggers
- Defining Actions
- Defining Conditions
- Defining Settings
- Managing Tasks
- Viewing History
- Using SchTasks.exe for Creating and Managing Tasks
- Task Scheduler Events
- Troubleshooting Task Scheduler
- Tasks Won't Run If the Service Is Not Started
- The Task Will Run Only When a Certain User Is Logged On
- The Task Action Failed to Execute
- Interpreting Result and Return Codes
- Understanding the Windows System Assessment Tool
- Understanding WinSAT Assessment Tests
- Examining the WinSAT Features Assessment
- Running WinSAT from the Command Line
- Understanding WinSAT Command Exit Values
- Running WinSAT Using Performance Information and Tools
- System Capabilities Section
- OEM Upsell And Help Section
- Understanding Windows Error Reporting
- Overview of Windows Error Reporting
- How WER Works
- Store Management System
- ReportArchive Folder
- WER Service
- Understanding the Error Reporting Cycle
- Understanding WER Data
- Configuring WER Using Group Policy
- Configuring WER Using the Action Center