Skip to main content

Did an upgrade to 9.8 this morning, seemed to go smoothly.

Got a ticket about Self Service throwing up an error. I checked, and sure enough Self Service is erring out on every computer I tried.
Checked the Console log on the client:

9/18/15 9:09:19.597 AM Self Service[276]: [ERROR] -[JAMFBinaryCommunication notifyThatDaemonIsAbsent] (line:299) --> The daemon is not present

Any ideas? I finally gave up and tried restarting the JSS to no avail. Tried numerous policies in SS, nothing worked.

@Ghanbarzadeh Can you confirm if this issue is still present in 9.81? I didn't see it mentioned in the Release Notes.


@Josh.Smith I have another thread started for reports about 9.81. So far they are positive and are saying the Self Service issue is resolved.

https://jamfnation.jamfsoftware.com/discussion.html?id=17173


I received confirmation from Jamf that this issue is fixed 9.81, even though it was not in the release notes. However, it is not a retroactive fix - meaning machines that were broken with 9.8 will stay broken.


I just upgraded to 9.81 and I am seeing the same thing :(

But I did upgrade from 9.80.


@jgwatson is that for machines that were already broken with 9.8 ? As @cbrewer says machines that were broken with 9.8 will stay broken.


hmm.... Self service will not install my policies (dmg) on machines that have been freshly imaged with 10.11.

Previously enrolled machines that upgraded from 10.10.x -> 10.11 work fine.

.pkg packages install fine on freshly imaged 10.11 machines.
.dmg packages are giving problems on freshly imaged 10.11 machines. Error: An error occurred attempting to mount the package xxxxx.dmg

We are running 9.81


Awesome! This bug made us lose contact with 3 stolen machines.


@apredmore Did that happen because of 9.8 ? or 9.81 ?


We are also trying to fix our fleet with devices that are not checking in with our JSS.

When trying to ARD > Send Unix Command > jamf manage Task Status = "jamf: command: not found"

We also get this status when trying to run this in Apple Script:
do shell script "sudo jamf manage"
"jamf: command: not found"

Can we not jamf manage devices when using SSH?


@kwsenger try using the new full path to the jamf binary already ?


@kwsenger, Try what @lkrasno is suggesting. Specify the full path to the binary (which changed in 9.8.x): /usr/local/bin/jamf.


@rcorbin We lost most of our OSX machines when we upgraded to 9.80


Answer to my own question: Send Unix Command: /usr/local/jamf/bin/jamf manage


I think my clients are re-enrolling themselves :(

Most of them seem to be stuck in a loop The management framework will be enforced once policies are done

They show this error when the check for policies triggered by enrollment takes place:

* - [NSPlaceholderString initWithString:]: nil argument

Then, they get stuck in the above loop. Can anyone offer any advice?


Just had this issue with one of my users.
But it was not caused by upgrading to 9.8, it was caused because the user disabled the jamf daemon service.
After I ran the command sudo launchcth load -w /Library/LaunchDaemons/com.jamfsoftware.jamf.daemon.plist issue was resolved