Issue when updating jamf binary during re-enrollment

josh-the-tech
New Contributor

Hi,

Unfortunately recently we have had issues with our JSS that resulted in us downgrading to 9.65 and then finally back up to the latest version 9.81. However all of our Macs that have the 9.65 jamf binary don't seem to update. When doing a policy check in, this is the output (I've tried this on a number of Macs)

jamf policy -verbose
 verbose: Checking for an existing instance of this application...
Checking for policies triggered by "recurring check-in"...
 verbose: Checking for active ethernet connection...
 verbose: No active ethernet connection found...
 verbose: The Management Framework Settings are up to date.
Upgrading jamf binary...
 verbose: Upgrading version 9.65 to version 9.81
The management framework will be enforced as soon as all policies are done executing.
No policies were found for the "recurring check-in" trigger.
 verbose: Removing any cached policies for this trigger.
 verbose: Creating task checkForTasks...
 verbose: Adding launchd task com.jamfsoftware.task.checkForTasks...

The binary doesn't actually update. Following this, I run the enrolment to force it that way but then I get the following output and error. We're not sure what this last error is being caused by. (Edited output to remove URLs)

Downloading required CA Certificate(s)...
This computer was successfully enrolled to the JSS with the following device certificate: "71BAEB88-2995-5AB2-A041-D322D8889462"
Retrieving inventory preferences from https://our.jss/...
Locating applications...
Locating accounts...
Locating package receipts...
Finding extension attributes...
Searching path: /Applications
Locating hard drive information...
Locating software updates...
Locating printers...
Locating hardware information (Mac OS X 10.10.5)...
Gathering application usage information...
Submitting data to https://our.jss/...
<computer_id>910</computer_id>
Getting management framework from the JSS...
Enforcing management framework...
Checking availability of https://our.jss/...
The JSS is available.
Enforcing login/logout hooks...
Enforcing scheduled tasks...
Creating launch daemon...
Creating launch agent...
Checking availability of https://our.jss/...
The JSS is available.
Checking for policies triggered by enrollmentComplete

There was an error.

     *** -[NSConcreteTask terminationStatus]: task not launched

It's this error that's stumping us. I couldn't find anything relating to it for the jamf binary when I did a little Google of it.

The way we're working around it at the moment is manual QuickAdd package enrolment but would like to avoid this for every machine if possible and do not want to re-image either.

Thanks in advance.

0 REPLIES 0