We are a medium-sized company, and our fleet is 95% Macs.
Jamf helps us to manage Macs remotely via an intuitive dashboard.
Managing macOS can get difficult sometimes without the help of an MDM. With Jamf, I have control of the fleet with a few clicks.
Being able to update third-party applications without the need for other external tools is another plus.
With minor modifications, we were able to have an almost zero-touch deployment. This way, we know that all Macs will always have the same configurations.
We are also working on the self-service app, which has a lot of potential.
With Jamf, we can create almost a zero-touch deployment which saves a lot of time with flashing the OS, manually installing the apps, and configuring some settings.
This has enabled us to save time for each onboarding/offboarding/laptop change.
I worked in an environment where we had only 10 Macbooks and no MDM, and without Jamf, it was super hard to manage the Macbooks. With self-service, the sky is the limit. You can do whatever you want with it.
There are some out-of-the-box integrations that can help you achieve some results.
Smart Groups with alerts is useful. This will let me have visibility of the environment without having to constantly see what is happening.
After some tweaks, zero-touch deployment is another valuable thing. We are able to configure the laptop with the security requirements needed, default applications, and so on without touching it. This feels great, especially when you send a brand new sealed Macbook to some user.
Another awesome feature is Patch Management. Until this day, many people don't know that this exists. However, it helps a lot with patching third-party applications.
The solution needs cheaper training. Some companies don't have that much budget to invest in training.
They need integrations with known/other services out of the box.
Reports for execs could be more colorful/attractive.
The documentation for the API is still confusing.
Until this day, I still don't know what's the best way to securely run your API in an end-user endpoint.
Some documentation could also be updated or created in cases where a large population uses the same environment (like Jamf + Google + Okta) or something like that.
I've used the solution for two years.
I used Kandji and ManageEngine in previous jobs.
Jamf was already in my current environment, and it just works, so there is nothing to say here.