When

At Jobs > Scheduling, when configuring the settings of a Job, use the When section on the Properties tab to specify when the Job should be executed.

Configuration

to execute a Job immediately

to postpone the execution of the Job for any offline Agents

• Use case: The Job on online Agents will be executed immediately, but creates a separate After next boot Job for any offline Agents on which the Job is scheduled. When one of the offline Agents gets online, the After next boot Job will be executed and remains active until all specified Agents have completed the Job. If you clear this option, the Job will fail on all offline Agents, depending on the Launch timeout settings (in the Console, at Setup > Global Settings).

to schedule Jobs on Agents running on Windows laptops

• Use case: When a laptop goes into hibernation, sleep or standby, its Agent goes offline and it will become part of the After next boot Job. However, when the laptop is resumed and the Agent comes back online again, the After next boot Job on this Agent will not be executed, because the laptop has not booted. As many users rarely turn off their laptop, but put it in hibernation, sleep or standby instead, this can cause a backlog in Jobs that need to be executed on these Agents. If you select both options, Jobs scheduled on Agents running on laptops will also be executed.
• Not supported on Unix, Linux and Mac OS X machines. When selected, the non-Windows Agent(s) will execute the Job only after a reboot of the machine.

to execute the Job on a specific date and time

• Select the start date and time.
• Use case: The Job is scheduled for example at night or during the weekend when network traffic is at its lowest.

to execute the Job recurringly at a specific interval

• Select the repeat pace (every, weekly or monthly) and interval and the start time (immediately or on a specific date).
• Use case: This can be useful for recurring maintenance Tasks like defragmentation or disk space queries. When you select Effective Immediately, the schedule will be reset to the moment of editing. This means that the Job will again be executed immediately, after which it is executed recurringly at the specified interval.

to execute the Job after the next boot of the specified Agents

to execute the Job after every boot of the specified Agents

• Select this option and schedule the Job to a Team, and this will be a dynamic schedule.
• Use case: If the Team is enabled, the Job will automatically run on all Agents added to that Team before or after the Job has been scheduled.

to execute the Job after new Agents get online

Additional options

Use the following additional options:

Clear this option to (temporarily) put the Job On Hold. The Job will not be executed until the Scheduled option is selected again.

Use this option to specify what should happen to the Job when it is scheduled outside the launch window. Select the time period during which Agents are allowed to execute Jobs. The availability of the option If outside launch window depends on the permissions of your administrative role. The options are:

• Fail the Job: fail the Job when it is scheduled outside the launch window of the Agent.
• Override window and continue: schedule the Job irrespective of the launch window of the Agent. This option is only available if the administrative role of the administrator permits the use of this functionality.
• Wait for next window: postpone the Job until the next launch window when it is scheduled outside the launch window of the Agent. If the global setting Launch timeout is set to less than one week, a warning will be shown that this combination may cause the Job to fail on Agents with infrequent launch windows.

Use this option to configure a timeout for the Job. In Run Books, if a Run Book Job is not completed within the specified timeout, it will change the status of any active Agent to Timed out. Subsequent Run Book Jobs will continue as normal. The end result of the Run Book will be Completed with errors.

• Use case: This is useful to prevent situations in which Jobs cannot be completed because an Agent that executes a Task goes offline during execution, for example because it is being serviced or rebooted. Because this Task will remain active, the Job will not finish. By configuring a maximum Job duration, you can prevent these situations: the Job will be canceled when it times out.

Use this option to boot Agents automatically when the Job starts (available for Immediate, Scheduled and Recurring Jobs only). This broadcasts a "wake-up" packet to the Agent and forces it to use UTC time. By default, Ivanti Automation uses a global broadcast address, 255.255.255.255 and UDP port 3163 for Wake-on-LAN. If necessary, you can set up different Wake-on-LAN settings (in the Console, at Setup > Global Settings). This option cannot be used in combination with option Schedule offline Agents for next boot.

Use this option to specify whether to use local time of the Agent or UTC time of the Datastore (available for Scheduled and Recurring Jobs only).

• Use case: The option UTC time is useful in large environments, where the Datastore is located in a different time zone than the Agent.