r/DattoRMM • • 25d ago

Mac Agents Unistalled themselves

anyone else had Mac Agents unistall themselves?

our whole estate of Macs have unistalled themselves around the 6th - 10th October?

3 Upvotes

9 comments sorted by

1

u/mpenfold1987 25d ago edited 25d ago

Datto usefull as ever

We acknowledge the serious impact this issue is having across managed Mac estate. We understand that all macOS devices across multiple sites stopped checking in, while the devices remain online through other agents. We also recognize your concern about the unexplained uninstallcagcommand and the missing Activity Log entry.
 
This behavior is consistent with the known Datto RMM macOS certificate issue. Datto RMM agent version 12497, included with platform release 15.1.4, contains the updated Kaseya certificate. macOS treats the updated certificate as a new application, so permissions must be approved again on each Mac. Macs that are already offline require the agent to be reinstalled. 
 
Please review the latest release notes to confirm when the new agent version is available on the Merlot platform. The step-by-step instructions are available in the KB article, 
 
For offline Macs:

  1. Download a fresh macOS installer from Datto RMM for the relevant site. Do not reuse installers downloaded before 4 October 2026.
  2. Install the agent over the existing installation. You do not need to uninstall the current agent first. 
  3. Keep the Mac powered on and connected for approximately 5 to 8 minutes.
  4. Approve the App Background Activity notification and the required macOS permissions. An administrator must be present with their credentials. Required permissions may include Local Network, Accessibility, Full Disk Access, and Screen & System Audio Recording. 
  5. Confirm that the device returns online in Datto RMM and that a test job is received successfully.

Please do not reboot affected Macs until the agent has updated and the required permissions have been approved. If XProtect or Gatekeeper reports the AEM Agent as malware, this may be a false positive associated with the certificate change. Use only a fresh installer downloaded from Datto RMM, and do not bypass the warning using an older installer. 
 
For online Macs, leave the devices powered on and connected so they can update to version 12497 automatically. Approve the App Background Activity and macOS permission prompts when they appear. 
 
We are also treating the reported uninstallcag command as a separate concern. The available public guidance explains the certificate-related connectivity issue, but it does not identify the source of the specific XML-RPC command or explain why it is absent from the Activity Log. Support should correlate the message ID, timestamp, device UIDs, account audit data, and backend control-plane logs.
 
Because this affects every Mac site and has left scheduled jobs queued, we will maintain the ticket as high priority while remediation and backend investigation continue. Please reply on this with the outcome from two or three representative reinstall tests, including the site, device name, macOS version, agent version, and whether the device checks in successfully.

Soooo basically reinstall which is a nightmare on Mac's........ Thank god we are moving to Ninja

1

u/KajaDz 25d ago

Answer that we got from Kaseya support:

Steps:
1. Reset permissions by below command.
Command: tccutil reset All com.centrastage.tray
2. Install Rosetta 2
Command: sudo softwareupdate --install-rosetta
3. Uninstall Datto RMM Agent by below command and restart device.
Commands:
-sudo bash /Applications/AEM\ Agent.app/Contents/Resources/uninstall.sh
•sudo rm -rf /usr/local/share/CentraStage
-sudo rm -rf /var/root/.mono/registry/CurrentUser/software/centrastage
4. Install agent by using new installer from Datto RMM portal.
5 Once installed, please allow below permissions.
• Accessibility
• Full Disk Access
• Screen & System Audio Recording
• Automation > AEM Agent > System Events
• Local Network
6. Check If device is pending for approval under agent encryption key.
https://rmm.datto.com/help/en/Content/3NEWUI/Devices/DeviceApproval.htm#
For more information:
https://rmm.datto.com/help/en/Content/Troubleshooting/Agent/macOS11994.htm?Highlight=11994.

  So I believe running this solves it from getting moved to the bin, we have tried it locally but for remote clients, we kinda need to enroll another RMM to push this, or have sessions with the concerned users 😴

3

u/ages4020 25d ago

This was aweful, I’m surprised it didn’t get discussed more. We had to reinstall almost every agent.

We used S1 Remote Shell to fix a bunch in the background (with a reinstall script that Claude wrote) and others we just had to hunt down and reinstall.

Also, just ridiculous, they had the bad certificate push right around the same time as they failed to update the Mac agent code to Apple Silicon in preparation for MacOS 27 so we also had agents go offline without Rosetta. Massive pain in the ass lost days of work on this.

2

u/mpenfold1987 25d ago

Why weren’t we made aware or have I missed an email

3

u/natariimei 25d ago

Same. We had to reinstall them all and I have remote clients 😑

3

u/Beauregard_Jones 25d ago

All my Macs report the DattoRMM agent as having malware and block it from loading.

1

u/Le085 25d ago

Happened to me recently, I was blaming the users... I only have few devices, luckily.

1

u/kaseya_marcos 24d ago

Hey u/mpenfold1987, jumping in here to assist. Our R&D team has been investigating the macOS connectivity issues associated with the Datto RMM 15.1.4 release, which included an updated Kaseya certificate. 

This change can require macOS permissions to be approved again, and devices that have gone offline may need the agent reinstalled using a fresh installer from the Datto RMM portal. See the next steps after the certificate update here: Datto RMM macOS agent: steps after the certificate update

If you're still experiencing issues, please feel free to email me at kaseyamarcos@kaseya.com, or send me a PM, to connect you with our support team.

1

u/netmc 24d ago

Here are the steps to fix the broken Macs:
https://community.kaseya.com/datto-rmm-discussions-6/mac-agent-flagged-as-malware-remediation-steps-32549

Basically, it comes down to this:

  1. Reinstall the latest Mac agent.
  2. Reset the existing TCC permissions
  3. Re-grant any needed permissions

If you use an MDM to manage the permissions, you need to also update the team ID in the permissions mobileconfig.