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: [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.
Correct, and that's where the real hurt is.
Machines actually responds to Casper Admin, so, right now we are pushing a recon with an EA that checks for that file.
That only works if the computers are reachable and all the laptops spread around the world will not be easy to assess. I'm guessing, next week we'll send an email to people who we have no update from and ask them to run something from Self Service. If that fails, we know they need the fix.
Still, since most of our users aren't admins, that means we have to find a way to apply the fix...
Yes, we are planning on doing that, but there is no way to nicely ask the users to restart, other than using phone or email. It's not possible to use the jamf binary to restart nicely, it doesn't work in the state things are, the screen only flickers.
You could run a script command to send up a jamfHelper dialog explaining they must restart. Or cocoaDialog if you have that installed. Yes, its more commands you need to run, but it might be better/faster than getting on the phone with every user.
All I can is I'm very glad we decided to wait on upgrading our JSS to 9.8. We didn't see the need since it was mostly to support iOS 9, and we don't manage iOS devices with Casper here. Patiently waiting for 9.81 to see if this is resolved. Honestly, I know bugs happen, but a bug like this is very troubling and not acceptable in my opinion.
There are a million ways to tell the user to restart, the number one problem is to get to the computers! As long as they are here at the uni, no problem, but so far we have made contact with 284 out of 906 computers :(
254 with working recurring and 30 without.
To follow up on @kstrick , I've got a post discussing the updated script available here:
Latest rev of CasperCheck is available from here:
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.
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
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?
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