Name

The name of the task, up to 40 characters

Description

The description of the task, up to 50 characters.

Image

Path to the image on the client’s machine. May contain Windows environment variables such as %ProgramFiles%.

Path

For a task that installs a program (e.g., an “install task,” select the software package that contains the files that install the task). Leave blank if the task is not an install task.

Optional parameters

Some tasks require or accept optional parameters.  See the help for the various Modules to see whether or not the task requires parameters.  Such parameters, if required, are specified here.

Software Package

For a task that installs a program (e.g., an “install task,” select the software package that contains the files that install the task). Leave blank if the task is not an install task.

Install Task

Leave blank if the task is an install task. Otherwise, select the task that is used to install the program that runs this task.  The Scheduler uses this task to install the defined module for the first time, and to perform any updates (when auto-update is checked).

Auto-update

If checked, the module defined by the task will be automatically updated by the Scheduler if the version defined in by the software package selected for the task does not agree with the version that is actually currently installed.  The Scheduler checks to see if a module requires update each time before it is invoked.  For modules that are set to start and continue running indefinitely, the Scheduler checks at every "tick" interval (as defined in the setting agentSchedulerTickInterval).

Force checksum

If checked, the module defined by the task will be automatically updated by the Scheduler if the checksum of the installed file does not agree with the checksum maintained on the MIE.  Note that this is a more thorough check than Auto-update to make sure the correct version is on the client.

Run under SYSTEM

If checked, the module will be run under the SYSTEM account of the local machine on which it is installed.  Otherwise, the module will be run under the logged-in user's account.

Priority

Priority of task within the schedule. When there are multiple tasks in a schedule, the agent runs them one at a time by priority. The lower the number, the higher the priority.

How to run

Indicates how the task is to be run: Normal, Once, or Startup. Normal tasks are run periodically according to the frequency selected by the Run Every and Units controls. If Once is selected, the task is run only once. Startup tasks are run when the agent is started (typically at system startup time). Startup tasks with a zero completion time are considered background tasks that should always be running.

Run Every

Applies only to Normal tasks. Used in conjunction with the Units selection box, this value indicates how frequently the task should be run.

Units

Applies only to Normal tasks. Used in conjunction with the Run Every selection box, this value indicates how frequently the task should be run.

Jitter

Applies only to Normal tasks.  Specifies, in seconds, a maximum amount of random time to add to the Run Every setting when determining the next time to run.  This causes the running of the task to be spread out over time.  The jitter factor is multiplied by a random number between 0 and 1, and then added to the Run Every setting when determining the next time to run.

Run on Sunday

Run On Monday

....

Run On Saturday

Check each box for the day(s) that the task should run.

Run the task in a window

If selected, the task is run in a window that is visible to the user.

Report status back to MIE

If selected, the agent sends the status of running the task back to the MIE.

Deliver WDA package using APS

Run Once tasks can be delivered using Application Push Scheduler (APS) as an alternative means.  Alternate delivery only applies to Run Once tasks.  This is usually used to leverage other electronic software distribution systems to assist in performing self-remediation (where WDA can detect when it has issues and request a push / re-installation of itself.)  In such circumstances, where WDA is not operational or marginally operational, an alternative means will be required to deliver a fresh installation of WDA to the affected machine.

Package GUID

The unique identifier of the package that will be pushed by the Run Once task.  (Note that this setting may be renamed to agree with the particular software distribution tool being used.)

Program GUID

The unique identifier of the program that will be pushed by the Run Once task.  (Note that this setting may be renamed to agree with the particular software distribution tool being used.)