Automox is an endpoint management solution from the company of the same name in Boulder. Cloud-based and globally available, Automox enforces OS & third-party patch management, security configurations, and custom scripting across Windows, Mac, and Linux from a single console. With it, IT and SecOps can gain control and share visibility of on-prem, remote and virtual endpoints without the need to deploy costly infrastructure. Automox aims to reduce corporate risk while raising operational…
$1
per month per endpoint
Microsoft Intune
Score 8.3 out of 10
N/A
Microsoft Intune (formerly Microsoft Endpoint Manager), combining the capabilities of the former Microsoft System Center Configuration Manager, SCCM or ConfigMgr, is presented as a unified endpoint management option. Microsoft Intune is an endpoint management solution for mobile devices, an MDM solution that allows the user to securely manage iOS, Android, Windows, and macOS devices with a single endpoint management solution. The component Endpoint Configuration Manager (the…
$5
per user/per month
Pricing
Automox
Microsoft Intune
Editions & Modules
No answers on this topic
Microsoft 365 Business Basic
$5
per user/per month
Microsoft 365 For Individuals
$6.99
per month
Microsoft 365 Apps
$8.25
per user/per month
Microsoft 365 For Families
$9.99
per month
Microsoft 365 Business Standard
$12.50
per user/per month
Microsoft 365 Business Premium
$15
per user/per month
Offerings
Pricing Offerings
Automox
Microsoft Intune
Free Trial
Yes
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
Automox can patch macOS, Windows, and Linux endpoints with PatchOS, an offering at $1 per endpoint/ month with an annual commitment.
The Automate Essentials or Automate Enterprise packages are for scaling IT automation, endpoint configuration, and software updates.
Modules are available with Automox Assist, a one-on-one remote endpoint control and assistance for helpdesk technicians.
In my experience, Kaseya really lacked reporting of any kind and seemed clunky. Although we were on the on-prem version, not their cloud version, in my experience, their support was less than helpful and more interested in cold-call selling rather than helping me solve problems …
Automox lets us control so much more and makes it incredibly easy to target very specific devices for very specific actions. it is also incredibly reliable and I know it will patch as expected with very minimal monitoring. Automox has been the most stable of all the tools I …
Automox blows Intune out of the water in terms of app patching. I don't know why Microsoft doesn't spend money on making pushing patches easy with Intune, but that creates an opportunity for others I guess? If you've ever worked with Intune you know what I'm talking about. If …
Automox is better at patching applications such as browsers or Adobe than Intune. Intune, however, has better reporting and a more robust catalog of device management capabilities. We use both in our environment and utilize each of their strengths, as mentioned above. At the …
From a pricing perspective, Automox is very competitive when compared to others with similar feature sets and capabilities. Other solutions from larger vendors were somewhat limited in their visibility, operating system support, and third-party application integration. Automox …
Automox has a larger list of 3rd party software that is available. In my experience, Automox does not allow you to browse software looking for updates to apply. In my opinion, the reporting of automox sucks comparatively.
Special thing about Automox is that it has customer deploy packages for many remote end points where as other tools listed does not have that privileges. Other tools are not user interface friendly where as Automox user interface is very easy and customizable as well. Unique …
We stoppped using PDQ because it required our users to connect to the corporate VPN. It might take months for some remote users to receive a patch, and often we would have to schedule time with them one-on-one to ensure that it got done. With Automox, we don't have to do any …
I've used a number of other patching products at previous employers. Automox, while it does not have all the bells and whistles of SCCM, Tanium, or BigFix such as software self service or automated deployment through network scanning, software catalogs, or warranty check …
The ability to do 3rd party patching - multiple OS' along with the ability to create an organization platform with managed tiers/silos makes using Automox within a larger org that has specific division heads much easier to use. I can control my division tech while leveraging …
Price and ease of use of the product Automox hands down beat them. But those products also had a monitoring component to consider. But when looking at the monitoring component it wasn't intuitive and hard to implement.
I've used Group Policy, SCCM, Chef, Puppet, psexec, Ivanti, and PDQDeploy. The big lifters like SCCM, Chef, or Puppet enable more complex and refined configuration management. They also require a lot more knowledge to manage let alone at least some understanding of the …
The reason I would score it a nine is because of the inability to “run as.” Since it only runs as a system, this makes some tasks impossible. It would be beneficial to have an encrypted set of credentials in the UI that we can use to “run as,” and also the ability to run as the current user with elevated permissions would be nice. In terms of patching, Automox does a good job, and being able to use Automox to run PowerShell on a computer without needing to open up ports for WinRM is a great feature.
Windows Autopilot makes provisioning user Windows PC laptops a breeze. A user only needs to turn on the laptop, join it to their local WiFi, login with their O365 account then sit back and let Windows Autopilot handle the app installations required for work, configure the laptop settings to meet my organization requirements. I have seen this all completed in less than 30 minutes depending on how fast the internet connection is. Where Microsoft Intune needs to improve I think is the part where it can push out software updates to 3rd party apps. Right now I have to use Automox to fill in this gap.
[Microsoft Endpoint Manager (Microsoft Intune + SCCM)] helps to speed up the deployment of patches/software throughout our environment. I can easily build a package and then deploy across all endpoints.
The ability to supercede software is also quite handy. This automates the removal of old versions and replacing them with newer versions.
The Intune Autopilot option is very useful if you want to deploy software to devices straight out of the box. You can configure them to download software when a user opens a new PC and turns it on for the first time.
I would like to see more detailed error messages when a patch fails. Perhaps at which step it failed at, downloading, installing, etc.
It would be helpful if we could see what stage of installing or downloading a patch is at through a percentage or status bar instead of a vague "Installing..." message
It would also be helpful to have a way to kill or end scripts that are stuck instead of waiting 24 hours for them to automatically end. Something like an "End all actions" button for endpoints on our side would be extremely helpful when testing a script that had a bad line or action in it.
The program itself can be challenging to use, especially if there hasn't been any formal training on the use of the product. Either training/reviewing documentation is recommended prior to using SCCM.
At times, it can be difficult to try and find out why a certain machine that's listed in SCCM says that the endpoint has the SCCM client and shows as Active, but in fact, it's not. It's also difficult at times to try and figure out why the client can't be pushed down to the endpoint.
Even though the remote assistance features in SCCM are really good, it can be challenging at times when the remote options don't work for a particular endpoint, even though the machine is active, online, etc.
Mascom Wireless is a Microsoft shop and SCCM has proved to be helpful in keeping our Microsoft products up to date every month without fail. We also have a Microsoft Enterprise Agreement which we renewed for three years ending 2022. The remote access utility works wonders for the organisation and have saved travel bills including subsistance allowance. We have been able to fulfill security audits both internal and external. We have been able to keep a robust inventory of our computer assets and nothing falls of the cracks
Automox has excellent dashboards that help to identify key performance indicators of where your patching program stands, what to prioritize, and what issues you have. Where Automox struggles is easily identifying what issues are preventing successful patching, seeing what manual patches are successfully installing/not installing, and easily remediating issues with installation issues.
The console is not intuitive and does not work well often. Due to the complexity of the product, documentation can be confusing. When properly configured, routine tasks like OS deployment, remote control, and software deployment are easy to do. Troubleshooting of System Center Configuration Manager issues is hard, as there are various logs, and their content can be hard to understand.
It's a 'heavy' system, which demands a lot of resources form the datacenter perspective. So, make sure you followed the requirements to avoid frustration in the future. From the 'client' perspective, it's fine. I've never had any issue with that.
In my experience, they were responsive but the fixes were more like bandaids than a fix for the underlying problems which they admitted were on their end.
Being a Microsoft product, support was good. Out interaction was limited to our in-house IT team which was installing the Intune app in our mobile device. The installation was smooth and we haven't faced any difficulties with the app while using it. Provides a smooth and secure access to all Office 365 apps in mobile while separating the personal and professional data.
Work with a "test group" of users who you have a good relationship with so that when things don't work properly they understand! Work with your partner nicely without forcing things especially timelines as you are bound to make mistakes and create oversights in the project Management can also interfere with the implementation (which can cause delays) if you make too many mistakes which takes me back to having a "test group" where you have good relations
Automox is able to scale better than PDQ Deploy. We were happier with the 3rd party software patching since we have a lot of different software we use across departments. PDQ deploy required a lot more manual intervention to stay on top of deployments. Automox just ended up being a timesaver for us in the end.
We did not evaluate or use other products like Microsoft Endpoint Manager (Microsoft Intune + SCCM). The main reason we did not evaluate or use other products is because Microsoft Endpoint Manager (Microsoft Intune + SCCM) integrates seamlessly with Microsoft 365 and Windows PCs. Expenses would have increased as well if we had purchased another similar product.
We used to use a different patching solution and since switching to Automox, I have been able to cut the amount of time I spend on vulnerability management by 50% or more. I love how "set it and forget it" some of the policies can be. I love how simple it is to keep an eye on things.
In our current environment, this System Center Configuration Manager had replaced several standalone solutions for patching, imaging, remote assistance, reporting, etc. That saved a lot of time and resulted in money to manage the IT infrastructure.
Once SCCM is deployed and fully configured, all agents are deployed and it is easy to automate a lot of processes and just control them from time to time to make sure that everything is working as supposed to be.
SCCM + Windows 10: great built-in endpoint protection solution. As a result, there is no need to buy additional software for that purpose.
The imaging process is better compared to WDS because you can modify deployment packages and apply patches to a newly imaged machine. This saves tons of time for new employees deployment.
