KACE Systems Management Appliance (SMA) vs. Red Hat Ansible Automation Platform

I think it has added value for any organization. It reduced our Tech Support cost by: -Supporting users anywhere -Reducing users downtime as well keep them informed with the status of their tickets -Managing software and hardware actively -Processing automation -deploy mass software installs, patching or updates - Provide approved software's to users to install without IT help

Incentivized

Red Hat Ansible automates server management, configuration updates, and deployments across our server infrastructure, keeping everything consistent, reducing human error, and saving time. Also provides detailed reports on what is done and uses role-based access controls to keep systems secure by controlling who can make changes.

Incentivized

• Inventory: KACE provides a ton of hardware and software inventory information that is easy to search, filter, and export. This is critical when we need to find the answers to questions about how many of such and such we have in our fleet.
• Patch Management: We were using WSUS before and it was altogether too cumbersome. KACE has given us the power, flexibility, and verification we need to feel comfortable our patches are up-to-date.
• Service Queue: We made KACE our help desk system and it does everything we need it to do. Great improvement over our old system.

Incentivized

• It reduces custom scripting efforts because everything can be scripted in simple, human-readable YAML playbooks.
• Not only servers, but also network devices, VMs, Containers, Kubernetes clusters, etc., can be automated via Ansible, showcasing its extensive list of supported devices.
• It is agentless, which makes it lightweight and allows for easy integration into CI/CD and GitOps pipelines.
• Many Tier-1 telcos use Ansible for Day 0/1/2 automation of RAN, transport, and core infrastructure (e.g., network function lifecycle management, NE configuration push, patching VNFs).

Incentivized

• The KACE SMA needs a better way to handle different roles in the software so certain users can access or administrate certain parts of the software, but not the entire software installation.
• The KACE SMA could improve the ticketing process of projects. The aspects of the title and some information do not always flow down from the parent ticket to its child tickets.
• The KACE SMA could improve the UI of the software with the addition of different CSS color schemes.

Incentivized

• I can't think of any right now because I've heard about the Lightspeed and I'm really excited about that. Ansible has been really solid for us. We haven't had any issues. Maybe the upgrade process, but other than that, as coming from a user, it's awesome.
• Give out Lightspeed for free.

Incentivized

Even is if it's a great tool, we are looking to renew our licence for our production servers only. The product is very expensive to use, so we might look for a cheaper solution for our non-production servers. One of the solution we are looking, is AWX, free, and similar to AAP. This is be perfect for our non-production servers.

Incentivized

Overall, the software is simple to understand and use. That said, most vendors have been slowly updating their user interfaces to HTML5 so that they have a clean updated look and feel. This is where KACE falls short in that the UI is great for a packaged software 10 years ago. This isn't a major limitation as the software is really meant primarily for technology users.

Incentivized

It's overall pretty easy to use foe all the applications I've mentioned before: configuring hosts, installing packages through tools like apt, applying yaml, making changes across wide groups of hosts, etc. Its not a 10 because of the inconveinience of the yaml setup, and the time to write is not worth it for something applied one time to only a few hosts

Incentivized

Great in almost every way compared to any other configuration management software. The only thing I wish for is python3 support. Other than that, YAML is much improved compared to the Ruby of Chef. The agentless nature is incredibly convenient for managing systems quickly, and if a member of your term has no terminal experience whatsoever they can still use the UI.

Incentivized

KACE does exactly what you need it to do, it maintains your computer environment. You can set patch schedules, inventory computers, setup software catalogs; basically everything you need to ensure the computers on your network are being actively managed. This is all with little need for constant configuration or updating the setup.

Incentivized

There is a lot of good documentation that Ansible and Red Hat provide which should help get someone started with making Ansible useful. But once you get to more complicated scenarios, you will benefit from learning from others. I have not used Red Hat support for work with Ansible, but many of the online resources are helpful.

Incentivized

I spoke on this topic today!

Incentivized

We have selected this software because it rolls several different systems into one. We have a helpdesk system with this and an asset and inventory management system as well. We pay one price for the whole system instead of paying multiple companies different amounts that would have totaled more than we pay for the single system.

Incentivized

AAP compares favorably with Terraform and Power Automate. I don't have much experience with Terraform, but I find AAP and Ansible easier to use as well as having more capabilities. Power Platform is also an excellent automation tool that is user friendly but I feel that Ansible has more compatibility with a variety of technologies.

Incentivized

• KACE has saved us from having to spend several days of employee hours in crafting DVDs and duplicating them (100+ DVDs)
• KACE has saved us on the postage required to send out those DVDs for every update (monthly) to all of our customers electronically

Incentivized

• POSITIVE: currently used by the IT department and some others, but we want others to use it.
• NEGATIVE: We need less technical output for the non-technical. It should be controllable or a setting within playbooks. We also need more graphical responses (non-technical).
• POSITIVE: Always being updated and expanded (CaC, EDA, Policy as Code, execution environments, AI, etc..)

Incentivized