Posted on 07-19-2018 09:04 AM
When JAMF quickadd is run, its script symlinks /usr/local/bin -> /usr/local/jamf/bin/jamf
This causes an issue when installing popular scripts such as brew (homebrew) which appears to rely on usr/local/bin being a directory, not a symlinked path. ie you get the following error:
mkdir: /usr/local/bin: Not a directory
Failed during: /usr/bin/sudo /bin/mkdir -p /usr/local/bin
since bin is symlinked to bin@ -> /usr/local/jamf/bin/jamf
(btw, yes, PATH doesn't follow symlinks)
Posted on 07-19-2018 09:26 AM
This is a known bug as of 10.4 (PI-005852).
Posted on 07-19-2018 10:39 AM
Dealing with the same issue right now with version 10.4.1.
Lots of dev tools (e.g. docker, aws, git) rely on /usr/local/bin, so this is a big issue for me.
This is a good link for more discussion on this issue:
I'm implementing the enrollment script from this post: https://www.jamf.com/jamf-nation/discussions/28097/jamf-pro-10-4-and-quick-add-package-bug#responseC...
Posted on 07-23-2018 06:52 PM
Any way we can ping JAMF to address this in next patch fix? Can only imagine every developer and engineer w/quickadd is reeling in agony trying to fix this w/out knowing there's a script you have to run to fix JAMF's issue. Already filed a support ticket but no ETA on fix.
Posted on 07-24-2018 08:03 AM
Posted on 07-25-2018 01:37 PM
Im happy to report it appears to be fixed in 10.6.0. It also appears that as of today it didn't make the release notes but I can confirm the missing mkdir line has been added to recon in 10.6.0 so new quickadds will have it. I've also pinged support to hopefully update 10.6.0's release notes page accordingly so we can see the end of PI-005852
Posted on 07-27-2018 08:48 AM
and the release notes have now been updated to reflect the change. yay! http://docs.jamf.com/10.6.0/jamf-pro/release-notes/Bug_Fixes_and_Enhancements.html
Posted on 07-30-2018 07:58 AM
What would the workaround be for machines that we have already used 10.5 QuickAdd to enroll? I have a lot of machines that are now reporting the symlink issue but I'm not sure what to do to remedy them. Any help is greatly appreciated!
Posted on 07-30-2018 08:29 AM
Posted on 07-30-2018 08:31 AM
@bpavlov I upgraded my client software to 10.6 but since I am cloud I don't know if I just need to wait for my instance to update to 10.6 or what is needed. I apologize if this sounds weird, I'm new to Jamf and literally just finished enrolling a bunch of devices.
Posted on 07-30-2018 08:38 AM
@kricotta the fix is in the 10.6 of Recon so you'll need to rebuild your quickadd pkgs. I asked same question about machines in field here that had old quickadd/sym link issues and they said to run the fix script on all machines. I haven't rolled that out yet but it appears pretty simple.
Curious how others are tracking which machines have fix and who doesn't, maybe its a moot issue if you just apply to all.
Posted on 07-30-2018 08:45 AM
I've tried the fix script as well. I can't push it via Jamf as, well it is broken and won't check in. However, I did manually run it on a machine having the issue and still no love. I'm calling support now.
Posted on 07-30-2018 08:55 AM
Posted on 07-30-2018 09:01 AM
Support is upgrading me to 10.6 cloud instance (apparently I was not scheduled until August 4th for the update). So I will report back if the 10.6 upgrade and new QuickAdd package fixes the issue.
Posted on 07-30-2018 09:42 AM
Ok, I have been upgraded on the backend to 10.6. However, it doesn't appear to have done anything. The Fix Script didn't work either. I created a new 10.6 QuickAdd and also, no improvement. I then tried manually removing anything Jamf off the machine, profiles etc. The magic combination seems to be the following (nothing else needed to be removed).
Run these commands on affected machine:
sudo rm -rf /usr/local/jamf/bin/jamf sudo rm -rf /usr/local/jamf/bin/jamfAgent
Then run Recon - Remote Enrollment to install package and re-link. NOTE: I am swearing off using QuickAdd packages now in favor of remote push where possible.
Posted on 07-30-2018 04:04 PM
So to follow-up again. This apparently isn't fixed and it's back to the drawing board.
Posted on 08-02-2018 02:54 PM
Posted on 08-03-2018 06:38 AM
Hello @kricotta, sorry to hear you are still having problems with this workflow. If you are still having issues with it, could you reach out to and work with support so we can learn more about why it's not working in your case?