Automox review.
June 18, 2023

Automox review.

Tyler Woodworth | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User

Overall Satisfaction with Automox

We use Automox to support the automatic patching of operating systems and 3rd party applications. Automox can also help with the implementation of new software via workouts or even the removal of applications where management of the device is unavailable. The scheduling and patch policy enforcement is critical for our business to ensure endpoints are secure as soon as possible, especially in today's ever-changing security climate.
  • 1st and 3rd party patching (and growing list of 3rd party apps).
  • Multiple policies to ensure different levels of criticality are addressed.
  • End user notifications.
  • Reporting and compliance are more streamlined and easier to read.
  • Allow patches to be seeded across endpoints enrolled (local LAN distribution of patches).
  • More options for end-user notification, what exactly would be patched, and more choices for installation and reboot times.
  • Expansion into mobile devices.
  • Positive impact for assurance of patch compliance.
  • Positive impact for visibility into vulnerability management.
  • Positive impact for zero on-prem services to setup and maintain to meet patching needs.
Biggest experience change was the end users being presented with different alerts/warnings to update their endpoint. Enrollment of Automox was automated through Microsoft Intune Autopilot to auto-enroll all endpoints as they are deployed to ensure compliance and patch thresholds.
The interface can feel clumsy at times or missing better reporting functionality.
Better 3rd party patching and reporting.

Do you think Automox delivers good value for the price?

Yes

Are you happy with Automox's feature set?

Yes

Did Automox live up to sales and marketing promises?

Yes

Did implementation of Automox go as expected?

Yes

Would you buy Automox again?

Yes

Automox is best suited where connectivity is close to 100% with Cloud access. Where there are disconnected endpoints or clients that have limited bandwidth, it is less appropriate. If you are looking to seed patches down to a location and have endpoints updated from that, is is also less appropriate as first or third-party patching solutions would need to be added on.