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
ServiceNow IT Service Management
Score 8.5 out of 10
N/A
ServiceNow is a fast-growing service management provider that went public in 2012. Built on the ServiceNow Now Platform, the IT Service Management bundle provides an agent workspace with knowledge management, and modules supporting issue tracking and problem resolution, change, release and configuration management, and (on the higher tier ITSM Professional plan) ITAM and software asset management.
$10,000
per year
Pricing
Automox
ServiceNow IT Service Management
Editions & Modules
No answers on this topic
Starting Price
$10,000.00
per year
Offerings
Pricing Offerings
Automox
ServiceNow IT Service Management
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 …
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.
In our organization, we are using ServiceNow extensively. Change Management, Incident Management, Problem Management, Time tracking are few modules which we use extensively. This sort of model will work for any product or service based companies as the product is built on ITIL framework. So this product will be suited for small or large scale companies to better organize and add controls and track SLA's for technology or business process.
When I have a number of requests to make, for example a request to add a dozen or so user accounts to more than one group account in Active Directory , I can put all the needed information into the initial form, add it to my "shopping cart" and all of that information remains on the screen for the next item for which I only need to edit a few items (like the AD group name in this example), and keep adding them to the shopping cart until I have them all. When I "Check Out" each of those items is generated as a separate task under the one request. It simplifies and expedites the creation and tracking of these kinds of requests.
I can easily and quickly see what tickets are currently assigned to me in order to prioritize them and remain aware of my workload.
Numerous fields for CIs can be used when trying to find the entry for a particular item. For example, IP Address, server name, raw text, classification, and so on.
To help with making sense out of related tasks, when a task is assigned to me and I need to open another task for a different team to work in order to complete my task, I can open a sub-task from my ticket so that the relationship between the two can be pulled up later into reports. For example, I may have a task to build a new vm, and need to open tasks for networking, security accounts, software installation and so on. By opening sub-tasks from my assignment, the time spent by all parties concerned is tied together for more meaningful cost accounting.
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.
It is hard to find areas for improvement, the tool is very powerful. That said, building the CMDB still involves some manual interaction which was not how it was presented in demos.
The CMDB data is almost too deep and detailed. When you build the relationship map it can be so large that it is overwhelming. You can limit this, but the default maps are massive if you are discovering lots of device classes.
The product is expensive. Since they are the leader in the industry and the product has tons of features, they definitely charge for it!
To be completely honest setting up a new ticketing system can be a pain in the ass. Once you have it setup and customized the way you want it, you don't want to switch unless you're unhappy with the product. Unless future releases and updates really muck the system up, I wouldn't change.
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 dashboard is so confusing, [there are] many clicks to open a task and search by a ticket. The Enterprise customisation [we did] has finished to kill the software and creates a really bad experience on a daily basis. [It is] So slow, and so many clicks to process a ticket. Works only on IE so, that [should] make you realize that [it] is a bad idea.
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.
I would give it this rating because we have had no major issues with the support for ServiceNow after we implemented it at our organization. They seem to respond promptly and efficiently if we ever do need to open a support case with them about an issue we are having.
To type in what should be a text box, you have to click an empty cell, a tiny text box pop up opens with a check box and an X. You the. Type in the text box and have to click the check mark. If you have a bunch of fields to fill out, doing this is very annoying. Absolutely know thought went in to this. I'm sure somebody in marketing thought it was a good idea. It wasn't.
Without exception, every client I have worked with has been very happy with their resulting product. While this is partly due to my work, I must point out that the platform is the winning decision, not the implementer.
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 used to use Jira to handle service tickets but it's way too robust for something this straightforward. Due to the nature of Jira, you needed to already have a lot of documentation and knowledge about who should be assigned the ticket, so the lift of creating a ticket was time consuming.
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.
Overall ServiceNow has a positive impact on getting the SLA of tickets down in supporting our customers.
One negative impact has been the amount of time to get the product to produce an ROI, it's almost too big to fail and too big to replace. You almost become committed to the product. Good or bad.
Another negative impact would be if you track metrics of employees and time tracking, there is a lot of scenarios where engineers will track time on tickets but not get credit for closing them as the assignee function of tickets can only be tied to one user and credits only the engineer who closes the ticket.
Another positive impact would be the level of security for permissions and scaling the workloads is robust and you will get out of the system what your team is willing to put in.
