What this updates
This workflow installs IronAgents's own agent software. It does not install OS patches, reboot computers, run arbitrary scripts or restart selected monitored services. Monitoring briefly restarts if it was running. A deliberately stopped collector stays stopped.
Real application-requested updates succeeded on both tested Ubuntu environments, the tested Mac and Windows 11 device, with original device identities and confirming check-ins preserved. Helper startup after reboot and broader failure/uninstall acceptance remain separate checks. The packages remain development releases with signing limitations.
One-time local setup
Use the current platform download page or local update control to install Linux/macOS 0.10.0 or Windows 0.12.0 or later. These are minimum helper versions, not the latest release numbers. The current download page is authoritative.
This installs a separate privileged updater: root on Ubuntu/macOS, SYSTEM on Windows. The ordinary collector retains its restricted account. After enrollment, allow about a minute for the updater to contact the configured application. An older installation offers Enable website updates… with local setup guidance.
The helper accepts only authenticated IronAgents release requests from its protected configured server. It opens no inbound port. A checksum and verified HTTPS do not replace publisher code signing.
Request and confirm
- As an owner or operator, open Fleet or Agent health and choose Update agent… for the intended device.
- Review the device and proposed update, then confirm the request. There is no bulk update or automatic update-on-release policy.
- Open machine details for request history, requester, timestamps and result. Viewers can inspect progress but cannot request or cancel updates.
- Verify Succeeded and the new agent version. Reopen the desktop companion if needed to load its updated interface.
| State | Meaning and next action |
|---|---|
| Queued | Waiting up to 24 hours for the helper. Can be canceled before collection. |
| Installing | The helper collected the request and is running the verified installer. Portal cancellation is unavailable. |
| Waiting for check-in | The helper reported installation. The requested version must still check in. |
| Succeeded | A check-in confirmed the requested version after the request began. |
| Failed, Expired or Canceled | Read the explanation and inspect local state before requesting again. |
Installation/acknowledgment has a fifteen-minute deadline; a reported installation gets ten minutes for its confirming check-in. A deliberately stopped collector cannot provide that confirmation until you start it locally. A timeout is not proof that no files changed.
Local controls
Stopping monitoring does not stop the helper's separate polling. Disabling website updates leaves local CLI/menu update controls available and persists across upgrades. Uninstall removes the helper. Disable/uninstall is refused while an update is actively running.
Ubuntu, with administrator permission:
sudo fleet-monitor-agent disable-remote-updates
Use enable-remote-updates to enable it again. Inspect the scheduler with systemctl status fleet-monitor-updater.timer and its logs with sudo journalctl -u fleet-monitor-updater.service -n 50 --no-pager.
macOS:
sudo '/Library/Application Support/FleetMonitor/current/fleet-monitor-agent' disable-remote-updates
Use enable-remote-updates in place of the disable action to enable it. sudo launchctl print system/com.fleetmonitor.updater reads the helper's scheduler state. Do not confuse it with the collector or per-user menu bar login item.
Windows, in an Administrator PowerShell terminal, locate the installed release and disable the helper:
$fleetRoot = Join-Path $env:ProgramFiles 'Fleet Monitor'
$fleetVersion = (Get-Content (Join-Path $fleetRoot 'current.json') | ConvertFrom-Json).version
$fleetAgent = Join-Path $fleetRoot "releases\$fleetVersion\fleet-monitor-agent.exe"
& $fleetAgent disable-remote-updates
Use & $fleetAgent enable-remote-updates to enable it again. Inspect FleetMonitorAgentUpdate in Task Scheduler and its Last Run Result. The optional read-only OS update scanner is a different task and capability.
When a request cannot finish
Check helper connectivity, the request explanation and the platform's local logs. Retain the device's identity. If its application origin moved, follow the administrator-confirmed download page's local repair flow; an unreachable old server cannot deliver the update. See address-change troubleshooting.