Creating or Modifying Scheduled Automation Policies

Automation policies may use any Notification Server schedule, such as a shared schedule or a specified custom schedule. Maintenance windows (which are defined on the managed computers) cannot be used to schedule automation policies. When an automation policy is triggered, the appropriate actions are run immediately. You cannot schedule an automation policy to run at a later time after it has been triggered.
This topic covers the default options that are supplied with Notification Server. Solutions may extend these options or add new ones. For more information, refer to the appropriate solution documentation.
  1. To create or modify a scheduled automation policy
  2. In the Symantec Management Console, in the
    Manage
    menu, click
    Automation Policies
    .
  3. On the
    Automation Policies
    page, on the
    Schedules
    tab, do one of the following:
    To create a new policy
    1. Click
      New Policy
      .
    2. In the
      Automation Policy Name
      dialog, type the new policy name, and then click
      OK
      .
    To modify an existing policy
    In the left pane, select the appropriate policy.
  4. (Optional) In the right pane, edit the policy name and description by clicking the appropriate fields and typing the new details.
  5. In the
    Schedule
    drop-down list, select the schedule that you want to use.
    At Date/Time
    Specify the schedule date, time, and repetition in the appropriate fields.
    Shared Schedule
    In the
    Select Shared Schedule
    drop-down list, select the appropriate schedule.
  6. In the
    Details
    panel, under
    Data Source
    , specify the data source to use.
  7. Under
    Conditions
    , in the
    Evaluation Rule
    drop-down list, select the appropriate evaluation rule:
    Run for non-empty data
    Treats the data source table as a single unit. When the policy is triggered, the action is run only if the table contains one or more rows, and is run once only.
    You need to use this option if the data source contains information in an HTML file rather than a table.
    This option lets you target everything in a single column, such as a list of GUIDs. You cannot set dynamic parameters to distinguish targeted computers. If you want to do that, you must use the Run for each record option.
    Run for each record
    Evaluates the data source table row by row, which lets you use fields per row as dynamic parameters for the specified actions. The action is run once for each row.
    Run always
    Runs the specified actions without using a data source.
    This option is available only when no data source is specified.
  8. Under
    Actions
    , specify the task or job to run, and set any required input parameters.
  9. Click
    Apply
    to save the policy settings.
  10. (Optional) If you want to ensure that all of the policy components are consistent and that the input parameters are mapped properly, click
    Test Automation Policy
    .
    The test is an internal check only and does not affect any resources.