Trying to wrap my head around this. Had a couple of instances with new
Mojave builds where the Jamf agent was called.We already upgraded to JSS
v10.7.1 so it's not the agent requiring access but likely a policy which
needs access and the message is p...
We've experienced this on the odd Mac as well. In my experience it could
be one of several things. FileVault/Secure token not issued correctly
(works to run an authenticated restart), Rosetta and older versions of
Jamf connect (older version of roset...
Would it work to apply FV after the user has logged in?We apply FV via a
config profile on DEP level but, the FV encryption is theoretically
there to protect data and there's no data to protect until the users has
logged in and uses the Mac.So, in th...
Don't think there's an easy way around it. If you are using Filevault
then the first admin account gets the securetoken which is passed on to
subsequent accounts but as you mentioned, you still need to get past the
FV login. Option is possibly to lea...
Is this after the Monterey uprade. I believe you sometimes have to
re-apply the Jamf Connect authentication after major upgrades. We have a
policy that runs this process once (based on Monterey and Jamf Connect
installed) : /usr/local/bin/authchanger...