My previous post didn't complete because the spam bot blocked me, here' a link. @skoonin ]

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

@skoonin You can fix this by either calling /usr/local/bin/jamf instead of just jamf or by adding /usr/local/bin to the path for the user ARD uses.

ARD's PATH environment variables don't appear to include /usr/local/bin. When I ran echo $PATH via ARD's Send Unix command, here are the PATH variables I received back:

/bin:/sbin:/usr/bin:/usr/sbin:/System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Support

To address this, I've added a task template to my copy of ARD:

#!/bin/bash

CheckBinary (){

# Identify location of jamf binary.

jamf_binary=`/usr/bin/which jamf`

 if [[ "$jamf_binary" == "" ]] && [[ -e "/usr/sbin/jamf" ]] && [[ ! -e "/usr/local/bin/jamf" ]]; then
    jamf_binary="/usr/sbin/jamf"
 elif [[ "$jamf_binary" == "" ]] && [[ ! -e "/usr/sbin/jamf" ]] && [[ -e "/usr/local/bin/jamf" ]]; then
    jamf_binary="/usr/local/bin/jamf"
 elif [[ "$jamf_binary" == "" ]] && [[ -e "/usr/sbin/jamf" ]] && [[ -e "/usr/local/bin/jamf" ]]; then
    jamf_binary="/usr/local/bin/jamf"
 fi
}

# Run the CheckBinary function to identify the location
# of the jamf binary for the jamf_binary variable.

CheckBinary

$jamf_binary command_goes_here

The script above contains a function called CheckBinary, which populates a variable named $jamf_binary. The script calls the CheckBinary function before running commands which reference $jamf_binary, in place having to hardcode /usr/sbin/jamf or /usr/local/bin/jamf in the script.

For more information about ARD and task templates, please take a look at the links below:

http://www.peachpit.com/articles/article.aspx?p=606979&seqNum=3

http://www.peachpit.com/articles/article.aspx?p=606978&seqNum=6

It was reported to me that some systems have Self Service broken but the one I looked at later was fine. I'm getting hit with a number of things right now so I've not had a moment to look at the others.

I'm getting reports of ss not working too on 10.10.x too. Ss starts to run a policy, then errors out.

Count me in on the Self Service issue. Thread dedicated to it here: 9.8 Upgrade Self Service Down.

Same here on the Self Service issue. Just opened a ticket with my rep. Quite frustrating.

There is another thread called 9.8 Upgrade Self Service Down. I've stayed with 9.73 thus far. I'm hoping they iron this out for 9.81.

I upgraded my JSS to 9.8 from 9.72 and also upgraded Server.app to 5.0.4 which broke http on port 80 and 443, which in turn broke HTTP installs from Self Service. I disabled HTTP installs and Self Service is working using AFP/SMB. I see other threads stating Server.app 5.x is not being recognized by the installer which prevents JDS install for some people and they have had to revert back to Server.app 4.1.5.

Same http distribution issue, running 9.73. Updated Server.app only to 5.x to see this issue. Ended up rolling back Server.app 4.1.3 to resolve for now.

Oh yes. I should have though to ask which version OS X you were running. Version 5 seems to have broken a large number of things for a wide variety of people, though this last update was supposed to help resolve those. I've happily stayed on 10.9.5 and the associate version 3 server (3.2.2) as it continues to work beautifully while still allowing me to aggregate ethernet ports and assign the bond to the NetBoot service.

So far so good.. except imaging using 9.73 Casper Imaging seems to drop the Adobe Temporary Installer user forever, despite try to use the splash screen fix. When I tried with 9.8 Casper Imaging, it appears to have worked (or I got lucky). Still testing. I know all our techs are going to be THRILLED to have yet another CasperBoot Key! THRILLED!

Addendum: Which will finally motivate me to use Master @rtrouton's scripting mojo from CasperCheck.sh to apply this to the Casper Imaging app on people's boot keys.

Our JSS is running 10.10.5

We also have a problem using Casper Imaging 9.72 with our JSS 9.8. The computer reboots after completing the initial installs (AutoDMG 10.10.3 base image and some third party applications), logs into the Temporary Adobe Installer account, but doesn't install the First Run items and just sits there. Using Casper Imaging 9.8 works fine so I'm updating our NetBoot images, however the release notes state that Casper Imaging v8.6 or later is supposed to work.

@Chris_Hafner I'm currently using a bunch of scripts that point to /usr/bin/jamf. What did you update your scripts to for them to work in 9.81?

Just swap over to /usr/local/bin/jamf (which is the symlink) or the new full path /usr/local/jamf/bin/jamf

There is an example script above that might help you in a more automated fashion.

Do you have to path it out? I normally just put:

#!/bin/sh

jamf recon

as an example. I've never seen it not work and I don't have to re-path it if JAMF moves the binary.

In general that still works for me just fine. However, it's good to be extra specific in your scripts. Other smarter folks can tell all sorts of horror stories as to why it might fail. There have been a few threads pointing out that ARD isn't allowing the jamf command to be called in that manner (jamf recon) and requires the new full path. Otherwise, it should generally work.

P.s. I wonder if that's why the /usr/local/bin/jamf symlink exists. Just to be there if the binary needs to be moved again.

I upgraded from 9.65 to 9.81 and am unable to get computers to boot after imaging if I am putting down a recovery partition for FV with casper imaging 9.81, 9.8, or 9.73.

If I use casper imaging 9.65 the computer reboots to Macintosh HD properly, but is unable to talk to JSS (device signature errors), even when running 9.81 quickadd. I wonder if my old 9.65 quickadd would work.

If I delete the computer before using casper imaging 9.65, computer reboots to Mac HD and the 9.81 quick add runs but machine is stuck in adobe install account. Anyone find a fix for that?

Computers without recovery partition image and reboot fine with Casper Imaging 9.81.

separate post here

Would love any suggestions.

are you using AutoDMG to make your OS images? I have seen issues using InstallESD. I've had no issues with autodmg.

OS images were built with Composer. Casper Imaging 9.81 works consistently for me on images without recovery partitions, but pretty inconsistently on images with one.

Sometimes, after imaging and getting folder with question mark, when I hold down option key the only boot options are EFI/Recovery/Netboot. Other times Macintosh HD is there and I can select it and boot to it, but on next reboot same question mark. Repair disk/permissions isn't helping no matter what the boot options are.

Once in awhile if I delete the computers and choose the config with recovery partition it comes down ok, reboots and works fine. I can't find the pattern of when it works and when it doesn't yet.

not sure if you are using a thin or a fat image, but if it's possible, I would swap out your baseOS with an AutoDMG image, it includes recovery and works much better than composer IMO.

@CasperSally - Sounds to me like the system is getting blessed. I noticed with 9.8, that when I image now, I have to check "Boot to eager drive after imaging" or it doesn't Bless Macintosh HD and I see similar behavior to yours. I never used to check that box, as I like to see it complete before restarting, but with 9.8, I have to.

Are you checking that box when imaging? If not, try it.

@pblake thanks, but we've always checked 'boot to target drive after imaging' - i wish it was that simple.

thanks to everyone who responded. spoke to jamf support and looks like I'm hitting a bug.

Adding this as an after script to configs with recovery partition seems to be working.

bless -mount /Volumes/Macintosh HD -setBoot