AppDeploy

Deploy, update, and uninstall applications across your endpoints silently and at scale.

Overview

AppDeploy is Xcellerate RMM's built-in application deployment engine. It lets you push software packages to one, many, or all endpoints with a few clicks — silently, without disrupting the end user. AppDeploy supports MSI, EXE, DMG, DEB, and RPM package formats.

The module includes a curated package library with 200+ popular applications (browsers, runtimes, utilities) that are kept up to date by RMM Labs. You can also upload your own custom packages.

The AppDeploy package library with search and category filters

Key concepts

  • Package — an installer file plus metadata (name, version, silent-install flags, pre/post scripts).
  • Package library — a built-in catalogue of pre-configured packages maintained by RMM Labs.
  • Deployment task — an instruction to install, update, or uninstall a specific package on a set of endpoints or groups.
  • Deployment policy — a recurring rule that ensures a package is always installed (and at a minimum version) on members of a group.

Step-by-step walkthrough

1

Choose a package

Go to AppDeploy → Library. Search or browse for the application you want to deploy. Click it to view available versions and silent-install parameters.

2

Select targets

Click Deploy. Choose individual endpoints, one or more groups, or use a filter to build a dynamic target set. You can preview the list before proceeding.

3

Configure options

Set the deployment action: Install, Update, or Uninstall. Optionally set a schedule (e.g. deploy tonight at 22:00) and choose whether to restart the endpoint after installation.

4

Launch and monitor

Click Start deployment. The task appears in the Deployment history tab. You can see real-time status per endpoint: pending, downloading, installing, succeeded, or failed.

A deployment task in progress showing per-endpoint status

Uploading a custom package

Go to AppDeploy → Custom packages → Upload. Drag your installer file, fill in the name, version, and silent-install command line (e.g. /S for NSIS, /quiet for MSI), and click Save. The package is now available for deployment like any library package.

# Example silent-install flags
MSI:   msiexec /i package.msi /qn /norestart
NSIS:  setup.exe /S
InnoSetup: setup.exe /VERYSILENT /NORESTART

Tips & best practices

  • Use deployment policies for critical software (antivirus, VPN clients) — they auto-remediate if the app is uninstalled.
  • Test custom packages on a single device before deploying to a group.
  • Schedule large deployments outside business hours to minimise user disruption and network congestion.
  • Check the failed tab after every deployment and address errors promptly — common causes are insufficient disk space or conflicting installs.
Custom packages are stored on the server. Ensure you have enough disk space for large installers. Consider cleaning up old versions periodically.