Automation Manager and Designer requirements

Last Modified

Wed May 09 16:48 GMT 2018

Description

• This article provides the requirements and dependencies of Automation Manager.

Environment

• N-able N-central

Solution

• The Start Automation Manager link does not appear:
• Automation Designer can only be launched by ProductAdmin or SO Admin users.
• To launch the designer, .NET4, Powershell 2.0 is required.
• NOTE: For higher versions of N-able N-central - .Net 4.2 or higher and Powershell 3.0 are required.

• Automation Manager - Dependencies:
  • N-able N-central agent version 9.0,
    • Policies cannot be configured to execute against devices unless they have an N-able N-central 9.0 agent,
    • Agent Version should match that of N-able N-central server to avoid conflicts with newer AMP versions,
  • .NET4 Required by the Automation Manager Designer,
    • If not installed, the user will be prompted to install .NET4 on initial launch,
      Required by the Automation DLL on the agent side,
    • Upon installing/upgrading a 9.0 agent, the agent will attempt to install .NET4 using the dotnetfx4 package, as is done with RSM,
  • PowerShell 2.0,
    • In later versions of N-able N-central the PowerShell requirements may be higher,
    • Required on the designer side to execute policies. If the designer is launched and the local system does not have PowerShell version 2.0 a window is presented to the user with a link to the Microsoft KB article (968929),
    • Required on the agent side by the Automation DLL. If a policy is configured to be executed against an N-able N-central 9.0 agent that does not have PowerShell 2.0 installed, the error output in the scheduled task results pane in N-able N-central will contain a link to the online help with instructions on how to deploy/install PowerShell 2.0,
    • Deployment instructions are available in the `Am I Ready for Automation Manager' document in the online help,