Adobe invalid drive updating

06-Sep-2019 19:22

/bin/sh #################################################################################################### # # Copyright (c) 2011, JAMF Software, LLC. # # Redistribution and use in source and binary forms, with or without # modification, are permitted provided that the following conditions are met: # * Redistributions of source code must retain the above copyright # notice, this list of conditions and the following disclaimer. # # Step 3: Create a policy to install the DMG: # 1. = "" ] && [ "$dmg Name" == "" ]; then dmg Name="" fi #################################################################################################### # # LOGGING FUNCTION # #################################################################################################### log () #################################################################################################### # # VARIABLE VERIFICATION FUNCTION # #################################################################################################### verify Variable () #################################################################################################### # # SCRIPT CONTENTS - DO NOT MODIFY BELOW THIS LINE # #################################################################################################### # Verify Variables verify Variable dmg Name # Mount the DMG log "Mounting the DMG $dmg Name..." mount Result=`/usr/bin/hdiutil mount -private -noautoopen -noverify /Library/Application\ Support/JAMF/Waiting\ Room/$dmg Name -shadow` mount Volume=`echo "$mount Result" | grep Volumes | awk ''` mount Device=`echo "$mount Result" | grep disk | head -1 | awk ''` if [ $?

# * Redistributions in binary form must reproduce the above copyright # notice, this list of conditions and the following disclaimer in the # documentation and/or other materials provided with the distribution. Choose a location for the package and then click Save. Drag the DMG you created in the previous procedure to the Package pane in Casper Admin. Drag the install PKGfrom script to the Package pane in Casper Admin. == 0 ]; then log " DMG mounted successfully as volume $mount Volume on device $mount Device." else log "There was an error mounting the DMG. " fi # Find the PKG in the DMG package Name=`ls $mount Volume | grep "pkg"` # Install the PKG wrapped inside the DMG log "Installing Package $package Name from mount path $mount Volume..." /usr/sbin/jamf install -path $mount Volume -package $package Name if [ $?

But I would much rather download updates internally than to hit an external server and download the same update multiple times.

The script assumes that # the DMG has been previously cached to the machine to: # # /Library/Application Support/JAMF/Waiting Room/ # # This is the default location that a package will be cached to when selecting the "Cache" # option within a policy or Casper Remote. I even called and spoke with Adobe on configuring the server and the technician informed me that enterprise users are not even using the local server for whatever reason. I've been using Remote Update Manager via a script I wrote and put in Self Service and even though it isn't perfect, it isn't bad.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.IN NO EVENT SHALL JAMF SOFTWARE, LLC BE LIABLE FOR ANY # DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES # (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; # LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND # ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT # (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS # SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. I haven't been admining long enough to know the real woes of the pkg from dmg issues, but as of the current CC apps, I've not had any issues with the Creative Cloud Repackager, Since the change of all the binary paths are wrong in the script then.# ##################################################################################################### # # SUPPORT FOR THIS PROGRAM # # This program is distributed "as is" by JAMF Software, LLC's Resource Kit team. I will try to change them and re-upload the script to see if that makes a difference. How are you deploying CC updates after using Creative Cloud Packager to package the updates from Adobe?

The script assumes that # the DMG has been previously cached to the machine to: # # /Library/Application Support/JAMF/Waiting Room/ # # This is the default location that a package will be cached to when selecting the "Cache" # option within a policy or Casper Remote. I even called and spoke with Adobe on configuring the server and the technician informed me that enterprise users are not even using the local server for whatever reason. I've been using Remote Update Manager via a script I wrote and put in Self Service and even though it isn't perfect, it isn't bad.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.IN NO EVENT SHALL JAMF SOFTWARE, LLC BE LIABLE FOR ANY # DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES # (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; # LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND # ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT # (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS # SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. I haven't been admining long enough to know the real woes of the pkg from dmg issues, but as of the current CC apps, I've not had any issues with the Creative Cloud Repackager, Since the change of all the binary paths are wrong in the script then.# ##################################################################################################### # # SUPPORT FOR THIS PROGRAM # # This program is distributed "as is" by JAMF Software, LLC's Resource Kit team. I will try to change them and re-upload the script to see if that makes a difference. How are you deploying CC updates after using Creative Cloud Packager to package the updates from Adobe? # Note: You must enter the exact name of the PKG in the Parameter 4 field. # #################################################################################################### # # HISTORY # # Version: 1.0 # # - Created by Nick Amundsen on July 22, 2011 # #################################################################################################### # # DEFINE VARIABLES & READ IN PARAMETERS # ##################################################################################################### # # HARDCODED VALUES SET HERE # # Variables set by Casper - To manually override, remove the comment for the given variable # target Drive="" # Casper will pass this parameter as "Target Drive" if left commented out # computer Name="" # Casper will pass this parameter as "Computer Name" if left commented out # user Name="" # Casper will pass this parameter as "User Name" if left commented out.