Overview

Remote Monitoring and Management (RMM) allows Managed Service Providers (MSPs) to remotely deploy, monitor, and manage software across customer devices.

The Evo Security RMM integration with Datto RMM allows administrators to deploy, upgrade, and uninstall the Evo Agent directly from the Evo Portal while leveraging Datto RMM to execute deployments across managed endpoints

Prerequisites

Before configuring the integration, ensure you have:

Administrator access to both the Evo Portal and Datto RMM.

An existing Datto RMM environment.

An API Key and API Secret generated within Datto RMM.

Appropriate permissions within Evo Security to manage RMM integrations and deployments.

Generating Datto RMM API Credentials

To allow Evo Security to communicate with Datto RMM, you'll first need to generate API credentials.

Within the Datto RMM Portal:

Setup → User → Your Integration User Account

Under the API section:

Click Generate API Keys.

Record the following values:

API Key

API Secret

These credentials will be used when configuring the Evo Security integration.

Configuring the RMM Integration

Within the Evo Portal, navigate to:

Evo Admin → Integrations → RMM

Select Configure, then click New.

Complete the configuration:

Setting	Value
Provider	Datto RMM
Base URI	The URL generated by Datto RMM
API Key	Your generated API Key
API Secret	Your generated API Secret

Test Connection before saving.

Click Save.

Once saved, the Datto RMM integration is ready to use.

Creating a Mapping

Mappings associate an Evo tenant with a Datto RMM organization or site.

Navigate to:

Integrations → RMM → Mappings

Click New.

Configure the following:

Tenant

Directory (optional)

RMM Integration

Scope (Datto Organization or Site)

Save the mapping.

Mappings allow Evo Security to determine which deployment token should be used and which Datto-managed devices are available for deployment.

Note: Mappings associate an organization with its Evo tenant and directory (when configured). This information is used during deployments to automatically identify the correct tenant and directory, allowing Evo to generate and configure deployment tokens whenever possible.

Creating Deployment Components

Datto RMM uses Components to execute software deployments.

Before deployments can be performed, create an Evo installation component.

Within Datto RMM navigate to:

Automation → Components

Select Create Component.

Configure the component:

Setting	Value
Name	Install Evo Agent [WIN] or Install Evo Agent [MAC]
Description	Optional
Script Type	PowerShell (Windows) or Shell (macOS)

Paste the Evo installation script into the script editor.

Note: Our Deployment Scripts can be found HERE under Assets

Component Variables

Windows Components ( Pictured Above )

Create the following variables:

Variable	Type	Default
EVO_DEPLOYMENT_TOKEN	String	None
EVO_REMOVE_NOW	Boolean	False
EVO_UPGRADE_NOW	Boolean	False
EVO_LOG_OUTPUT	Boolean	False

macOS Components

Create the following variables:

Variable	Type	Default
EVO_DEPLOYMENT_TOKEN	String	None
EVO_UPGRADE_NOW	Boolean	False
EVO_REMOVE_NOW	Boolean	False

Save the component once all variables have been configured.

Note: When creating Deployment Components, include [WIN] for Windows components or [MAC] for macOS components in the component name. These tags are used to identify the target operating system and ensure the correct component is deployed. For consistency, keep the variable order the same between the Windows and macOS components whenever possible. The only exception is EVO_LOG_OUTPUT, which may appear in a different position as required.

Deploying the Evo Agent

Navigate to:

Desired Tenant → Endpoints → RMM Deployments

Click New.

Configure the deployment:

Select the Tenant

Select Provider → Datto RMM

Select the appropriate Scope

Optionally choose a Deployment Token

Select the target devices

Choose the Windows and/or macOS installation component

If devices already have the Evo Agent installed, you can choose whether to:

Use existing settings during upgrade

Apply the selected deployment settings

Click Save.

The deployment will be queued and begin automatically.

Deployment progress can be monitored from the RMM Deployments page, including individual device execution status.

Managing Deployments

From the Deployments page, administrators can:

View deployment progress

Review per-device deployment results

Monitor completed deployments

If a deployment has not yet started and is not in a terminal state, it can be cancelled directly from the deployment details.

Device Discovery

Device Discovery associates Datto-managed endpoints with existing Evo Computers.

Discovery begins automatically after a mapping has been created.

Automatic discovery runs every 4 hours.

Administrators can also perform a manual discovery.

To manually start a discovery:

Navigate to Integrations → RMM

Edit the Datto RMM integration

Under Discovery History, click the Search (Magnifying Glass) icon

Refreshing the Discovery History will display the progress and results of the discovery.

Note: Manual discovery is limited to 3 executions per hour.

Computers

After the Evo Agent has been successfully deployed:

Devices will appear under Endpoints → Computers

Successfully matched endpoints will be identified as RMM Managed

Note: When deleting an RMM-managed computer from Evo Security, the system first attempts to uninstall the Evo Agent before removing the endpoint record.

Deployment History Retention

Deployment history is retained according to the configured deployment retention policy.

Default: 90 days

Supported values:

Minimum: 30 days

Maximum: 365 days

Deployment history is automatically cleaned up on a daily basis.

Permissions

The following permissions control access to RMM functionality:

Permission	Description
Manage RMM Integrations	Allows users to configure and manage Datto RMM integrations.
Manage RMM Deployments	Allows users to create, manage, and monitor RMM deployments.

Evo Support Bot

RMM Integration - Datto RMM