The Red Hat Ansible Automation Platform (acquired by Red Hat in 2015) is a foundation for building and operating automation across an organization. The platform includes tools needed to implement enterprise-wide automation, and can automate resource provisioning, and IT environments and configuration of systems and devices. It can be used in a CI/CD process to provision the target environment and to then deploy the application on it.
$5,000
per year
Symantec Client Management Suite
Score 7.5 out of 10
N/A
Symantec Client Management Suite is designed to automate time-consuming and redundant tasks for deploying, managing, patching, and securing desktops and laptops so organizations can reduce the cost and effort of managing Windows, Mac, Linux, and virtual desktop environments.
The thing I mentioned earlier where we're constantly dealing with federal regulations or new agents that they want us to install and deploy and just getting those out in a consistent manner in a canned installation via Playbook is ideal
Whenever you have computers that aren't easily accessible or you have a big site to cover (or multi location), Symantec Client Management Suite (CMS) is really great to manage all your computers, if it's for installation, software, licenses or even status. Setting up all you need from CMS can take some time, especially when you're in a multi-location site. We had to ask the Symantec engineers to help us a couple of times and set things up because even if we followed the documentation, it wasn't an easy task. But at least, the Symantec engineers are people that know what they do and they're really efficient at it.
Makes it easy to create and share automation in one central hub.
Ansible content collections give me the ability to reuse code, making it rapid to carry out complex IT processes.
Event-driven automation allows me to reduce manual tasks: it is rapid to know which action to take and respond automatically by receiving events from external apps automatically.
Patch Management: We are able to easily deploy patches to all our workstations and accurately report on compliance.
Software Delivery: We do a lot of software deployments to our end users and with CMS we can quickly create policies or tasks to perform these deliveries and get quick results on our success or failures.
Inventory: Ease of use to get reports of what workstations have what software installed, patch levels, or hardware specifications.
Workflows should have more flexible paths than just success or failure.
The upgrade process can be challenging with differences in security and environment.
There is an opportunity to add CICD functionality into the tool.
For development, it would be nice to have the option of editing a repo directly from AAP to allow quick tests/reruns. Then, allow it to push the updates back or create a new branch/PR in GitHub.
The RBAC is good but could use improvements. One example would be an option that allows admins to assume the access of another user to validate it works as expected.
More transparency with the roadmap would be a welcome change. New and upcoming features are usually a surprise until a major Symantec Event takes place but little is heard about those features before and even after, in some cases, leading up to a release.
Documentation for some items is poor. Especially around the Workflow product. It was intended that the documentation for the elements in a workflow would be crowd-sourced, which is a good idea, but in order for that to happen, more people need to be using it and taking the time to draw up the documents.
Cost. Its always a big topic, especially in higher-ed, but Symantec could do more to lower its costs for some product lines in order to gain more acceptance and support. If that was done and more institutions could get their student workers to use the product, once they leave college and go into the "real-world" there is a possibility that they would start recommending Symantec products because of their use in College.
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.
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.
Support at Symantec isn't that great. Client Management Suite isn't even listed on the Support Portal when trying to open a ticket. Your best bet for support is actually the user groups that Symantec hosts. The members of the groups are usually very responsive. With Broadcom buying Symantec, I've seen a huge jump in personnel leaving Symantec, so I'm assuming the support is just going to get worse. Recently for a simple question, I reached out to 5 people just to find out 4 of the 5 had left the company.
AAP doesn't truly stack up against any of the products mentioned except for Aria Automation. But, it is extensible and open and has a lower cost to entry.
Although there are other tools that can be utilized I don't believe those tools are as robust as Symantec Management Platform. The Symantec Management Platform was chosen because of the value it returns internally and for our customers. You can pull just about any data element from an endpoint and provide detailed reports or great graphs for the C-Level
