Description
This article will go over using the Jamf Protect command line sudo protectctl info -v command, what to look for in this command, and how we can use that information to diagnose the issue.
Important Note: If Terminal returns "command not found," the agent is not installed on the computer.
Use Case
Use this command for general Jamf Protect troubleshooting, including check-in issues, alerts not being sent, and identifying which plan is assigned to the computer (if any).
Steps to Take
On the affected computer, open Terminal.
Run the following command:
sudo protectctl info -vEnter the administrator's password.
Once that command is run, there should be the following output.
Command Analysis
The items below correspond to the Terminal Output items highlighted above.
Connection status: Shows if the agent itself is communicating back with Jamf Protect.
Plan Hash: Shows a long string which will correspond to a plan within Jamf Protect. If we see a 0 this mean there is no plan deployed to the computer. For example in the screenshot below will show how in terminal they correspond.
3. Last checkin: Shows when the computer last checked in with Jamf Protect. We do have another checkin called insights checkin this is referring to the compliance checkin with in Jamf Protect this updates every 24 hours. If we would like to manually force the insights checkin we can run the following Sudo protectctl checkin -i this will update any out of date compliance reports in Jamf Protect.
4. MQTT and HTTP queues: Usually this should display as zero's. If we see a large number this usually indicates a communication issue as there is a lot of data queued up.
Additional Resource
Open source tool called Jamf Check: https://github .com/txhaflaire/JamfCheck