PreStage Packages require a signing certificate which is possibly the
issue that you are experiencing. Here is documentation to assist with
this:
https://learn.jamf.com/en-US/bundle/technical-articles/page/Creating_a_Signing_Certificate_Using_Jamf_Pr...
Run the script in a policy with a frequency you desire but write the
value to a plist. You can store this in /Library/Preferences or wherever
you want. Then setup the EA to read that value
If you have an integration or app (like MUT) that is updating extension
attributes or other various data on the Jamf record, using the API, it
will also update the Last Inventory Update value.In a limited sense, if
you only cared about when the Jamf ...
Having worked in education environments, this is most likely a case
where staff have set the firmware password themselves, left the district
or received a replacement, and nobody knows the password. They aren't
using their MDM to manage the firmware ...
Have 2 policies:Policy 1 is on a custom trigger that simply installs the
packagePolicy 2 is the script that checks for the file. If the file
doesn't exist, then it will execute 'jamf policy -event policy1'----If
you want it to all be in 1 policy then...
