Cherwell Service Management vs Microsoft Endpoint Manager (Microsoft Intune + SCCM)

• After proper training on setting up the views and servers, Cherwell did a good job separating various department ownership of tickets. Our work views weren't cluttered with irrelevant information.
• There is a lot of information that can be embedded into tickets. Such as sub-task assignments that could contain almost the same information as a ticket itself. Lot of customization options.
• Custom personal dashboards were nice, once I figured out how to do it. Not everyone wants to see things the same way as other people, and being able to move touch points where you want is always a plus.

Read full review

• [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.

Read full review

• Sometimes comments made on a ticket do not generate emails to the technician who owns it, and they will not know there is an update from the customer without checking it
• Sometimes I will see an error pop up when copying text but it can easily be closed
• Sometimes the time-out window for staying logged in does not appear on top of other applications so I will not know it's logging me out

Read full review

• 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.

Read full review

• Having a single SaaS instance of Cherwell has allowed our organization for the first time seamlessly transfer tickets across regions and allow for unprecedented communication between our groups. We look forward to opening the tool to all global IT teams and incorporating all major modules (Problem, Change, CI & Knowledge and more!) where we'll finally all be on the same tool and various IT data will finally all be in a relational database.
• Ongoing costs can be lowered because we now have enough in-house expertise to manage most of our routine Cherwell modifications and management.
• Once Cherwell is fully implemented at our organization, we'll be able to do with several separate systems and databases where all IT information is currently stored which will make things more simple and cost-effective to maintain.

Read full review

• Cuts down our software deployment and patch management time compared to our old tools.
• Better reporting capability to determine the success to fail ratio of a deployed software or patch and additional information provided to mitigate the failed deployment.
• Consistent tool usage across our global units with centralized reporting to monitor monthly patch and software deployment results.

Read full review