Agent is Not Auto-Updating
If a device is not updating to the latest Automox agent version, there are several potential reasons. This guide explains the common causes and provides steps to resolve the issue.
Possible Causes
-
Staggered Rollout:
- Updates are rolled out gradually; not all devices receive updates simultaneously. Devices will attempt updates during their routine check-ins.
-
Blocked Working Directory:
- The update process uses C:\Windows\Temp on Windows as the working directory, which may be blocked on systems with strict security controls.
-
Disabled Auto-Update:
- Your organization may have requested Automox Support to disable auto-updates via the Agent Update Policy.
-
Firewall Restrictions:
- Firewalls may block access to the Automox repository. Ensure allowlisting rules are configured correctly.
Troubleshooting Steps
Step 1: Verify Working Directory Permissions
- Ensure C:\Windows\Temp is accessible. If blocked, allowlist this directory for all devices. See full instructions here.
Step 2: Confirm Update Policy Settings
- Verify whether auto-updates have been disabled for your organization. Contact your IT administrator or Automox Support for confirmation.
Step 3: Check Firewall Rules
- Ensure that your firewall does not block the Automox repository. For required configurations, refer to the Agent Firewall Allowlisting Rules.
Steps to Resolve
If the issue persists:
- Restart the agent service:
Windows:
net stop amagent
net start amagent
Linux:
sudo service amagent restart
macOS:
sudo launchctl kickstart -k system/com.automox.agent
- Review local agent logs for errors related to updates.
- Log file location: [Provide file paths per OS].
- Submit a support ticket:
- Include the device name, ID, and relevant log files.