Overview 💥
Liongard has identified an issue affecting macOS Agents running version 4.2.4 where the built-in auto-update mechanism fails to upgrade the agent to newer versions.
This issue has been fully resolved in later agent releases (4.2.5 and newer). However, any agent currently stuck on 4.2.4 must be manually repaired or upgraded once to restore normal auto-update behavior going forward.
Liongard provides multiple supported recovery paths, depending on scale and severity.
Why This Happen 🤔
Mac Agents on version 4.2.4 contain a defect in the auto-update workflow that prevents:
Successful update checks
Downloading the newer installer
Executing the updater correctly
As a result:
The agent may continue checking in
Auto-update may show as Enabled
The agent never advances beyond 4.2.4
This condition does not self-correct and requires manual intervention.
‼️ Impact
Affected agents may experience:
Being permanently stuck on version 4.2.4
Missing important stability and security fixes
Inconsistent inspection behavior over time
Auto-update enabled but ineffective
Once repaired, future auto-updates work as expected.
Recommended Resolution (Primary Fix) 🧑🏫
Use the Official Liongard Mac Agent Updater Script
This is the recommended and supported first-line fix, especially for bulk remediation.
Steps:
Download the updater script:
👉 https://resources.static.liongard.com/scripts/LiongardAgentUpdate.shDeploy the Script
Manual execution via Terminal
MDM / RMM (Jamf, Addigy, Kandji, Intune, etc.)
✅ Option A: Manual Execution (Terminal)
Copy the script contents into a file named:
LiongardAgentUpdate.sh
Make the script executable:
chmod 755 LiongardAgentUpdate.sh
Run the script with elevated privileges:
sudo sh LiongardAgentUpdate.sh
📌 The script must be run as root / with sudo.
✅ Option B: MDM / RMM Deployment
Paste the script contents directly into your MDM’s script module
Ensure the script runs:
As root
Without user interaction
No parameters or environment variables are required
(Example shown below using Addigy)
What the Script Does:
Behind the scenes, the updater script will:
Download the appropriate Liongard macOS agent package
Repair existing agent components in place
Install the updated agent over the existing installation
Restart Liongard services automatically
No agent re-registration is required.
Verification Steps:
After the script completes successfully:
Log in to the Liongard Portal
Navigate to:
Admin → Agents
Locate the affected macOS agent
Confirm:
Agent version is newer than 4.2.4 (for example 4.2.6 or later)
Last Heartbeat is current
Auto-Update Status is enabled
Example verification shown below:
Additional Troubleshooting & Alternate Recovery Options 👨💻
If the updater script cannot be used, or if further troubleshooting is required, use one of the supported options below.
1 – Manually Trigger the Built-In Updater
(Recommended for testing or a small number of devices)
On the affected Mac, run:
sudo /Library/Liongard/LiongardAgentUpdater
This command immediately:
Checks Liongard for the latest macOS agent
Downloads and validates the installer (if available)
Installs the update in place
Restarts Liongard services as needed
Verification:
After completion:
Log into Liongard
Navigate to Admin → Agents
Confirm the agent version has updated and the heartbeat is current
2 – Uninstall and Reinstall the Latest macOS Agent
(Use when auto-update or updater repair paths fail)
This approach fully bypasses the auto-update mechanism and guarantees the device is on the current version.
Recommended when:
The agent is stuck on an older version
Auto-update attempts fail repeatedly
The device is on a known problematic build
Steps:
Download the latest macOS agent installer:
Admin → Agents → Install Agent
Uninstall the existing Liongard macOS agent from the device
Install the latest
.pkgusing:Manual install, or
RMM / MDM deployment (Jamf, Intune, Kandji, etc.)
Confirm the agent reappears in Liongard and checks in normally
📌 Reinstallation automatically restores a clean, supported state.
Important Notes & Best Practices 🙌
🔁 This is a one-time fix per affected machine
✅ Once upgraded, future auto-updates function normally
🛠 The updater script is safe to run on existing installs
❌ Simply waiting will not resolve agents stuck on 4.2.4
When to Contact Support 🤩
Please contact Liongard Support if:
The updater script fails
The manual updater does not advance the version
The agent does not check in after reinstall
Collect:
Script output
Logs from
1./Library/Liongard/logs/
2./tmp/liongard-agent-installer.logmacOS version and architecture