We are actually a service provider. Most of our clients are using Jamf.
The main use case is only with Macs. If you want to manage a complete Mac, For example, similar to how we do in a CCM for our core Windows devices, if you want to do that with Mac, then the Jamf tool is the best tool. You can manage everything for Mac devices.
It's a good product. From the reviews that we are getting, the feedback from the client, the tool is very good on the Jamf side - especially for the Macs.
The initial setup is simple.
The stability is good.
The solution offers a nice, updated UI.
For Windows, we have a reset option. We'd that option available for Mac. That will be great. Since we don't currently have that, the alternative takes up a lot of time and requires an engineer to visit, get a hold of the laptop, and reinstall the operating system. If we could do this as a reset and have the option to handle it remotely, that would be a big improvement.
I've been using the solution for more than four years.
Clients always look for a kind of solution with no issues reported and also they want a kind of zero-touch deployment that doesn't need any user or any engineer interactions for the enrollment. This solution is perfect for this.
In very rare cases, with the type of implementation we use, we used to get support from Jamf, from Windows. Otherwise, we don't interact with them. Everything, all the instructions, are already there in GitHub. Reaching out would be a very rare case. If any new setup needs to be done or any new whichever is not available in GitHub, definitely we'll reach out to Jamf. Otherwise, it's zero-contact.
The initial setup is simple, actually. We just need a Jamf URL and a basic connection. I'm just talking about for setting up a cloud instance. Since everything will be there in the cloud, you just need the URL, the Jamf cloud URL, and admin credentials. The APNs certificate is required. That allows them to enroll your device. After that, there are so many options; the configuration profile, et cetera, needs to be created. That's a different scenario. However, in general, the setup is fine.
A Mac deployment usually will take three to four minutes. It's quite fast. However, it depends on how you're configuring it. If you have the URL and if you have the username and the password, you can do it immediately.
From the user's end, it will take some time in situations where a user is not familiar with the enrollment process. There'll be follow-ups with the documents. If you are an engineer, it's easy, it's minutes, and it's fast.
How many engineers you need for deployment depends on how big the project is. It depends on the devices. We do have a client where we have around 18,000 devices. For that, currently, we have four engineers and they're easily managing it.
We are a service provider. We support various companies that need assistance with their Microsoft, Macs, et cetera.
Aside from the lack of a reset option, the solution is great and I would recommend it to those using Macs.
I'd rate the solution at a nine out of ten.