For Onsite Manager to execute automated tasks on remote Windows devices, the following prerequisites must be met in the target device:
- The Workstation Windows Service is running.
- The Server service is running.
- The Remote Admin share (ADMIN$) is available.
- The Windows Network is running, and Printer and File Sharing are activated.
- Ports 135 and 445 must be open. By default most firewalls will block any incoming traffic to these ports.
- There is enough disk space to copy the script.
- The device is WMI-enabled.
If using PowerShell scripts:
- Some scripts require that PowerShell 2.0 or 3.0 is enabled.
- The PowerShell execution policy must allow unsigned scripts.
For Onsite Manager to execute automated tasks on remote Mac and Unix/Linux devices, the target device must meet the following requirements:
- Port 22 is open.
- Supported SSH ciphers are implemented, for example, aes128-cbc and 3des-cbc. These ciphers are implemented by default in Mac and Linux devices, but not by default in some Unix platforms, including Solaris.
- SSH is enabled.
- The interpreter for the scripts being run must be installed on the system. The scripts that run on these platforms are written in Python, which is available by default on macOS and most Linux deployments.
Script Limitations
For scripts and automation packages, the size limit for file parameters is 1 GB.
Where Automation Files are Stored
Automation files are stored on the File Storage Server, a repository for binary files used in automation:
- scripts
- script packages
- quick tasks
- resource files used by scripts
Files are uploaded to the File Storage Server automatically, with no manual intervention by the user. Communication between the File Storage Server and Barracuda RMM is handled by the File Storage Service. All of the existing scrips in the Automation Library are stored on the File Storage Server, and the following types of files are uploaded when they are created:
- New and customized scripts
- New and customized script packages
- New and customized quick tasks
- Any resource files used as parameters in scripts
These files, including the resource files, are uploaded to the File Storage Server when a new or customized script, package, or task is saved. After creating your script, allow time for any resource files to be uploaded, especially if your script or task requires many files or large files.
If Barracuda RMM stops while files are being uploaded to the File Storage Server, interrupting the upload, the upload continues when Barracuda RMM restarts.
Files are uploaded to the File Storage Server automatically and communication is handled by the File Storage Service. To find the location of the File Storage Server follow the To view the Service Center website communication settings procedure in Viewing or Changing the Communication Settings.