Automation Manager

Rather than spend time on time-consuming, repetitive manual tasks, you can automate those tasks on Windows computers using Automation Manager so you can spend more time working on more pressing issues.

With Automation Manager, you can use default scripts, or create custom scripts, and apply them as Script Checks or Automated Tasks.

Even if you do not have scripting or programming experience, you can use the Automation Manager (previously known as the Script Builder and based on technology licensed from N-able). Its intuitive interface enables you to easily create and test your own custom policies (a collection of tasks) before deploying them on Windows computers.

View the N-able MSP Institute training course N-sight RMM Feature Focus - Automation Manager.

The Automation Manager is only required on the script author's computer. It is not needed on every endpoint running the .amp scripts. Once deployed, these scripts use a component bundled in the Windows Monitoring Agent from 10.3.4.

To create an Automation Manager policy, drag and drop the target objects (scripting components) onto the Policy Builder in their run order. This includes any conditionals (If or For Each objects).

Once in place, link and configure the objects (including the policy's Input Parameters). Test the policy to ensure there are no problems. Upload the generated .amp file to the Dashboard for deployment as a Script Check or Automated Task.

The Automation Manager includes over 600 pre-built objects grouped under functional headings. Event Log includes Create Event and Get Events; Control Flow has For Each and If / Else.

Automation Manager policies are based on PowerShell. In addition to the default objects, you can also add your own PowerShell script using the Run PowerShell Script object. This ensures the created script exactly matches your requirements.

No coding experience is necessary to use the Automation Manager. However, you may need domain knowledge, an understanding of Windows as well as a familiarity with its terms, concepts and technologies depending on the selected objects.

System Requirements

Devices running Automation Manager and devices running Automation Policies (scripts) require the following:

Windows Operating System

Type OS Version
Workstations Microsoft Windows 7 (32/64-bit) or later
Servers Microsoft Windows Server 2008 (32/64-bit) or later

Software

Software Version / Info
.NET Framework version 4.6 or later
PowerShell version 5.1 or later
N-sight RMM or N-able N-central Windows Agent only required on devices where the created Automation Policies will be run or tested

Automation Policy Requirements

As well as the above requirements, devices where the Automation Policy will be run must also meet the following requirements, dependent on the Automation Policy functionality.

Automation Policy Includes Device Installed Software Requirement
SSH object(s) Operating System = Professional or Enterprise license at minimum
Telnet object(s)
Wake on LAN object(s)

Office 365 object(s)

Operating System = Professional license at minimum

Microsoft Online Services Sign-In Assistant

Microsoft Online Services for Windows PowerShell or Windows Azure Active Directory Module for Windows PowerShell

Windows only: as Automation Manager creates PowerShell they are not compatible with Linux or Mac Operating Systems.

Dashboard Permissions

The Automation Manager and Script Manager are only available when logged into the Dashboard as a user with the Custom Scripts permissions enabled.

The Automation Manager may be slow to respond when creating a policy with a large number of objects. We suggest splitting these larger policies into smaller ones then use the Run Policy object in Extensions to combine them.

Unexpected errors can occur if you attempt to run two policies containing SSH objects at the same time. For example, the first policy sends commands in the SSH session created by the second policy. These errors occur because a class which handles the SSH connection is static.

What do you want to do?