Jamf Pro Reviews

We use Jamf for zero-touch deployment and handling our customers' hardware and licenses. We use it for all the things you use device management or enterprise mobility management systems for, but it's not an inventory in our case. We use it mainly for zero-touch deployment with customers who operate worldwide and the headquarters can be in Sweden, England, or Germany, but the users are all over the world. 

Jamf Pro is the only product we can use at the moment because they are ahead of their competitors in zero-touch deployment for the end-user. Jamf Pro has a self-service feature that has helped us minimize our support cases. That's a feature the customers like very much.

I'd like to see Jamf add Unified Endpoint Management, but it's not going to happen. It's too complex. We tried that for so many years, and no one can do this for Windows and macOS. It can be done with iOS, but that's not the case here. If you want device management for a real laptop operating system, you need two systems. They're very different.

I've been using Jamf Pro for nearly seven years.

The cloud version of Jamf Pro is extremely stable.

Jamf Pro is scalable. We have upwards of 50 customers, one of which has 200,000 users, and it's working, but our largest deployment is about 12,000 users. 

Level 3 support is okay, according to what I hear from that department. When it's a level 3 question, no one expects that we will have the answer in one or two days, but sometimes it can take one or two weeks or even a few months. Generally speaking, we get the support we need. 

We've worked with Intune. It's much harder and takes more time to provide the same level of customer experience with Intune that we can offer with Jamf Pro. We can do a lot more scripting for the end-user with Jamf Pro than we can do with Intune, and it takes more time.

For someone who's familiar with device management and designing this type of environment, I wouldn't say it's hard to set up Jamf. It can take anywhere between two days and one month, but that depends on the type and size of the customer. 

We've been in deployment for about 12 years, and we used open-source products initially, but now we need zero-day support for Apple, and the only good product we have found is Jamf. All others have been good for one or two years, but they stop delivering and maybe disappear. 

Jamf is still there after all these years, and they continue to improve the product. With Intune, Microsoft decided not to offer device management for the macOS. Instead, they chose to have Intune integrate with Jamf. 

We need remote hardware and software management. We are a half on-site half offsite workforce over two office locations. We need to be able to deploy hardware and software catered to each department at a quick pace. Jamf works perfectly for this. 

The ability to script executions of CLI-based solutions is second to none.

We needed an MDM solution that would meet our InfoSec needs on data/hardware/software deployment. We also needed a way to revoke the same data/hardware/software if required.

Jamf filled all of these needs.

The solution allowed software deployment without having to use admin credentials and remote control sessions. Jamf cut the time it takes to deploy a new machine to a new user. We are able to group departments quickly and deploy the correct work environment every time.

Jamf also keeps a store and list of our available software titles that the end-user can choose from if needed. Once they find the title they need they can download and install it on their own without creating a ticket with the IT department. This saves us a lot of time.

The self-service portal and auto-enroll are great.

Self-service has reduced the number of your support tickets incredibly. End users are able to search for and find available and approved software and download and install it themselves. This has saved time for both the end-user and the IT department.

Auto enroll is a fantastic feature integrated into the system. We buy direct from Apple. Once purchased they are entered automatically into our auto-deploy script. It keeps our equipment safe and reduces the time from Box to EU.

An easier way to deploy Full OS upgrades would be a great start. For use to deploy Big Sur we needed a bunch of scripts and two different ways to deploy. Once Monterey came out our script no longer worked. If Jamf could work with Apple to get the App Store deployment of the OS upgrades to work that would be great.

Another feature that would be great would be a way for an App Store Application deployed by self-service to be forced to update to the latest on the App Store. Many apps, especially Office, lag behind and an uninstall and reinstall is required to fix the issue.

They need to scale the self-service header.

I've used the solution for six years.

I have not had one problem using the Jamf Cloud solution.

It scales well.

Support has been great for the few times I had to use them. They offer a very quick response. 

Positive

We did not use a previous solution. We imaged all the machines.

We used a kickstart consultant.

The vendor we used was very capable.

I'm IT. I don't concern myself with ROI. My concern is keeping the company running. Cost is a factor, however, uptime is more important.

The cost is average. The setup is not that bad. We used one of Jamf's quick kickstart consultants to get us going.

I had used Jamf at a previous job so brought it over.

