JAMF announced today that, due to changes that are coming in OS X 10.11, Casper’s jamf binary will be moving its location in a future release of Casper. For those not familiar with Casper, the jamf binary is the agent software which Casper installs on Macs in order to manage them.
Current location:
/usr/sbin/jamf
Future location:
/usr/local/jamf
From today’s announcement, it also appears that the jamf binary will not be moving on all versions of OS X:
Mac OS X 10.5.x – 10.6: The jamf binary will be staying in /usr/sbin/
Mac OS X 10.7.x and later: The jamf binary will be moving to /usr/local
Now that this information is public, I’m releasing an update to CasperCheck that should be able to handle checking for the Casper agent in both its current and its future locations. For more information, see below the jump.
The change is a new function in CasperCheck named CheckBinary, which will first try to locate the current location of the jamf binary by running the following command:
/usr/bin/which jamf
If the jamf binary can’t be located that way, both /usr/sbin and /usr/local are checked to see if the jamf binary is located in either of those directories.
The updated script is available below. It is also available on CasperCheck’s GitHub repo:
https://github.com/rtrouton/CasperCheck
