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
Spiceworks Help Desk
Score 7.7 out of 10
N/A
Spiceworks offers a set of free tools for IT network management and help desk support ticketing. The inventory management system essentially provides comprehensive device information for asset management. The Spiceworks Network Monitor provides information on observed IT for problem tracking and server performance monitoring. And finally, the Spiceworks Help Desk Software lets IT personnel stay on top of issues across the network with a ticketing system. Help desk roles with role-based…
It has helped save us so much time, as it was designed to automate mundane and repetitive tasks that we were using other tools to perform and that required so much manual intervention. It does not work very well within Windows environments, understandably, but I would love to see more integration. I want it to be sexy and attractive to more than just geeky sysadmins.
It's a great helpdesk solution - we currently have five years of data within it, roughly 25,000 tickets. The older edition is a great inventory and software license tracking tool. It is easy for users to use the interface and submit tickets and requests on the web, and its email integration is solid. The new version is a below-average system monitoring tool, only giving up/down status and a few other metrics.
Debugging is easy, as it tells you exactly within your job where the job failed, even when jumping around several playbooks.
Ansible seems to integrate with everything, and the community is big enough that if you are unsure how to approach converting a process into a playbook, you can usually find something similar to what you are trying to do.
Security in AAP seems to be pretty straightforward. Easy to organize and identify who has what permissions or can only see the content based on the organization they belong to.
YAML is hard for many to adopt. Moving to a system that is not as white space sensitive would likely increase uptake.
AAP and EDA should be more closely aligned. There are differences that can trip users of the integration up. An example would be the way that variables are used.
Event-driven Ansible output is not as informative as AAP.
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.
Spiceworks is a free tool, so there would be no hesitation if we are required to upgrade it. We have installed Spiceworks on a dedicated server with more than enough resources to get the most from this tool, so we will have this running in our department for years to come.
Spiceworks is user friendly and easy to set up. It can be customized to suit your needs. If there are any problems, you can go to the community forums for support and be in contact with many IT Pros, as well as the Spiceworks support staff and development teams who are always happy to help users out
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.
Spiceworks has been working out of the box, and some of the basic customizations have been successful with just our internal staff handling. We don't have any other issues with the tool. It provides us with the inventory information we want in a quick and concise report in a variety of formats for our team.
If you can spin up a VM to run it on, you'll thank yourself later. If you have remote sites, set up a local server (or dedicated computer) at each site and set them up as remote collectors for the main site. You'll save time and bandwidth
I haven't thought of any right now other than just doing our own home-brewed shell scripts. Command line scripts. And how does this compare? It's light years ahead, especially with the ability to share credentials without giving the person the actual credentials. You can delegate that within, I guess what used to be called Ansible Tower, which is now the Ansible Automation platform. It lets you share, I can give you the keys without you being able to see the keys. It's great
EGroupware UI is clunky and hard to use, Jira is great but the pricing is expensive in comparison with spice works that has a free version and you can test it out properly before buying and make a correct decision based on your business plan and company objectives with the right software.