Risks of Stopping or Removing the Automox Agent

Using the Automox agent to schedule worklets to stop the agent service or uninstall the agent can lead to unexpected behaviors or broken devices. This article explains the risks and provides alternative methods.

Why This Matters

When the agent service is stopped or removed through the agent itself, communication with the Automox console is disrupted. This often results in:

• "Dead" agent states: The agent is unable to confirm the completion of its task due to interrupted communication.
• Queue issues: Commands to stop the service or uninstall may leave the agent in limbo, requiring intervention from Automox Support.

Recommended Methods for Stopping or Uninstalling the Agent

To avoid these risks, use one of the following approaches:

1. Group Policy Objects (GPOs)
2. PowerShell commands
3. Manually executing these actions

Troubleshooting Common Issues

1. Restarting the Agent Service:
   • If the agent is "stuck," restart it:
     • Windows: net stop amagent && net start amagent
     • Linux: sudo service amagent restart
     • macOS: sudo launchctl kickstart -k system/com.automox.agent
2. Resolving Queue Limbo:
   • If the service does not recover, contact Automox Support for assistance in clearing commands.

Conclusion

Avoid using the Automox agent to stop services or uninstall it to prevent disruptions. Instead, leverage tools like GPOs, PowerShell, or manual methods for reliable management. For further assistance, consult Automox Support.