Skip to main content
Solved

Adobe package script error via Self Service.

S
Forum|alt.badge.img+7
  • sirsir
  • Valued Contributor
  • 62 replies

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?

Best answer by lunddal

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.

View original
    Did this topic help you find an answer to your question?

    3 replies

    L
    Forum|alt.badge.img+12
    • lunddal
    • Contributor
    • 64 replies
    • Answer
    • October 6, 2015

    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.

    M
    Forum|alt.badge.img+11
    • mikeh
    • Contributor
    • 82 replies
    • October 6, 2015

    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.

    S
    Forum|alt.badge.img+7
    • sirsir
    • Author
    • Valued Contributor
    • 62 replies
    • October 6, 2015

    Thankfully only our Adobe packages use it. I edited all of them and they are now working.

    Thanks!

    Reply


    Most helpful members this week

    Terms & ConditionsCookie settingsAccessibility statement

    Cookie policy

    We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

     
    Cookie settings