Just installed 10.11.1 on an iMac and installed Casper 9.81. Tried to run Recon, it logins in, but when I click Enroll, it comes back with:
A connection error occurred: jamf binary failed to install
I can see that it creates the directory /usr/local/jamf as root, but the the directory has nothing in it.
I ran into a similar issue a little while back. I think the problem lies in the fact that the
/usr/local/bin directory does not exist on a fresh image of 10.11. The QuickAdd.pkg will create this directory if required but, I suspect, the Recon.app just tries to create a symbolic link directly into this, non-existant, folder which points back to the actual binaries in
I ran into a similar issue with my automatic re-enroll process, which I use to provision machines. I was creating/downloading the binary to
/usr/local/jamf/bin/jamf, and then relying on the binary to create the symbolic links. That task continually failed until I pre-created the
Working with JAMF support determined that if Recon is set to use HTTP to get the binary it fails. If the preferences are set for SCP it works. I got no solid answer if this was a Casper bug, or an Apple bug or some as yet unknown double secret bug.
I am having the same issue running JSS 9.82 with 10.10.5 clients and 10.11.X clients. Recon Remote Enrollment errors out almost immediately with the error "A connection error occurred: jamf binary failed to install". QuickAdd packages generated from the Recon.app completes enrollment with some errors and QuickAdd packages downloaded from the Web Enrollment Portal work without issue. Unfortunately, our documented process is tied to using the Recon.app for enrollment so our rep's workaround of using QuickAdd packages leaves something to be desired.