Install the desktop agent on macOS
To manage one Mac, generate its customer-specific PKG in your workspace, install it with administrator permission, then verify later telemetry. Agent installation and Apple MDM enrollment are separate tasks.
Before you start
You need an OWNER or ADMIN workspace account, an existing customer, and permission to install software on the Mac. Obtain the current approved artifact and signing/notarization procedure from your platform operator. If macOS blocks the package, follow your organization's software approval process or contact support.
Install one Mac
- Open Generate an installer on Dashboard, or open
/installerson your workspace host. - Under Generate installer & enrollment token, select the correct Client, optional Location, macOS Operating system and PKG distribution.
- Optionally enter a Label, then choose Generate. Choose Download RevolutionaryRMM-Agent.pkg and open the package on the authorized Mac.
- Complete the administrator-authorized installation using the approved trust procedure. Extra distribution choices in the form do not prove that a separate DMG or MDM package was generated.
- Open Monitoring > Devices, clear filters and find the Mac under the selected customer. Open Overwatch and check CPU/memory and a later performance sample. Refresh after another check-in and confirm last seen advances.
The agent normally checks in every 60 seconds. Enrollment sets last seen before a metric arrives, so an Online badge or Enrolled attempt alone does not prove monitoring is working.
Set permissions for the task you need
Remote control needs Screen Recording and Accessibility, plus a native-capable artifact and a verified session. Full Disk Access is relevant to protected-file scanning. Separately MDM-enrolled Macs can receive an agent PPPC profile, but Screen Recording still needs local approval. A successful installation or heartbeat does not prove remote capture, input or protected-file scanning.
Generated enrollment tokens are reusable for 30 days. Keep tokens, links and copied commands private. Revoke stops new enrollment with that token and does not uninstall the service. Duplicate short hostnames within one customer are refused with 409 hostname_already_enrolled. Preserve saved agent configuration on reinstall; if it is lost, retire the stale record through an authorized administrator or use a distinct short hostname before retrying.
If installation or reporting fails
Check workspace URL, token validity, outbound HTTPS, service state and the redacted installer error. Use Onboarding troubleshooting for the failing stage. See Desktop agent for update trust and removal, MDM / EMM for mobile management, or Getting started for workspace setup.
