Scheduled tasks help

About the Schedule task dialog box

Access this dialog box from the Scheduled tasks window (Tools > Distribution > Scheduled tasks). In the Scheduled tasks window, click the Create software distribution task toolbar button, or from the shortcut menu of the task you want to configure, click Properties.

Use this dialog box to set the start time for the task and to psecify whether to make it a recurring task and how often. This dialog box also shows the task targets. Depending on the task type you're scheduling, you may also see options for delivery methods and distribution packages.

About task copying

You can also create groups for your common tasks to categorize them. Other users will see groups only if their RBA scope allows them to see a task in that group. If you try deleting a group that contains tasks, you won't be able to delete the group if there are tasks in the group that your scope doesn't allow you to see.

About the Overview page

This page lets you pick an owner for the task and summarizes the choices you've made in the Scheduled tasks dialog box. If you want to modify any of your choices, click Change beside that choice. If you want the task to appear in the Scheduled tasks window's Common tasks group, rather than the My tasks group, click Show in common tasks.

About the Distribution package page

Use this page to select the distribution package you want to deliver. Once you select a Package type, the Distribution package list shows the packages of that type that you can distribute. The packages in the list correspond to the packages you can see under that type in the Distribution packages window for the current user and the public user. Click the Distribution package you want.

Push-based software distribution tasks can include a preliminary package and a final package. When using multiple packages, the packages are installed in order one at a time. The previous package must return a successful task status before the next package begins installing. For more information, see Using multiple distribution packages in a task.

About the Delivery method page

Use this page to select the delivery method to use for the package you're delivering. Once you select a Delivery type, the Delivery methods list shows the delivery methods of that type that you can use. The delivery methods in the list correspond to the delivery methods you can see in the Delivery methods window for the current user and the public user. Select the Delivery method you want.

About the Target devices page

Use this page to view target devices for the task you're configuring. You can't add targets on this page. You can add targets later by dragging and dropping them into the task in the Scheduled tasks window. Targeted devices can be in these categories:

You can also select the Wake up devices option on this page. This option wakes up a powered-down computer for the selected task by using Wake On LAN. When the task is complete, the computer shuts itself down again. This feature only works on computers with BIOS versions that support Wake on LAN technology. Selecting this option will make tasks take longer, since the task waits for devices that just woke up to boot. Don't mark this option for pull distribution packages.

About the Schedule task page

Use this page to configure when the task runs and how retries should work:

When rescheduling a task, you can limit the devices the task runs on. You may want to do this if the task failed on a large number of devices and you don't expect the failed device state to change, for example. Limiting the task this way would help the task complete more quickly because the scheduler wouldn't keep trying devices that won't process the task. You can choose to run tasks on devices in these states:

About the Schedule dialog box

Several Management Suite agents have features that you can schedule using the local scheduler agent that is installed on managed devices. Use this dialog box to configure that schedule.

You can also use the local scheduler to schedule your own tasks to run periodically on devices. Once you create a local scheduler script or customize the schedule for a device agent, you can deploy it to devices by using the Scheduled tasks window.

To configure a local scheduler task, in the Managed scripts window (Tools > Distribution > Managed scripts), from the My scripts shortcut menu, click New local scheduler configuration script.

All criteria in this dialog box that you configure must be met before the task will execute. For example, if you configure a schedule that repeats every day between 8 and 9 o'clock with a Machine state of Desktop must be locked, the task will only execute if it's between 8 and 9 o'clock and the device is locked.

These options are available in the Schedule dialog box:

Events section

The events section is dimmed unless you're configuring a local scheduler script from the Manage scripts tool.

Time section

Use this section to configure times for the task to run. If you launched this dialog box from the agent configuration tool, you can specify a random delay on the agent configuration page you came from. The random delay interval you specify is a time range during which the task may run. For example, if you have a large number of users who log in at the same time, this delay allows tasks that run on login to not all run at the same time, assuming your delay interval is long enough. The default delay is one hour.

Run filters section

When configuring local scheduler commands, you can specify the minimum bandwidth criteria necessary for the task to execute. The bandwidth test consists of network traffic to the device you specify. When the time comes for the task to execute, each device running the local scheduler task will send a small amount of ICMP network traffic to the device you specify and evaluate the transfer performance. If the test target device isn't available, the task won't execute. 

When specifying bandwidth criteria for devices that may be connecting to the core through a LANDesk Management Gateway, you should put the Management Gateway's IP address in the to field. This allows the bandwidth test to complete and the task can then execute.

You can select these Minimum bandwidth options:

The run filters section has these options:

Other options