Skip to main content
Question

9.8 Upgrade Self Service Down

  • September 18, 2015
  • 65 replies
  • 287 views

Show first post

65 replies

Forum|alt.badge.img+14
  • Contributor
  • September 30, 2015

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


Forum|alt.badge.img+18
  • Valued Contributor
  • September 30, 2015

@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


Forum|alt.badge.img+15
  • Esteemed Contributor
  • September 30, 2015

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.


Forum|alt.badge.img+10
  • Contributor
  • September 30, 2015

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

But I did upgrade from 9.80.


Forum|alt.badge.img+18
  • Valued Contributor
  • September 30, 2015

@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.


Forum|alt.badge.img+5
  • Contributor
  • October 2, 2015

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


Forum|alt.badge.img+4
  • Contributor
  • October 20, 2015

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


Forum|alt.badge.img+18
  • Valued Contributor
  • October 20, 2015

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


Forum|alt.badge.img+11
  • Contributor
  • October 21, 2015

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?


Forum|alt.badge.img+11
  • Contributor
  • October 21, 2015

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


Forum|alt.badge.img+14
  • Contributor
  • October 21, 2015

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


Forum|alt.badge.img+4
  • Contributor
  • October 21, 2015

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


Forum|alt.badge.img+11
  • Contributor
  • October 21, 2015

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


Forum|alt.badge.img+8
  • Contributor
  • October 22, 2015

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?


Forum|alt.badge.img
  • New Contributor
  • December 15, 2015

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