Skip to main content

Install Datto RMM Agent [VSA 9 Migration]

Summary​

Installs the Datto RMM agent on Windows, Linux, and macOS devices managed by VSA 9. Each device joins the Datto RMM site stored in cPVALDattoRmmSiteUid. The installer is downloaded from the address stored in cPVALDattoRmmAgentUrl.

Devices that already have the Datto RMM agent are left unchanged. The result for each device is saved in cPVALDattoRmmDeployStatus.

note

Schedule this agent procedure against all machines that move to Datto RMM. Run the Sync Datto RMM Sites [VSA 9 Migration] agent procedure first, so that the custom fields are filled in.

warning

Endpoint security can block or remove the Datto RMM agent. Before running this procedure at scale, add the Datto RMM agent to the allow list of your antivirus or EDR product. See Datto RMM allow list requirements.

Dependencies​

Implementation​

  1. Export the agent procedure from ProVal's VSA RMM instance.
    Name: Install Datto RMM Agent [VSA 9 Migration]

    The export will download the necessary XML file.

  2. Import this XML file into the partner's VSA RMM instance.

  3. Run the agent procedure against one or two test devices. Confirm that each device appears in the expected Datto RMM site.

  4. Schedule the agent procedure against the remaining devices.

Sample Run​

Image1

Variables​

This agent procedure has no variables. It reads its settings from the cPVALDattoRmmSiteUid and cPVALDattoRmmAgentUrl custom fields.

Results by Device​

DeviceResultcPVALDattoRmmDeployStatus
Datto RMM agent already installedNo changes.Completed - Datto RMM agent already present
Agent installed and detectedInstalled.Completed - Datto RMM agent installed
Agent not detected after the installFailure.Failed - Datto RMM agent not detected after install
No Datto RMM site UID storedFailure. No changes.Failed - cPVALDattoRmmSiteUid is empty
No download address storedFailure. No changes.Failed - cPVALDattoRmmAgentUrl is empty
note

The procedure waits 30 seconds on Windows and macOS, and 120 seconds on Linux, before it checks for the agent. A slow device can report Failed and still finish the install later. Run the procedure again on that device; it reports Completed once the agent is present.

How the Agent Is Detected​

PlatformDetected by
WindowsRegistry value HKEY_LOCAL_MACHINE\SOFTWARE\CentraStage\DeviceID
LinuxFile /opt/CentraStage/uninstall.sh
macOSFile /Applications/AEM Agent.app/Contents/Resources/uninstall.sh
note

Linux devices need wget and sudo. macOS devices need curl. Both are present on most systems by default.

Output​

  • Agent Procedure Log
  • cPVALDattoRmmDeployStatus custom field on each device

Changelog​

2026-10-16​

  • Initial version of the document.