Cherwell Software was a full suite of service management tools competing with BMC Remedy, ServiceNow, and IBM SmartCloud. It was acquired by Ivanti, and has reached EOL.
N/A
KACE Systems Management Appliance
Score 10.0 out of 10
N/A
Quest now offers the KACE Systems Management Appliance (SMA) as an IT Asset tracking and management appliance (also available as a virtual deployment if hardware requirements are met). Beyond discovery, inventory tracking and license management, KACE emphasizes automating software upgrade distribution with minimal end-user disruption, featuring remote replication for multi-site upgrades and rollouts. KACE SMA may be bundled with KACE Cloud Mobile Device Management (MDM) to form a complete UEM…
Well suited in an IT environment where you have limited staff. It can be managed by one administrator. Reliability of the SaaS environment has been excellent. Flexibility in developing automated workflows to open, manage, and close Incidents. Change Management due to ability to modify OOB to meet the needs of our staff. Contract Management allowing us to be notified when a contract or license is up for renewal and setting reminders. Integrations are not easy to create and manage.
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
Cherwell's email handling automation works flawlessly. The only time that I have ever needed to reset the automation service that drives it is when my own server that houses the small connecting agent has some kind of problem and disconnects us from our hosted Cherwell instance. It just works. Emails to a certain address always result in a new ticket or update to an existing ticket.
Cherwell is literally 100% customization in so many ways that it would be pointless to try to enumerate them. There is a very sizable list of already-created customizations (called "mApps") that you can download and apply to your instance. If you don't like them you can roll them back in seconds. But you can add and configure entire modules using one of these pre-defined, completely free, add-on packages. It's so easy to add features this way that I check the list of available mApps every month or so just to see what functionality I can add.
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.
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.
Cherwell is still the best tool for the job in the market. Even though Ivanti bought them and are trying to convince everyone to move over to Neurons for ITSM, they have stated Cherwell will remain supported indefinitely and have a roadmap for future Cherwell development. Unfortunately, ISM is not as flexible as Cherwell (and the UX is atrocious), hence why many people are sticking with Cherwell (and why many Cherwell customers never purchased ISM originally)
I enjoy the layout and configuration of our Cherwell Service Management instance. It did take me a bit to get used to, as with any new ticketing system, but now that I understand the system more, I thoroughly enjoy it! There are just so many options and the UI is very intuitive.
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.
The browser client is mostly acceptable in terms of performance, but still lacks parity with the rich client. The rich client is not very performant at all. It's built on old architecture and relies heavily on a fast internet connection, good caching and database indexing. There are several unwritten rules with form design (and form arrangement) which most users are not aware of, but can severely impact performance in the rich client. This is where the flexibility of Cherwell can come back to bite you if you step outside the boundaries of these unwritten rules
We generally have a good time with Cherwell support, however, there are the few niche cases where I have to explain how Cherwell works to the customer support agent on the other end. A little more product education for tier 1 support could go a long way in helping expedite support requests from SaaS customers.
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.
I didn't partake in the in-person training, but it was available. I preferred the online method instead, which was a great experience. It was nice to have someone available to bounce questions off of and demonstrate how certain functions worked.
The training was great! We got together to review the system, its UI, and how to perform basic functions. Then there was plenty of time to ask questions and test out the system while there was someone available to assist.
Implementation is a breeze. Each time I've implemented it, we had an outsourced vendor overseeing it & assisting where needed. However, Cherwell OOTB is ready to go, and configuring it for LDAP/SAML, etc. for authentication and user-imports is really straight forward. The infrastructure needed for Cherwell is extremely simple too - and installing the server & database takes no more than 20 mins
Much more customizable than other products, especially when ran in a self-hosted environment. Cherwell [Service Management] allows for greater flexibility of custom development and integrations to allow for automating tasks that traditional ITSM apps are not well suited for. Cherwell [Service Management] gives you the freedom to develop your own objects with minimal licensing costs.
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.
We have never had any major show-stopper issues with Cherwell itself - more so with the infrastructure it sits on. Moving from in-house cloud (on Cherwell's side), to AWS then to Azure has caused multiple problems over the years (some still on-going), however the product has remained fairly stable
As mentioned, they were always great to work with (minus the project management side). My only feedback would be to push back on requirements that don't make sense
As with any standard ticketing system, it helped decrease the time before first contact with clients.
Our department was always concerned with keeping a low budget, and it was cheaper than most.
My supervisor could easily tell how many resources were being put into each employee, so we had more visibility of our team's capabilities at a given time if we needed to take on something complex.
