Skip to content

Scheduling

Many objects in the CapaInstaller Console, such as packages, jobs, Replicator tasks, groups, and profiles, have a schedule that controls when they run. The Scheduling dialog has the same tabs for all of them: Start, Interval, and Recurrence. Some objects show extra options, such as a Wake On LAN request or a synchronization priority.

  1. Right-click the object, and then select Schedule.
  2. Select or clear the Enabled checkbox to activate or deactivate the schedule.
  3. Set the start, interval, and recurrence on the tabs, as described below.
  4. Click OK.

If you save a schedule that isn’t enabled, you’re asked whether the schedule should be enabled.

On the Start tab:

  1. Select the date and time when the schedule takes effect. For a new schedule, the start defaults to the current date and time.
  2. Choose when the schedule ends:
    • No end date: the schedule never expires. This is the default.
    • End by: the schedule expires on the date and time you select.

Execution times can be restricted by configuring an interval. The interval is the period of time each day in which the schedule is active.

On the Interval tab:

  1. Enter a Start time and an End time for the period each day in which the scheduled object is allowed to run.
  2. Optionally, enter a Duration instead of an end time. The values adjust automatically to the correct interval.

The interval is based on 24 hours, so the period can run past midnight.

Recurrences define when executions of the scheduled object occur.

On the Recurrence tab, select how the schedule runs:

  • Once: the schedule runs once. This is typical for the installation of a software package.
  • Periodical: the schedule runs periodically. Select Hourly, Daily, Weekly, or Monthly, and set how often:
    • Hourly: recur every number of hours.
    • Daily: recur every number of days, or every weekday.
    • Weekly: recur every number of weeks on the weekdays you select.
    • Monthly: select the months, and the days or weekdays of the month.
  • Always: the schedule runs every time an agent run is triggered. This is typically used to keep critical inventory information updated.

Optionally, select End after and enter the number of occurrences after which the execution stops.

The default recurrence depends on the type of object you schedule.