Jamf Pro

It is an excellent central source for managing our macOS and iOS fleets (we also have some AppleTV units in classrooms that we manage with Jamf). The granularity it provides for configuring and maintaining groups of devices is very powerful. The capability to add custom shell scripts is the best feature, since if you have root access, which you essentially do from Jamf, you can do pretty much anything you need (outside of Apple's framework restrictions). It is fairly straightforward to manage large numbers of endpoints using Jamf Pro.

Scripting is definitely one of the good things about JAMF Integration with ABM works flawlessly

1. Speed of deploying of apps and policies on to the device - takes 10-20s for iOS and less than 15 mins for macOS (depending on the file size). 2. Presence of an on-demand Inventory Update to push the policies without having to wait the usual cycle, whenever necessary. 3. SelfService catalogue which allows apps as well as policies to be present which the user can run whenever required. 4. Patch management for majority of common apps in macOS (apart from Microsoft apps which come with MAU) is available in JAMF App Catalog which helps in robust tracking and monitoring of deployment of latest versions or versions with security updates (w.r.t. Zero-Day Vulnerabilities) 5. LAPS functionality is well-defined with two LAPS admin whose password can gets rotated every hour upon viewing and the LAPS admin works without having to log into it as a local account. 6. Well-developed GUI where most functionalities come in the form of UI and does not need to be achieved by scripts or other roundabout method. 7. Ability to scope/unscope policies and apps based on single devices and not groups.

It can be overly complicated to get certain things done with configuration profiles. The Sites feature initially appears attractive, but actually using it creates a lot of extra work and we ended up with a fair amount of technical debt that we needed to clean up in the move to the cloud service. Learning the API for ad hoc automation and connections to external systems require a fair amount of time and practice.

Product support is definitely something they should upgrade. Some of it's features are broken with a lot of bugs.

1. High cost. 2. No escalation matrix or system of defining criticality of issues when raising a ticket with JAMF support resulting in poor or unsatisfactory customer experience. 3. Apps for macOS are only supported as .pkg. One needs to use the JAMF composer to convert a .dmg file to a .pkg one but a lot of settings get lost during the conversion. 4. No commands of force restart or shut down for macOS. 5. USB restrictions segment removed from JAMF Pro and added to JAMF Protect.