"The single pane of glass for managing devices is helpful because it allows me to perform updates and control things without having to disturb the doctors or nurses."
"KACE has made our life much easier since we got off the Microsoft solution. The Microsoft solution was a lot harder to image over different ports and stuff. They would only have this one place where we could do all the imaging. Now, we have a whole building where we can image from. This means that we can image from our storage area, where we have a place to do our imaging. We can also image right at our desks, which is a lot easier."
"Asset management is most valuable. It is essential for all customers. The other features are also useful, but asset management is most important."
"Patching is definitely the most valuable feature. It gives us good, centralized software, which comes in very handy since we are doing 400 servers at a time. It enables us to manage all the servers, and to deal with the application team regarding reboots and scheduling."
"When vulnerabilities are exploited so much, it is nice to be able to quickly detect or deploy what is needed within our off-work hours or during work hours without a reboot."
"The most valuable feature of KACE is the mass package deployment. There are a lot of endpoint management solutions in the market. The way KACE responds is with the installation management feature, which is done in a very intelligent way, as well as scripting. It's wow. It's really wow. On top of that, there is a mass undeployment feature as well."
"The big pros of Quest KACE Systems Management are its simple interface, and simple, direct management. It's very easy to maintain and manage the device, and it's easy to get it up and running. You can have it up and running in an hour..."
"The ability to build scripts right on the deployment center itself, as well as building groups that take those scripts/task chains has been absolutely invaluable and one of the most important parts of my whole environment."
"Being a game-changer in configuration management software is what has made Ansible so popular and widespread. Much of IT is based on SSH direct connectivity with a need for running infrastructure in an agentless way, and that has been a big plus. SSH has become a great security standard for managing servers. The whole thing has really become an out-of-the-box solution for managing a Unix estate."
"One of the most valuable features is that Ansible is agentless. It does not have dependencies, other than Python, which is very generic in terms of dependencies for all systems and for any environment. Being agentless, Ansible is very convenient for everything."
"It has improved our organization through provisioning and security hardening. When we do get a new VM, we have been able to bring on a provisioned machine in less than a day. This morning alone, I provisioned two machines within an hour. I am talking about hardening, installing antivirus software on it, and creating user accounts because the Playbooks were predesigned. From the time we got the servers to the actual hand-off, it takes less than an hour. We are talking about having the servers actually authenticate Red Hat Satellites and run the yum updates. All of that can be done within an hour."
"Ansible provides great reliability when coupled with a versioning system (git). It helps providing predictability to the network by knowing exactly what's being pushed after validating it in production."
"Ansible is agentless. So, we don't need to set up any agent into the computer we are interacting with. The only prerequisite is that the host with which we are going to interact must have the Python interpreter installed on it. We can connect to a host and do our configuration by using Ansible."
"The software asset management functionality is an area that needs to be improved. It could be more automated because when connections need to be made, such as when I connected Adobe and my malware removed, the process was pretty much manual."
"My biggest complaint is that almost every time they send out a new version, it fixes something and breaks another. Something that wasn't working in the last version now works, but something else stops; or they'll remove some dashboard that I really found to be nice and replace it with something totally different that I could care less about."
"Scalability is my primary concern right now."
"What could be improved is the possibility to use replicas in a secure way outside our network in order to maintain the machines that never connect to our corporate network."
"It is a little bit difficult to use the license compliances because you need to decide when you are using the software catalog if you are using it with their license compliance or the normal software part. Under the inventory, you can use software as a menu link or software catalog. Most of my specialist software is not in the software catalog. When I try to import them, in my license compliances overview, there are cryptic names for this software that I have to import. That is not very good for the reports that I use. When I take them to my bosses, they see cryptic names of software that they don't understand. It would be much better for me if I could use software and the software catalog as well for the license compliances."
"I would like for there to be improvement when it comes to Microsoft and Windows updates. It has the ability to do it but the control of it is not there like I have in the Windows Server Update Services. The way KACE does it is still very granular. You don't really see the process like it is in the Windows Server Update Services. I think that would be one of the biggest things that I would like to see KACE really put some work into and really make that a big enhancement."
"There is always room for improvement. However, the system does most of what we need at this moment."
"The initial setup was complex. It is a Linux-based virtual server, where the customer cannot get into the back-end, so you can only follow their prompts. Then, there are specific things that have to be done in their implementation and upgrade phases that have to be done in a certain order or steps. If you don't get those steps right, the system doesn't work. I think that either simplifying that process or providing really good step-by-step documentation would be helpful."
"Ansible is great, but there are not many modules. You can do about 80% to 90% of things by using commands, but more modules should be added. We cannot do some of the things in Ansible. In Red Hat, we have the YUM package manager, and there are certain options that we can pass through YUM. To install the Docker Community Edition, I'll write the yum install docker-ce command, but because the Docker Community Edition is not compatible with RHEL 8, I will have to use the nobest option, such as yum install docker-ce --nobest. The nobest option installs the most stable version that can be installed on a particular system. In Ansible, the nobest option is not there. So, it needs some improvements in terms of options. There should be more options, keywords, and modules."
"The area which I feel can be improved is the custom modules. For example, there are something like 106 official modules available in the Ansible library. A year ago, that number was somewhere around 58. While Ansible is improving day by day, this can be improved more. For instance, when you need to configure in the cloud, you need to write up a module for that."
"When you set up Playbooks, I may have one version of the Playbook, but another member of the team may have a different vision, and we will not know which version is correct. We want to have one central repository for managing the different versions of Playbooks, so we can have better collaboration among team members. This is our use case for using Git version control."
"Accessibility. Ansible uses a CLI by default. Those accustomed to it can find their way and adopt the YAML files easily over time. But, some users are more comfortable using UIs..."
"Some of the modules in Ansible could be a bit more mature. There is still a little room for further development. Some performance aspects could be improved, perhaps in the form of parallelism within Ansible."
The KACE Systems Management Appliance provides a growing organization with comprehensive management of network-connected devices, including servers, PCs, Macs, Chromebooks, tablets, printers, storage, networking gear and the Internet of Things (IoT). KACE can fulfill all of the organization's systems management needs, from initial deployment to ongoing management and retirement.
Quest KACE Systems Management is ranked 3rd in Configuration Management with 27 reviews while Red Hat Ansible Automation Platform is ranked 2nd in Configuration Management with 5 reviews. Quest KACE Systems Management is rated 8.8, while Red Hat Ansible Automation Platform is rated 8.4. The top reviewer of Quest KACE Systems Management writes "We can see everything for the endpoint management of devices using a single interface". On the other hand, the top reviewer of Red Hat Ansible Automation Platform writes "Enables us to efficiently manage an almost unlimited number of nodes". Quest KACE Systems Management is most compared with Microsoft Endpoint Configuration Manager, Microsoft Windows Server Update Services, BigFix, Kaseya VSA and ManageEngine Patch Manager Plus, whereas Red Hat Ansible Automation Platform is most compared with Microsoft Endpoint Configuration Manager, Red Hat Satellite, VMware vRealize Automation (vRA), BigFix and Microsoft Azure DevOps. See our Quest KACE Systems Management vs. Red Hat Ansible Automation Platform report.
See our list of best Configuration Management vendors.
We monitor all Configuration Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.