> Scheduled tasks > Adding Automation Policy Tasks

Adding Automation Policy Tasks

Automation Policy tasks are used to perform Automation Manager policy scripts on selected devices.

This procedure can only be performed at the SO or Customer-level.

  1. In the navigation pane, click Configuration > Security Manager > Profiles
  2. Click Add in the Scheduled Tasks screen.
  3. Select Automation Policy from the Scheduled Task Type list.
  4. Type a Task Name.
  5. Select the security Credentials of the account that will be used to perform the Automation Policy from one of the following:
    • Use LocalSystem credentials: The User Name and Password of the local system account pre-configured by the OS for system-wide access to the selected devices.
    • Use Device Credentials: The User Name and Password configured for the selected devices to which the Automation Policy will be applied.
    • Custom Credentials: An administrator User Name and Password that you can configure for use by the task.
    • Use Currently Logged On User: Use the account of the currently logged on user to perform various tasks, for example, modifying local printers and local profiles, as well as interactions with a logged-in user.

      When you select this option, N-central identifies active console and RDP users and applies the following logic:

      1. If there are console users other than RDP, users are ignored.
      2. If there is only one active user, then this user becomes the currently logged on user.

Automation Policy

  1. In the Repository Item drop-down menu, select an Automation Policy.

The Description and File Name fields display additional information about the policy.

Executing Devices

  1. Select an Executing Device:
    1. Best Available: Assigns the responsibility for selecting an Executing Device to MSP N-central. MSP N-central will select the single device that is configured with a Professional Mode license, is actively communicating with the MSP N-central server, and that best meets the specific requirements for the Policy's Remote Category.
    2. Unselected: If an Executing Device is not selected for a Customer or Site, no tasks will be created for the devices of that Customer or Site.
    3. <device name>: A specific device configured with a Professional Mode license is actively communicating with the MSP N-central server and meets the specific policy requirements.

Targets

Running Automation Policy scheduled tasks requires Agents (version 9.0 or later) and PowerShell 2.0 (or later).

  1. Click one of the following tabs to restrict the list of devices to which the file will be transferred:
    • By Filter Only
    • By Device Only
    • By Filter & Device
  2. In each tab, select a filter to be applied and a device.

Schedule

  1. Select the schedule Type:
    1. Now to have the task performed immediately.
    2. Once to have the task performed at a specified time. Select a Start Date and Start Time.
    3. Recurring to have the task performed repeatedly. Select the Start Time, Days of the Week, and Days of the Month.
  2. Type the Task Timeout value for how long (in hours) before the task will be considered to have timed out.
  3. Select the Execution Window to define if the task should be run only at the specified time or if it can be run as soon as possible if the device is offline. If the device is offline at the original scheduled time, type the number of days after the scheduled time that attempts can continue to be made to run the task.

Recurring tasks cannot be configured in an Execution Window. If a device is offline at a scheduled date and time, recurring tasks will be run at the next scheduled date and time.

Notifications

  1. Under Notify On, choose if a notification should be sent based on success or failure.

    The task will fail if the Task Timeout value is exceeded.

  2. Select Send task output file in Email to attach the output file to the email notification.
  3. Select the Recipients to receive the notification and click Save.

See Automation Manager Training Videos for a list of tutorials about Automation Manager.