I'd advise potential users to just get it if you manage Apple Devices.

I use Jamf Pro to deploy software on my computers in our school and manage them.

Jamf Pro has improved my organization because I can have all my computers up to date on certain software, and it's very convenient for me.

I have found the most valuable feature to be the policies.

 I think there's room for improvement on the automation. For example, uploading a package to Jamf Pro and then updating the policy and other aspects, should be automatic. For instance, if I put a new version of the software, version 11 and the previous one was 10, Jamf Pro should be able to recognize if there's an update and update the policy automatically. It's not a big deal, but I think there's room for improvement.

There are a few additional features I am looking for in the next release. There should be a better way to implement malware protection. I know that Jamf is selling a product to do it, but I think a large part of it can be maintained directly inside the MDM without more cost. I think buying another software to protect the computer is a bit abusive. For instance, most of it can be done by running a script. It should be implemented in a better way.

I have been using Jamf Pro for a year and a half.

Jamf Pro is highly stable. I have never had a day of downtime since I have been using it.

I have found Yannick Jamf Pro to be scalable. I can work with a very small group of computers or I can update 500 of them in a few minutes.

We have approximately 500 people using the solution and they are mainly teachers.

I use it every day and I update the software once a week. Friday is a big day for me for the usage of the solution and for the rest of the time, it's only small maintenance or emergency operations that I use once in a while. Every day I check in if I've had issues or I check the logs for problems with deployments, and so on. I check it all the time, even when I'm not working, I check it on my phone. It's very convenient.

I have never had the need to use technical support. If I have an issue, I go to the website Jamf Nation, which is a community of Jamf users and I usually I find my solution there.

I have used two different solutions previously to Jamf Pro, which were MDM and FileWave. There was a third solution we were using but we had to remove it because it was bought by another software company, and it turned into abandonware. I had to look for another solution because all three that I used previously were not good solutions. Jamf Pro was a good solution.

The installation was very easy. It was done by the software company which I work with. The implementation took one day.

We used an integrator for the implementation and my experience with them was great.

I do the maintenance and support of the solution in my organization.

I did evaluate many other solutions from different vendors. There were approximately six or seven of them. The closest one I found that met my needs was not even close to matching the useability of Jamf Pro. Jamf Pro is very focused on the Mac system, which gives it a large advantage over the competition.

I would recommend those wanting to use this solution to try out the on-premise trial version to see how it works and how you can use it to do deployments. I tried it and it was a real eyeopener. The trial is very good and done well.

I rate Jamf Pro a nine out of ten.

As an organization, we are resellers, we provide services to our clients, and we work on various government and manufacturing projects.

We provide consultancy, as well as our services for both Jamf Pro and Apple products.

We also offer assistance if they encounter any problems with the integration of Apple products.

When I first started using this product, there were a couple of features that still excite me because there was no scope to address those issues. And these features completely eliminate some of our previous issues.

I am most excited about a feature that is called User-Initialed Enrollment.

I also like the Composer feature, which is a unique feature.

Snapshot is one of the tools that allows any package, container, or package creator to find a way to work with various applications. 

I really liked the Self Service applications as well. It is very convenient and useful.

The response time for support could be significantly improved.

I have some customers who are struggling to get a response.

The amount of time required for remediation is also a challenge. If the problem is identified on the first call, it should be tagged and resolved within the tag. This is something we have been dealing with, as well as a problem that some of our clients have encountered.

The cost could be lower.

I've been working with Jamf Pro for five years. I received my Jamf certification in 2017 and have been using it ever since.

Jamf Pro has been stable.

Jamf Pro is a product that can be scaled. Scalability is something that must and should exist, and I always believe in possibilities.

At the moment, the way the product is designed for managing Apple devices meets my needs.

When I need to scale it in the future, I know it's a possibility.

Support is something I believe could have been improved.

They offer one of the best cloud services available.

However, the response time and remediation could have been significantly improved.

Prior to Jamf Pro, I worked with three different products: SOTI, MaaS360, and VMware Workspace ONE.

The initial setup is quite simple. It is not at all complicated.

It is extremely simple for any user from an endpoint and an administrator's perspective.

It would be beneficial if it could be reduced slightly.

