What is the best way to install Creative Updates? Any Ideas

[jamest]

What is the best way to install Creative Updates? Any Ideas

Should I package it in Composer or is there anything way that it has been done successfully?

[denmoff]

If you are just trying to do point updates and not full version updates, you could use RemoteUpdateManager to update all of the CC apps.

Otherwise, you could use the CCP app to create update only packages for each app.

[jamest]

How can I turn that CCP pkg to a pkg that I can push through Casper? I dragged it to the left sidebar but it isnt allowing me to create the pkg. I feel like I may need to do a normal snapshot then create it as a pkg. Is this correct?

[Josh_Smith]

@jamest

How can I turn that CCP pkg to a pkg that I can push through Casper?

A couple of options:
1. Drag and drop it into Casper Admin, it should get zipped up since it is a non-flat package (assuming you are using a semi current version of Casper) and then you can push it out.
2. If you have trouble with that, as I have in the past with larger CCP packages, then the steps in this KB should work: Deploying PKGs Created with AAMEE or Creative Cloud Packager

I'd be interested to know how many people are using RUM, specifically with an internal Adobe Update Server, and how it is working for them.

PS: Don't try to snapshot it! :)

[AVmcclint]

Oh WOW! I had no idea about RemoteUpdateManager. I'd like to give my non-admin users the power to update their CC apps themselves so I'm thinking of making a Self Service policy that just has this command. The problem I see is that when I run the command myself in Terminal, there is very little feedback to say exactly what it's doing.

RemoteUpdateManager version is : 1.9.2.56 (BuildVersion: 1.9; BuildDate: Wed Nov 04 2015 01:13:06 )
Starting the RemoteUpdateManager...

Following Updates are applicable on the system :
        (AdobeDigitalPublishingCC2015-3.0/2016.2)
        (AdobeDreamweavercc64Bit-16/16.1.2)
        (AdobeInDesignCC2015-11.0/11.3.0.034)
        (PhotoshopCameraRaw8-8.0/9.5.50)

Following Updates are to be downloaded :
        (AdobeDigitalPublishingCC2015-3.0/2016.2)
        (AdobeDreamweavercc64Bit-16/16.1.2)
        (AdobeInDesignCC2015-11.0/11.3.0.034)
        (PhotoshopCameraRaw8-8.0/9.5.50)

All Updates downloaded successfully ...

About 10 minutes of complete silence here.... I had to launch Console and look for the various update logs to see if it was still doing anything - which it was. And then I finally get notice that it's finished.

Following Updates were successfully installed :
        (AdobeDigitalPublishingCC2015-3.0/2016.2)
        (AdobeDreamweavercc64Bit-16/16.1.2)
        (AdobeInDesignCC2015-11.0/11.3.0.034)
        (PhotoshopCameraRaw8-8.0/9.5.50)

RemoteUpdateManager exiting with Return Code (0)

Does anyone know of a way to display this output to the user as it is happening or maybe display something to let the user know that the policy is actually doing something?

[AVmcclint]

And even if there are no updates, I'd like the user to see the output from that too:

RemoteUpdateManager version is : 1.9.2.56 (BuildVersion: 1.9; BuildDate: Wed Nov 04 2015 01:13:06 )
Starting the RemoteUpdateManager...

No new applicable Updates. Seems like all products are up-to-date.
RemoteUpdateManager exiting with Return Code (0)

[dpertschi]

The droids your looking for are in ~/Library/Logs/RemoteUpdateManager.log

[AVmcclint]

Here's what I was able to cobble together. It ain't pretty but so far in my testing it actually works.

(of course I learned that I also have to push out the RemoteUpdateManager file to /usr/local/bin/ for any of it to work.)

#!/bin/sh
# must be run as root or via JSS which runs scripts as root

# creates a log file and starts it off with a date/time stamp
date > /var/log/CC_Update.log

# 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.
Please be patient. If you don't see any activity, click the Reload button above and check 
Self Service to see if the task is still running." >> /var/log/CC_Update.log

# opens the file with Console.app (or whatever is set as the default app for .log files)
open /var/log/CC_Update.log

# 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. 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/RemoteUpdateManager 2>&1 | tee -a /var/log/CC_Update.log

# /usr/local/bin/RemoteUpdateManager --action=list 2>&1 | tee -a /var/log/CC_Update.log
#### this command ONLY checks for updates. It does not actually install anything. Keep this
#### in the script for testing purposes.

# below checks the last line of the log file for a successful execution. If exit code = 0
# then either the updates installed or it is already up to date and the computer will say so. 
# If exit code !=0 then a vocal notice will alert the user that something failed.

if tail -1 /var/log/CC_Update.log | 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_Update.log | grep "(1)"
    then osascript -e "set Volume 5"
     say -v Alex "An error type 1 has occurred. Please notify your friendly neighborhood Mac Engineer."
elif tail -1 /var/log/CC_Update.log | 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

[AVmcclint]

duplicate