Automox vs. Open Source Puppet

We mainly use Automox for patch management and endpoint management. This makes it easier for our IT team to manage endpoints from the dashboard and saves us time and manual effort. It works well for us; we need to keep Windows PCs and servers up to date and automate regular security and software updates across multiple devices.

Incentivized

• Shows applications installed on a specific asset
• Able to push policies and updates remotely , creating policies is easy.
• Keep track of compliant devices and when is the last time they have connected to the servers
• All the great information provided within one single device

Incentivized

• There are some applications that updates to the wrong version causing Channel version issues, this then needs to be excluded from the policy and updated via a script.
• Certain software like NET. is not updated
• The worklet / remediation / evaluation system is not always effective, does not work all the time. Needs to be very detailed for it work.

Incentivized

This is a software that just works. Once configured its a set and forget kind of tool that keeps things up to date and alerts me if something is wrong. I was able to work through an expansion project to deploy an additional 500 devices in almost no time and create a robust self-patching environment.

Incentivized

I love the console interface; it makes taking action very simple compared to some other software I've used. There's a wealth of information at your fingertips on a user's endpoint page in Automox, and it's usually the only tool I need when troubleshooting, unless something more specific is going on.

Incentivized

I did not need to reach out to support often but when I did the answers were relatively correct and they were answered quickly. The only thing I might "ding" their support on was their lack of understanding of OS's different from Windows and especially Linux. Other than that I was satisfied

Incentivized

Implementing Automox successfully starts with a clear strategy for organizing and grouping devices based on operating systems, environments, or business criticality. This ensures that patching and configuration policies can be applied with precision. A phased rollout approach is essential—beginning with a pilot group allows teams to test patching schedules, reboot behaviors, and custom Worklets before scaling across the organization. Leveraging Worklets from the start can significantly boost automation by enforcing security baselines and performing routine system tasks. Integration with existing SOC tools, such as SIEMs, enhances visibility and response time by correlating patch compliance with threat intelligence. Additionally, aligning patching schedules with operational downtimes minimizes disruptions, and consistent monitoring and reporting helps maintain compliance and prepare for audits. Overall, Automox offers a streamlined and effective solution, but its true value is unlocked through thoughtful planning, testing, and integration with existing IT and security workflows.

Incentivized

Specifically for patch management, Automox is one of the most user friendly options available. The ability to customize packages and target specific machines makes it a very useful tool. It's definitely a stand out software out of the options available

Incentivized

• We wanted to like the remote support software, but the experience was poor compared to a solution like BeyondTrust.
• Development and deployment of worklets is fast for experienced coders.
• Policy execution and reporting is fast and reliable.
• The new analytics dashboard excels at reporting Mean Time to Remediation for executive reporting purposes.

Incentivized