- Jamf Nation Community
- Products
- Jamf Pro
- Re: Adobe package script error via Self Service.
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 10-06-2015 05:50 AM
When installing a Adobe PS package via Self Service, I'm getting this error:
Running JSS version 9.8.
Executing Policy HS Adobe Photoshop CS6 Install 2015-16... [STEP 1 of 3] Mounting Main Distribution Point to /Volumes/CasperShare... [STEP 2 of 3] Caching package Adobe_HS_PS_2014-15_Install.dmg... [STEP 3 of 3] Running script installPKGfromDMG.sh... Script exit code: 0 Script result: Variable "dmgName" value is set to: Adobe_HS_PS_2014-15_Install.dmg Mounting the DMG Adobe_HS_PS_2014-15_Install.dmg... DMG mounted successfully as volume /Volumes/Adobe_HS_PhotoShop_2014-15_Install on device /dev/disk1. Installing Package Adobe_HS_PhotoShop_2014-15_Install.pkg from mount path /Volumes/Adobe_HS_PhotoShop_2014-15_Install... /Library/Application Support/JAMF/tmp/installPKGfromDMG.sh: line 169: /usr/sbin/jamf: No such file or directory There was an error installing the package. Exit Code: 1 Unmounting disk /dev/disk1... "disk1" unmounted. "disk1" ejected.
What's causing this error?
Solved! Go to Solution.
2 ACCEPTED SOLUTIONS
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 10-06-2015 06:47 AM
The jamf binary has been moved from /usr/sbin/jamf to /usr/local/jamf/bin/jamf
Edit the line with the path to the jamf binary in the installPKGfromDMG.sh script.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 10-06-2015 06:52 AM
It appears to be that the installPKGfromDMG.sh script itself is hard-coded to expect the jamf binary to be located in /usr/sbin. However, with the release of Casper 9.8 and for El Capitan compatibility, the location of the jamf binary moved to somewhere underneath /usr/local/. The script will have to be altered to account for the binary's move. The might be as simple as changing all instances of /usr/sbin/jamf to /usr/local/*/jamf.
Good luck; you might be in for a lot of work if you use the script a lot.
3 REPLIES 3
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 10-06-2015 06:47 AM
The jamf binary has been moved from /usr/sbin/jamf to /usr/local/jamf/bin/jamf
Edit the line with the path to the jamf binary in the installPKGfromDMG.sh script.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 10-06-2015 06:52 AM
It appears to be that the installPKGfromDMG.sh script itself is hard-coded to expect the jamf binary to be located in /usr/sbin. However, with the release of Casper 9.8 and for El Capitan compatibility, the location of the jamf binary moved to somewhere underneath /usr/local/. The script will have to be altered to account for the binary's move. The might be as simple as changing all instances of /usr/sbin/jamf to /usr/local/*/jamf.
Good luck; you might be in for a lot of work if you use the script a lot.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 10-06-2015 07:47 AM
Thankfully only our Adobe packages use it. I edited all of them and they are now working.
Thanks!
