Arma supports the following Operating Systems -
Windows Server (2012, 2016, 2019, and 2022)
Windows Workstation (7, 8, 10, and 11)
Mac Carolina and Ventura
Linux (Ubuntu, Redhat, Debian, Fedora, Alma, Rocky, and Mint)
Microsoft M365 Tenancy
Protected Item Installation
Go to Clients -> Protected Items and select '+New Device'.
Select device operating system and preferred installation method (64-bit installer or command line).
Windows Devices
Selecting "Download Agent" will download a generic, client-independent, 64-bit MSI installer that can be run locally on the device.
This needs to be run manually on the device and once installed you will need to connect the device to the correct client in the Arma cloud service by running the locally installed Arma Backup Connect application.
Please Note if your account has 2FA enabled you will be prompted to enter your 2FA code.
Command line and scripted install
Copy the command line install and run in the device's command console, or use an installation script.
Please note:
• Each command line installation string is unique for each client.
• The installation command must be run as an Admin user.
Server 2012/2016 command line install - requires Curl
If you are running Windows Server 2012 or Server 2016 the application “Curl” needs to be installed on the device to allow the installer to download the agent. Click here for more info and download. This will then allow the Curl commands to be run from a console.
Windows 7 (64bit only) command line install - requires Curl
If you are running Windows 7 (64-bit) "Curl” needs to be installed on the device to allow the installer to download the agent. Click here for more details. Please note - you must run the command line install in the Curl\Bin folder on the Windows 7 device.
Mac devices
This downloads a generic, client-independent, 64-bit installer that can be run locally on the device. Once installed you will need to connect the device to the correct client in the Arma cloud service. If running Naverisk you can also deploy via Curl script on the console. Please note you must enable full disk access in settings before creating any profiles. This is a manual process and must be done otherwise Arma will not be able to see the files or folders.
Linux devices
This downloads a generic, client-independent, 64-bit installer that can be run locally on the device. Once installed you will need to connect the device to the correct client in the Arma cloud service.
On Ubuntu Devices all dependencies will be auto-installed. For other Linux distros please see below
If using any of the following you will need to install "MONO" manually. Mono is a prerequisite for the Arma Agent
Redhat, Fedora, Alama, Rocky https://www.mono-project.com/docs/getting-started/install/linux/
For Mint please see this article https://linuxhint.com/install-mono-linux-mint/
Each Repo may have a different way of deploying MONO. You may also need to apply the following setting to allow the mono repositories to load. Run from terminal “update-crypto-policies --set LEGACY”
Once MONO is installed, then from a Terminal run the Curl command to deploy Arma.
M365 Tenancies
In order to set up a new M365 Tenant, make sure that the Client's M365 S3 Storage is first set up and connected successfully (when you proceed to Clients -> Storage)
Go to Clients -> Protected Items and select '+New M365 Tenant'.
This will pop up a dialogue where the Tenant Name, Directory- and Application Id together with the Application Secret should be entered.
Device troubleshooting
Arma agent ports
Arma device agents connect to the Arma cloud and storage services via two outbound ports.
Outbound ports
443
57781
Ensure these ports are open for outbound connectivity on firewalls and anti virus products.
Arma device services
Arma runs two services on protected devices. Ensure these services are in a running state.
Arma Service Monitor: Monitors the Arma Sync service and restarts this if offline.
Arma Sync Service: Runs backups and restores on the device.
Device showing offline in Arma
If your device has been re-installed or is showing as offline, try restarting the Arma services on the device.
Manually upgrade Arma agent to latest version
The Arma agent checks for updates every 24 hours. To force an Arma agent to update to the latest version, click the Agent Restart button. This will restart the agent on the device and install the latest agent version.