The price for these products is designed in such a way that I believe it is a little on the high side.

They are really evolving, and there have been a lot of improvements since 2017. I like the changes that have been made.

It is now designed in such a way that it can serve the needs of any organization. I have not encountered any issues where I felt it could have been significantly improved, and a specific feature could have greatly aided in addressing issues. So far, everything is running smoothly.

It is recommended for any of our organizations. Jamf Pro is superior to MDM on an Apple platform. If you put Jamf into context and you only want to manage Apple, I believe this is one of the best options.

It can be argued that the fact that it only supports Apple is either an advantage or a disadvantage.

Jamf is your go-to solution for managing your Apple Suite. You should investigate and deploy this product.

I would rate Jamf Pro a nine out of ten.

We're moving from on-prem to cloud. It's a significant improvement because our previous on-prem solution for the Apple Mac we quite frail. But the kits we're using were out of warranty, so we were looking for a cloud solution that's easy to manage and partner up with.

For me, the most helpful feature is Jamf's smart groups. I also like the capabilities of the small groups because it gives you a nicer, cleaner, more polished view of your dashboard, and the dashboard is a lot more customizable for an administrator than Workspace ONE. With Workspace ONE, you have to navigate, and it isn't easy to articulate to leadership what it means if you're a non-technical person.

I would like to see Jamf add more training tutorials and documentation.

Jamf Pro, we just bought our own instance about three months ago, and for the last six months, I've been upskilling myself in that space. I think I'm convincing my colleague to reconsider our setup. At work, we use scanners in Workspace ONE because I know that Apigee also offers quite a bit of technology around that space as well.

Jamf is far more stable than Workspace ONE.

I think Jamf is definitely scalable. 

My experience with Jamf support has been quite seamless. When you load a ticket, you get support immediately.

Installing Jamf is pretty easy once you understand how DEP works and how to enroll devices. Zero-touch because we were aiming for a zero-touch environment, and it's entirely in the cloud. I'm not an expert in Jamf yet— I'm still learning— but for me, it was a lot easier to understand than Workspace ONE. Navigation is straightforward. It's not hard to create policies and manage the device. It's a lot simpler to create smart groups, view inventory, and see what the estate looks like. Jamf makes it easier to create a roadmap by giving me that view of where we need to be.

Jamf is quite up there. It wasn't the cheapest solution, but it's reasonable.  Apigee was cheaper than Jamf.

We were looking to put our Apple environment in Workspace ONE, and it didn't work well. It worked when we tried SCCM, but it wasn't something we were fond of based on who our partners were. So we looked at Parallels as well. 

I would rate Jamf nine out of 10.

Initially, Jamf Pro was primarily used to manage our all-Mac computer lab classrooms for one of our departments. Jamf Pro replaced a mix of DeployStudio, Munki, WorkGroupManager, and a couple of other antiquated tools which I'm sure I'm forgetting.  

Having one solution which replaced all those other moving parts has been a godsend. We are now expanding to managing individual faculty/staff Macs as well. It's going to be a bit of a process, but I'm excited to have Jamf Pro managing more and more of our assets.

Jamf Pro allows us to maintain an updated and consistent user experience in our classrooms while reducing the hands-on time required from our techs. Long gone are the days of running around (or even manually logging in via ARD) to update our classroom systems.

Jamf Pro is also helping our techs to more efficiently deploy new Macs to faculty and staff.  This is also a boon for security, as faculty and staff no longer need to have a secondary account for admin purposes - or worse, run as admin day-to-day.

Being able to easily deploy apps and patches to our client computers with minimal hands-on time from our techs has been huge. Being able to choose which apps and patches are deployed to which computer groups allows me to easily test on one batch of computers before pushing them out to the rest of our fleet.

The inventory reporting is also much more thorough than other solutions which just don't play nicely - or at least as nicely as they could/should - with Macs.  Due to the fact that it's all in the same system, we can get pretty granular about which apps/patches get pushed out to which hardware sets (Intel vs. M1, for example).

It would be nice if there was a built-in means of renaming computers that worked reliably.  This is a common problem I've heard many other Mac admins wish for as well.  

While Jamf Pro *can* rename computers, there are weird priorities based on when the computers check-in that can overwrite the desired name - particularly if your organization does not use any of the rather limited naming conventions that Jamf *can* recognize. Manually naming computers is one thing our techs still have to do. It's not a deal-breaker, but not ideal.

