I had similar experience before, re-install self service fixed the issue.
to re-install simply run a script to delete self service and run "sudo jamf policy", it will re-install self service
Terminal saying the Jamf binary is missing means someone removed it, recon is just an argument for the Jamf binary. I suggest making sure /usr/local/jamf/bin/jamf is there, and /Library/Application Support/Jamf as it sounds like this device was either tampered with or not enrolled correctly.
Restoring the Framework will not fix other issues. The reason you are not seeing anything in policy history, is Jamf dumps logs when a policy finishes and the policy is not finishing, so no logs. You can check /var/log/jamf.log and see what is being reported there.
Honestly, with a situation like this I would just reinstall macOS and reenroll the device. The chance of Shanaghan's with this one is really high, I suspect foul play. It's not like Jamf does not tell us where everything is publicly, and a privileged user could just delete stuff
Components Installed on Managed Computers - Jamf Pro Documentation 11.6.0 | Jamf
I had similar experience before, re-install self service fixed the issue.
to re-install simply run a script to delete self service and run "sudo jamf policy", it will re-install self service
Hi A_Collins,
Thank you for your message. I was able to delete Self Service and reinstall as you stated. Unfortunately, it still behaves the same way.
Hi all,
As an FYI, this is looking like security software issue. Thank you for your comments.
