In-Depth Review of the Kandji Platform

Рет қаралды 9,882

Күн бұрын

Пікірлер: 10

@craverst 11 ай бұрын

Thanks for the great review. We did the same, challenged Jamf against Kandji and we came to the same conclusion. Our fleet are currently more than 400 devices and it is almost impossible to manage devices in the same way you do with Jamf. If you focus on automation, APIs or options like "Smart Groups" there is no better MDM for Apple than Jamf.

@RocketmanTech 11 ай бұрын

Simplicity and customization don't go hand in hand, and I often find that when I go for the "simple" solution when I actually needed something more customizable, it ends up becoming more complex than if I had just started with the right solution.

@AlphaSphere 6 ай бұрын

Great overview, What types of custom attributes is everyone using out there? In the video you mentioned the country the device is in based on IP. What else? I've seen battery charge cycles as well, but what else?

@VeXeBB 11 ай бұрын

Hey sir, I switched from Jamf Pro to Kandji after using Jamf for 2 years. While I do think Kandji is "stripped" of more settings and basically looks like typical "web app" we need to keep in mind that Jamf Pro (aka Casper) they were founded almost 20 years(?) ago. I do think that Kandji is "worse" version of Jamf but I would recommend Kandji over Jamf for companies or start ups up to 300/500 devices. Great video tho!

@RocketmanTech 11 ай бұрын

The number of the devices isn't really the concern, it's the complexity of the workflows. I often find that companies over 100 devices start to get more complexity in their environments, but there's certainly new companies that are around the 300-500 range where I'm sure Kandji would still be a good option. I think some better criteria would be for going with Jamf: - Do you have many different workflows for devices? - Do you deploy enterprise level software (Cisco AnyConnect, McAfee Web Proxy, Crowdstrike, Palo Alto, ect)? - Are you highly security focused? - Do you have unique workflows that don't fit into Kandji's box? - Do you require advanced level support for your users? For us, we would never manage any client using Kandji, no matter how small or how simple, because we already have a high understanding of Jamf, so it's actually easier and much better for us to manage a server using Jamf. And if a company is looking for Tier 3 support from a service provider (like ourselves) providing a high level of Mac expertise, more often than not they won't support a product like Kandji, since they would already have the expertise in a more robust platform and would prefer to use that. So if I am to simplify this, if you can get by without a Mac expert on your IT team, you're probably fine. If you need to have a Mac expert on your team, you're probably going to want Jamf, because that's the tool they will prefer.