Addigy vs. Jamf Pro vs. Kandji

It is more suited for a environment were all they used is Apple devices. it make sit more complex to manage more then 1 portal for the same users the inly difference is them having Windows vs Mac OS. It is great to create profile with rules and manage your employees and track what they are doing

Incentivized

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.

Kandji is well-suited for the following: - Onboarding remote employees (we are a remote company). Kandji offers zero-touch deployment via Apple Business Manager, making it incredibly easy to configure our Macs. -Maintaining security and compliance for Apple devices -Managing a fleet of iOS devices in the field. Where it's less appropriate: -When there is a mixed OS environment -If you have a highly custom or script-heavy environment.

Incentivized

• Easy to use
• Support is always reachable
• Built-in profile manager
• Constantly evolving

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.

• Pushing custom scripts
• New device deployment
• App updates

Incentivized

• security risk
• UI could use improvement
• slow response

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.

• Problem after problem after problem with employees getting locked out of their laptops, (which was the whole reason we switched to Kandji - to prevent that from happening), employees ultimately having to factory reset their laptops to get back in, pop-ups that never go away, and continuous password sync issues.

Incentivized

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

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.

I gave it an 8/10 because overall, it offers a spotless and intuitive interface that makes routine device management easy. Features such as onboarding, app deployment, and compliance enforcement are handy, thanks to the various blueprints we can set up. The only reason I didn't give it a 10 is that it lacks some advanced configurations, and the reporting aspect is not as customizable.

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.

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.

Adiggy is robust but bitdefender makes it 100% better since your able to add both Windows and Apple devices and manage them and see them on the same site push updates and remote into them . Able to group them by categories and change depending on the priority that you would filter them by

Incentivized

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

With Intune, they aren’t friendly with Macs. We had to add each app individually and constantly update the packages for updates. Even when we do everything right, it still doesn’t work all the time

Incentivized

• Centralized Management for Multiple clients
• Efficient access to data

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.

• They promised us we could add devices as needed. I even had that written in an email. However, they rescinded that promise and required us to add devices in buckets of 50. That means, since we had 55 users, we had to pay for 100 licenses.
• Password issues were made much worse by using Kandji instead of our old MDM (Hexnode).
• Overall, Kandji created major headaches with laptop instead of improving.

Incentivized