Jamf Pro vs. ManageEngine Endpoint Central

Well suited for any organization that wants to manage apple products. It's extremely easy to integrate and has many connectors for existing enterprise infrastructure applications. Certificate management is a breeze. Not so suited for smaller businesses that only have 10-20 devices. Jamf has another product called JAMF Now that would suffice for those areas.

Compared to other endpoint management tools that I have experience with, the patch management and the system health statistics functions work much better and are easier to navigate. The endpoint control functions are nowhere near as good as what I've used with Kaseya's VSA application - with that you could remote control a machine via a remote desktop type interface, or you could connect to the command line or PowerShell and it functioned as if you were directly connected to the machine - command history, tab completion, etc.. "just worked" and if the endpoint disconnected, you didn't lose anything that was going in the window when it reconnected (Exception being if the machine rebooted), grouping systems by department or building was also easier, as was moving systems between groups

Incentivized

• Jamf Pro's Self Service is a great mechanism for making software available to end uses as they need it.
• Jamf Pro is also great for creating plans called PreStage Enrollments that allow for computers to skip many of the setup screens, as well as automating account creation.
• Jamf Pro in combination with Apple Automated Device Enrollment (formerly DEP) allows for devices to supervised and managed, this combination allows for locking, remote wipe of devices, and finding locations of devices when put into lost mode.

• We set alerts when a devices gets low on disk space. That is automatic and creates a ticket in ME SDP. We are then able to Add space to a VM Desktop, and then go thru ManageEngine Endpoint Central to extend the drives so the entire process can be done without interruption to the end user.
• Using the patch scans we can easily see what patches have been installed for all manufacturers not just Microsoft, without having to physically go to the device. It also allows us to choose which patches we want to push out and automate the process so we can be hands off, freeing up out time for other things.
• Remote access to devices. This allows us to remotely make changes, not just via remote control but also make registry changes and clean up space without going to the device and without interruption to the end user.
• Alerts. We have set up to get email alerts when new hardware is plugged into any computers. This lets us know if someone is bringing in un-authorized equipment (thumb drives, hubs, etc) to better manage what is/is not on our network.

Incentivized

• Training options are terrific, but costly.
• Finding what you need in Jamf Pro can be tough at times. The interface is not what I would call friendly.
• You'll need static credentials for Jamf Pro. They don't integrate with the Jamf Account, and it doesn't offer 2FA. SSO is an option, but it's not simple to set up.

• When I first started using ManageEngine Endpoint Central, the UI felt very complicated and cluttered up, which means as a new user, it took a lot of time to get used to using it and knowing where certain features are. This was also because specific features aren't obvious to the user, it can take time to find them through multiple routes.
• When pushing out specifc software to a large number of endpoint devices such as 1500 in my organisation, the deployment fails a lot more meaning some devices dont receive the software and this has to be done manually for them. This can take a lot of time.
• When an issue is reported about ManageEngine Endpoint Central, for example it constantly crashing when being heavily used. The support was delayed and it took a lot of time for first line support to address the issue and escalate it.

We stepped away and are looking at different products that integrate with our entire fleet MDM solution rather than focusing specifically on Apple products. An all in one solution fits our needs better and is more cost-effective in the long run. Jamf Pro needs to improve some features and support but overall its a good product.

Incentivized

ManageEngine is considered an excellent product due to its comprehensive suite of solutions for IT management, with ManageEngine Endpoint Central specifically excelling in endpoint management. The platform stands out for its user-friendly interface, robust features, and versatility in addressing diverse IT needs. It offers organizations a centralized solution for endpoint security, patch management, software deployment, and asset management

Jamf Pro has done pretty much anything we've needed with little setup headache. If we hit a wall, the Jamf user community and tech support departments both are more than willing to help solve problems. Tech support is excellent, but the surprising thing is the user base is by far the biggest resource. Jamf users love to help each other, by directly chatting about issues, posting best practices, or just posting info on the forums.

The application itself is great. However, I have little insight to what the patches are doing. Being able to see patch download progress, not just the status, would be great. The user interface could also use an overhaul. The countless menus, sometimes containing similar if not duplicate tabs can be frustrating to navigate.

Incentivized

Jamf Support is very responsive and usually assists in any challenge we are tackling. They are also very transparent when they are allowed to be. I personally love our Jamf Pro support rep and don't fear messaging their support team.

The immediate chat support is great and very helpful. However, if you need escalated support or have a deeper need that the chat tool can't help with, you will experience significant wait times and slow responses. The time zone difference becomes painful to the point of often just giving up.

They made me more comfortable using the product.

The training session was beneficial because it expanded my knowledge about Jamf products and really learn what I am capable of doing with Jamf Pro in terms of managing Apple computers and devices. Immediately after the training course, I was able to implement what I learn to our cloud instance.

Migration from an existing MDM requires device wipe and reenroll for full supervision of the device. It's somewhat painful. User enrollment makes things easier, but you miss out on full management.

Even thought we are using this solutions for different purposes (macOS device management VS mobile device management), I think at the end Jamf Pro is more focused or aimed for macOS management, and mobile device management is just a good addition to that. Same I can tell about Ivanty, is more about iOS/Android management rather than macOS

I tend to use a combination of solutions to keep the estate running efficiently. ManageEngine Endpoint Central has more control over the timing of patching for users. Juggling users being able to work and keeping systems up to date with user satisfaction in mind is a monthly goal. Pushing updates with giving users some control seems to be working.

Incentivized

• Jamf Pro has allowed us to minimize the time it takes to deploy devices. We can use zero-touch deployment methodologies which allow devices to go directly to end users and allow end users to get up and running without needing IT's help.
• We have implemented both a third-party & macOS patching service, which allows us to ensure all apps and versions of macOS are updated and secure.

• It has greatly helped us with our compliances through the compliance scans, such as taking our CIS compliance from 36% up to around 90%.
• It has massively reduced the number of application/patch vulnerabilities through automated patching & dynamic configurations with custom scripts. From 60 criticals and 300 highs down to just 5 criticals and 25 highs, very quickly.
• It has helped us identify issues with our Bitlocker not syncing to Azure AD properly, because the recovery keys in ManageEngine were always correct but werent always correct in Azure AD.

Incentivized