Adobe invalid drive updating
But I would much rather download updates internally than to hit an external server and download the same update multiple times.
Ideally we would like to download the updates once then have them available on our network instead of all of our users pinging Adobe for them. @thoule I am using this guide from Adobe https://helpx.adobe.com/creative-cloud/packager/
Please notify your friendly neighborhood Mac Engineer." elif tail -1 /var/log/CC_| grep "(2)" then osascript -e "set Volume 5" say -v Alex "An error type 2 has occurred.
Please notify your friendly neighborhood Mac Engineer." else osascript -e "set Volume 5" say -v Alex "An unknown error may have occurred." fi I setup an internal Adobe Update server a little while ago.
# * Neither the name of the JAMF Software, LLC nor the # names of its contributors may be used to endorse or promote products # derived from this software without specific prior written permission. # # Step 2: Upload the DMG and install PKGfrom script to Casper Admin: # 1. == 0 ]; then log " Package successfully installed." else log "There was an error installing the package. " fi # Unmount the DMG echo "Unmounting disk $mount Device..." hdiutil detach "$mount Device" -force # Delete the DMG /bin/rm /Library/Application\ Support/JAMF/Waiting\ Room/$dmg Name After uploading the script I then added the name of the package in Parameter 4 as instructed: ACCUP50416When running the policy on one of my Macs I am presented with the following error: Would anyone have any idea on how to get this to work or what I am doing wrong?
# # THIS SOFTWARE IS PROVIDED BY JAMF SOFTWARE, LLC "AS IS" AND ANY # EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED # WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE # DISCLAIMED. Thank-you, Anthony) The binary path changed in 9.8 to /usr/local/bin/jamf.
I found it much easier to run a terminal command to update Adobe products than to package the updates up and push them out via a policy!
This script just makes it easier for non-admin users to apply updates themselves with a single click.
Please stand by." # runs the commandline component of the Creative Cloud updater and pipes the output # to the log file as well as standard output so it shows up in jamf logs /usr/local/bin/Remote Update Manager 2&1 | tee -a /var/log/CC_#### this command ONLY checks for updates. If exit code = 0 # then either the updates installed or it is already up to date and the computer will say so. = 0 then a vocal notice will alert the user that something failed.
if tail -1 /var/log/CC_| grep "(0)" then osascript -e "set Volume 4" say -v Alex "Your Creative Cloud programs are up to date" elif tail -1 /var/log/CC_| grep "(1)" then osascript -e "set Volume 5" say -v Alex "An error type 1 has occurred.
# You can choose to put the log file where you want. date /var/log/CC_# appends an informative header to the log file echo "----------------------------------------------- This installation may take 10-15 minutes even though there may not be any signs of activity.
" /var/log/CC_# opens the file with (or whatever is set as the default app for files) open /var/log/CC_# a vocal notice to the user letting them know this may take a while osascript -e "set Volume 3" say -v Alex "This may take a while. # /usr/local/bin/Remote Update Manager --action=list 2&1 | tee -a /var/log/CC_# below checks the last line of the log file for a successful execution.