After the Jamf binary has been killed, the next scheduled check-in will run correctly. Once Jamf Restart has been deployed to a Mac, it will check if the process for the Jamf binary has been running for more than 1 day, if the Jamf binary has been running for more than a day, it will kill the process. bin/launchctl load /Library/LaunchDaemons/ You can launch the LaunchDaemon with the command The LaunchDaemon and Script can be packaged and deployed via Jamf (a lot easier to do when all Macs are checking-in).

An Extension Attribute (Jamf Restart) that reads the log and displays if the Jamf binary has been killed.

A log file ( /var/log/jamfRestart.log ) that captures that output of the script.

A script (/Library/Scripts/jamfRestart.sh) that checks if the process has been running for 1 day or more.

A Launch Daemon ( /Library/LaunchDaemons/) that will run the script once a day.

Since getting access to a Mac that isn't checking-in is can be somewhat difficult, I have made something I am calling 'Jamf Restart' which lifts ideas and code from CasperCheck and AppProcessKiller. Killing the Jamf binary resolves the issue and the Mac can check-in with the jamf server again. There does not appear to be a time-out for the Jamf binary.ĬasperCheck or the new Jamf-Management-Framework-Redeploy API function do not resolve ths issue.

I suspect this issue is caused by a network interuption when a policy is running or a script within a policy that cannot complete (the softwareupdated process has been hanging on some versions of macOS Big Sur). This policy trigger is already being run: root 88591 0.0 0.0 34245156 1048 ? Ss 21Jul22 0:03.85 /usr/local/jamf/bin/jamf policy -stopConsoleLogs -randomDelaySeconds 300 If you attempt to manually check-in you will get a similar error to: It would appear that the Jamf binary begins its check-in process but never completes, this stops any further check-in attempts as the process is still running and wont attempt to check-in until the original process has completed. This is evident when Macs have run their Inventory Update for 'x days'. I’ve detected an issue where the Jamf binary stops checking in, this can be for hours, days, weeks or even months.

What is jamf binary