Skip to main content

Hello all, we are seeing a really annoying pop up started on our managed osx devices. A window that says JAMF wants access to our keychain and please enter the password. On my machine I tried the the admin password and my password (I am also an admin) but hither worked.



Any ideas what could cause it? The logs are as below



Fri Nov 08 10:19:28 osx5 jamf[4486]: Failed to submit disk encryption information to the JSS. Will try again later.
Fri Nov 08 10:20:46 osx5 jamf[4845]: Checking for policies triggered by "recurring check-in"...
Fri Nov 08 10:20:47 osx5 jamf[4845]: The management framework will be enforced as soon as all policies are done executing.
Fri Nov 08 10:20:47 osx5 jamf[4845]: Adding launchd task com.jamfsoftware.task.checkForTasks...
Fri Nov 08 10:20:49 osx5 jamf[4919]: Enforcing management framework...
Fri Nov 08 10:20:55 osx5 jamf[4919]: The computer was not enrolled in MDM with the JSS. The device certificate did not install.
Fri Nov 08 10:20:55 osx5 jamf[4919]: Enforcing scheduled tasks...
Fri Nov 08 10:20:55 osx5 jamf[4919]: Removing existing launchd task /Library/LaunchDaemons/com.jamfsoftware.task.1.plist...
Fri Nov 08 10:20:55 osx5 jamf[4919]: Adding launchd task com.jamfsoftware.task.1...
Fri Nov 08 10:20:56 osx5 jamf[4919]: Creating launch daemon...
Fri Nov 08 10:20:56 osx5 jamf[4919]: Creating launch agent...
Fri Nov 08 10:20:56 osx5 jamf[4919]: Existing plug-in, 1.plist, is up to date.
Fri Nov 08 10:21:01 osx5 jamf[4971]: Submitting disk encryption information to the JSS.
Fri Nov 08 10:21:02 osx5 jamf[4971]: Failed to submit disk encryption information to the JSS. Will try again later.

What happens if you perform a sudo jamf enroll command on one of these systems?



Also, what version of the JSS are you running and is this issue happening on a particular version of OS X or multiples?

Hi there, the enroll command doesn't work in 9 by itself, you need to add -prompt, when I do this it still carrys on. I am in discussion in JAMF about this, so will come back if we fix it as well.



Thanks for your ideas

This seems to have been resolved by 9.21, we haven't seen the issue since that update

my environment got bit by this issue today (JSS 9.82) during a mass FileVault rollout project. Clients are trying to submit the FV key and in essence DDOSing my JSS... is anyone else seeing this old issue again?

Terms & ConditionsCookie settings