Devices and agents

The Enlist agents

What the Windows and Mac agents are, where they live, how they talk to Enlist, how they stay safe, and how to remove them.

Each onboarded computer runs the Enlist agent. It connects out to Enlist, runs the work Enlist sends it, and reports back what it did and what the computer has.

Windows agent #

Runs on
Windows 10 22H2 and Windows 11, Pro or Enterprise, x64 or ARM64 (the versions Enlist is tested on)
Service
EnlistAgent ("Enlist Agent")
Installed in
C:\Program Files\Enlist\Agent, with its state in C:\ProgramData\Enlist\Agent
Tray app
enlist-tray.exe, which shows messages and questions to the signed-in person
Remove it
Uninstall Enlist Agent from Settings → Apps, or uninstall the MSI from your RMM

Mac agent #

Runs on
macOS 14 and later, Apple silicon and Intel (one package)
Runs as
The LaunchDaemon app.enlistit.agent
Installed in
/Library/Application Support/Enlist/bin/enlist-agent, with logs in /Library/Logs/Enlist
Needs
Full Disk Access (see Onboard a Mac)
Remove it
sudo "/Library/Application Support/Enlist/bin/enlist-agent" uninstall

How agents talk to Enlist #

  • Outbound only, on port 443. No ports open on the computer or the client's firewall.
  • A certificate per device. Each agent proves who it is with its own certificate (mutual TLS), which renews itself in its last 30 days. A device's page has Renew certificate for when you need it now.
  • Always connected. The agent keeps one connection open and reconnects on its own, waiting a little longer each time (up to 5 minutes) if Enlist can't be reached. It sends its inventory every 15 minutes.

Signed work #

An agent runs only work that is signed. Every command is signed by Enlist's servers. Every blueprint version also carries the passkey approval of whoever published it, and every Terminal run the passkey of the technician who ran it, which the agent checks itself against the passkeys your devices trust. Agent updates are code-signed (Developer ID on a Mac) and also signed with a release key kept offline, and the agent refuses an update that isn't.

Updates #

Enlist updates agents for you, in waves: a small group first, then more, then everyone. If too many devices fail an update, the rollout stops on its own and your notification channels hear about it (security.agent_update_halted). Devices → Agent updates shows where each update is and how many of your devices failed it (see Devices).

What the agent reports #

Hardware, OS version, installed software, patches needed and installed, disk encryption, and on a Mac whether Full Disk Access and Find My are on. The device's page in Devices shows it all. See Working with devices.

Last updated 2026-11-18. Something wrong or missing? Email [email protected].