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
Microsoft Intune
Score 8.3 out of 10
N/A
Microsoft Intune (formerly Microsoft Endpoint Manager), combining the capabilities of the former Microsoft System Center Configuration Manager, SCCM or ConfigMgr, is presented as a unified endpoint management option. Microsoft Intune is an endpoint management solution for mobile devices, an MDM solution that allows the user to securely manage iOS, Android, Windows, and macOS devices with a single endpoint management solution. The component Endpoint Configuration Manager (the…
ServiceNow was administrative heavy and required more than one admin. Also expensive for smaller customers. Remedy was scaled more for enterprise customers where we are small to mid-sized. FootPrints - we replaced FootPrints with Cherwell due to a lack of BMC putting any further …
Cherwell is the most customizable and powerful ITSM product without programing your own system from scratch. It has the most "heart" of any product I have used.
We went from a HP SM application with complex development and extensive cost. During our evaluations of the tools in the marketplace it became very clear that Cherwell Met or Exceeded all other applications for the functions we needed especially cost. We were very skeptical of …
We used Altiris previously to image computers in the organization. The only way we could deploy that was through a network boot, but with SCCM we have an option in Software Center to start an image on a client. This is much easier to understand for users if/when they need to …
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.
Windows Autopilot makes provisioning user Windows PC laptops a breeze. A user only needs to turn on the laptop, join it to their local WiFi, login with their O365 account then sit back and let Windows Autopilot handle the app installations required for work, configure the laptop settings to meet my organization requirements. I have seen this all completed in less than 30 minutes depending on how fast the internet connection is. Where Microsoft Intune needs to improve I think is the part where it can push out software updates to 3rd party apps. Right now I have to use Automox to fill in this gap.
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.
[Microsoft Endpoint Manager (Microsoft Intune + SCCM)] helps to speed up the deployment of patches/software throughout our environment. I can easily build a package and then deploy across all endpoints.
The ability to supercede software is also quite handy. This automates the removal of old versions and replacing them with newer versions.
The Intune Autopilot option is very useful if you want to deploy software to devices straight out of the box. You can configure them to download software when a user opens a new PC and turns it on for the first time.
The program itself can be challenging to use, especially if there hasn't been any formal training on the use of the product. Either training/reviewing documentation is recommended prior to using SCCM.
At times, it can be difficult to try and find out why a certain machine that's listed in SCCM says that the endpoint has the SCCM client and shows as Active, but in fact, it's not. It's also difficult at times to try and figure out why the client can't be pushed down to the endpoint.
Even though the remote assistance features in SCCM are really good, it can be challenging at times when the remote options don't work for a particular endpoint, even though the machine is active, online, etc.
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)
Mascom Wireless is a Microsoft shop and SCCM has proved to be helpful in keeping our Microsoft products up to date every month without fail. We also have a Microsoft Enterprise Agreement which we renewed for three years ending 2022. The remote access utility works wonders for the organisation and have saved travel bills including subsistance allowance. We have been able to fulfill security audits both internal and external. We have been able to keep a robust inventory of our computer assets and nothing falls of the cracks
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.
The console is not intuitive and does not work well often. Due to the complexity of the product, documentation can be confusing. When properly configured, routine tasks like OS deployment, remote control, and software deployment are easy to do. Troubleshooting of System Center Configuration Manager issues is hard, as there are various logs, and their content can be hard to understand.
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
It's a 'heavy' system, which demands a lot of resources form the datacenter perspective. So, make sure you followed the requirements to avoid frustration in the future. From the 'client' perspective, it's fine. I've never had any issue with that.
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.
Being a Microsoft product, support was good. Out interaction was limited to our in-house IT team which was installing the Intune app in our mobile device. The installation was smooth and we haven't faced any difficulties with the app while using it. Provides a smooth and secure access to all Office 365 apps in mobile while separating the personal and professional data.
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
Work with a "test group" of users who you have a good relationship with so that when things don't work properly they understand! Work with your partner nicely without forcing things especially timelines as you are bound to make mistakes and create oversights in the project Management can also interfere with the implementation (which can cause delays) if you make too many mistakes which takes me back to having a "test group" where you have good relations
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 did not evaluate or use other products like Microsoft Endpoint Manager (Microsoft Intune + SCCM). The main reason we did not evaluate or use other products is because Microsoft Endpoint Manager (Microsoft Intune + SCCM) integrates seamlessly with Microsoft 365 and Windows PCs. Expenses would have increased as well if we had purchased another similar product.
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.
In our current environment, this System Center Configuration Manager had replaced several standalone solutions for patching, imaging, remote assistance, reporting, etc. That saved a lot of time and resulted in money to manage the IT infrastructure.
Once SCCM is deployed and fully configured, all agents are deployed and it is easy to automate a lot of processes and just control them from time to time to make sure that everything is working as supposed to be.
SCCM + Windows 10: great built-in endpoint protection solution. As a result, there is no need to buy additional software for that purpose.
The imaging process is better compared to WDS because you can modify deployment packages and apply patches to a newly imaged machine. This saves tons of time for new employees deployment.