I've used the solution for about four years now.

We use Jamf Pro to automate device management.

The solution has good integration with Google and has high performance for our Mac fleet of devices.

Jamf Pro currently is only used on Mac computers and could improve by having compatibility with other operating systems. We have to use other tools to manage our Windows and Android devices. There could be other improvements but I am still exploring and learning more about the features.

I have been using Jamf Pro for a couple of months.

The solution is stable.

Jamf Pro is scalable.

The technical support from Jamf Pro is amazing.

We previously used different solutions.

The installation was complex. 

We used the help from an implementation consultant team and we went through Jamf's 200 and 300 courses. The courses took one week to complete and an additional four weeks to complete the communication process.

The price of this solution is a bit high but it is worth the money for the features. 

There is an annual license for the use of this solution.

My advice to those wanting to implement Jamf Pro is the process to implement the solution takes a while. You have to go through Jamf 200 and 300 courses first to be able to understand the solution.

I rate Jamf Pro a ten out of ten.

Our primary use case is automated enrollment for clients. We use Apple Business Manager and leverage it for new computers. For existing computers, I created an automated enrollment process, enlisting machines that can remotely wipe and re-install the OS and bring down the entire suite of applications on enrollment, which is very powerful.

A good use case would be the end-user experience. The end-users are excited and happy that they're able to be more productive because they're able to access approved applications and self-service. They're able to submit tickets to the help desk, in which, if they need an application approved, it'll go through an approval process.

Anything outside of the core application suite, you'd have to get approval. At the same time, they like the aspect of being streamlined like that.

Overall, it's quite helpful and productive.

I found that automated enrollment is very powerful because you can bring standardization to the environment. 

The restrictions are very powerful because you can block new OS releases, so you can vet them to make sure they're not going to break any legacy applications. That's very useful and powerful.

The ability to leverage self-service for a better end-user customer experience. You can categorize it to different aspects of your organization, be it HR, creative department, or legal, whatever you like.

The reporting needs to be improved so that generating them is more user-friendly. The reporting should have more of a graphical interface. For example, if you want to create a report on how many computers have been checked in the past 30 days you can produce it. However, it is not something that you'd like to give to a CIO.

It will export data into a spreadsheet, but executives don't want to look at spreadsheets. Rather, they want to look at bar graphs, charts, and visuals with percentages.

The prices are expensive and should be reduced.

When we paid for training, we could not have all five people training at one time. I thought that if we were paying $18,000 USD then we could have everybody training at once. However, this is not the case and it doesn't make sense to me.

The response time for technical support could be better.

I have been using Jamf since 2009 or 2010, with version 8.6.

Jamf is very stable. They have a 99.9% uptime in the cloud, and I use it on a daily basis. I would say that it's very robust.

This product scales very well. There's a great use case from IBM that shows how they scaled in that environment. They bought 100,000 Macs and it scaled out very well. I've used it myself when I went from zero to over 600 computers in less than six months.

At this point, we're just implementing it with our clients. The Mac footprint is perhaps 500 end-users, total. We're planning to grow the environment and we're going to use Jamf to do it.

I would rate their technical support a nine out of ten. They are good, although the response time could be better.

I have always used Jamf, and start with version 8.6 in 2009 or 2010. At that time, there wasn't really another similar solution.

If you're using a cloud-based deployment then it is straightforward and Jamf will spin that up for you. If you're on-premises then it's a $6,000 USD on-site visit. A technician will come on-site and spin up the on-premises solution for you. An on-premises version is primarily used by federal government agencies, more often than commercial agencies. Commercial agencies usually move to the cloud.

The IT staff, including myself and several other individuals, are the ones who operate Jamf from an administrative perspective.

This is an expensive solution.

The price of a training pass for five people was $18,000 USD.

My advice for anybody who is implementing Jamf is to get the cloud version first and immerse yourself in it. The key is to always look at the admin guide, which can be very helpful. I would also suggest leveraging Google because if you search for Jamf Pro, there are a lot of videos where they show you how to do certain implementations. In summary, I would say that the best thing is to do your research.

I would rate this solution a nine out of ten.