Automation Manager automation automation policies automation checklist
Automation Manager enables you to eliminate repetitive tasks across your customer base by creating repeatable processes using a visual "drag and drop" scripting interface.
When you open Automation Manager, it checks for updates. If detected, Automation Manager upgrades itself to the newer version. For example, you uploaded or installed Automation Manager v1.0 yesterday and we release v2.0 today. The next time you open Automation Manager, it upgrades itself from v1.0 to v2.0.
- When creating a policy with a large number of objects, the Automation Manager Designer will be slow to respond. N-able suggests that you split these larger policies into smaller ones and combine them using Run Policy objects.
- Policy files larger than 10MB cannot be uploaded through the Automation Manager Designer. Policy files larger than 20MB cannot be uploaded through N-able N-central.
- If you try to run two policies containing SSH objects at the same time, then unexpected errors can occur. For example, the first policy can send commands in the SSH session created by the second policy. These errors occur because a class which handles the SSH connection is static.
If you have a number of tasks that you need to perform on a regular basis, you roll up these tasks into a "policy" (an Automation Manager Policy, or AMP) using Automation Manager, set up the schedule for this policy in N-able N-central, and then report back the details and status to your customers.
Automation Manager Policies support backward compatibility. This means that newly created or updated policies can run on older agents, so long as the policy doesn't use objects that are newer than what is supported on the agent. Within the Automation Manager Designer's help section for each object, the version required to support this object will be shown, and your policy will display the lowest version required to run your complete policy as you add and remove objects.
You can also use custom properties with Automation Manager policies that pulls in the appropriate customer or device-specific information, rather than creating separate Automation Manager policies per customer, or per device. Automation policies can also set the property for devices. For example, a policy can run based on a property of "Maintenance required". After completion of the task, the automation policy can change the property to "Maintenance completed. Automation policies cannot update customer-level properties.
Automation Manager requires PowerShell 3.0 to run AMP-based services.
Automation Manager allows you to configure any messages that are sent to the user with your company logo, fonts, and colors.
Assembling an Automation Manager Policy draws on the Automation Objects (a set of actions or tasks) library from the following categories:
The following are the supported operating systems for Automation Manager:
|Workstation Operating Systems||Server Operating Systems|
What do you want to do?
- Install Automation Manager
- Create a new Automation Manager policy
- Modify an existing Automation Manager policy
- Debug an Automation Manager policy
- Delete an Automation Manager policy file in Software Repository
- Uninstall Automation Manager from a computer
- Review the Default Automation Manager policies within N-able N-central
- Use Input Parameters and Global Variables in an Automation Manager policy
- Use Output Parameters in an Automation Manager policy
- Create Custom Services Based on Automation Manager policies
- Run Automation Policies with Office 365 Automation Objects
- Run Peer-to-Peer Automation Manager policies