You can see it in the URL of the computer record or in the attribute Jamf Pro Computer ID on a computer record in Jamf Pro.Īs long as the computer is online you should see the command run and the computer will go through re-enrollment once the QuickAdd installs. Find the Jamf Pro Computer ID of the computer in this state.If so you can use the new jamf-management-framework API endpoint to reinstall the Jamf management framework (QuickAdd package) automatically and re-establish management with the Jamf Pro server.Ī quick look at how you can use this new feature in Jamf Pro 10.36: You can usually tell this is the case if you check the Management History on a computer record and see commands running successfully.

Jamf Pro accomplishes this by using the InstallEnterpriseApplication command, which means a computer in this state would still need to be receiving and processing MDM commands from your Jamf Pro server. Have you ever had an instance where a computer has lost device trust and when you attempt to run any policies or a recon you get at Device Signature Error? Or someone sends in a ticket that Self Service isn't working and can't connect to the MDM server (due to Device Signature Error)? On 10.36 you now have a way to redeploy the Jamf management framework without having to unenroll and re-enroll a computer. Hot off the presses is Jamf Pro version 10.36, which includes the first iteration of a feature that a lot of admins have been waiting to see for a long time.

What is jamf recon