Updating Adobe CC
Hello -
To update to a new version of Adobe CC in the enterprise, Adobe has their tool, the Remote Update Manager.
https://helpx.adobe.com/creative-cloud/packager/using-remote-update-manager.html
Basically, you invoke the tool using a command line script... In my case, from the K1000.
I'm curious if there is anyone out there who is doing this. More specifically, how are you doing it? I could set up a script to run every X minutes, but I'm not sure how to really tell what the progress is, like a MI would. And speaking of MI, I don't know that I could use this because there's not really a "software" associated with this, since the command is just invoking a separate update utility.
Thanks for any ideas you may have.
Carl Sundermann
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
anonymous_9363
9 years ago
I wouldn't let any vendor automatically update anything on my client's estates. In the recent past, Adobe hasn't exactly covered itself in glory with certain releases of their applications!
Posted by:
chucksteel
9 years ago
We push out the Adobe CC updates using a script. This allows us to test them before pushing them to campus, which is why Adobe designed the system this way. Our setup follows:
Create a smart label to find computers with the Remote Update Manager installed:
SELECT MACHINE.NAME AS SYSTEM_NAME, SYSTEM_DESCRIPTION, MACHINE.IP, MACHINE.MAC, MACHINE.ID as TOPIC_ID FROM MACHINE WHERE (((1 in (select 1 from SOFTWARE, MACHINE_SOFTWARE_JT where MACHINE_SOFTWARE_JT.MACHINE_ID = MACHINE.ID AND SOFTWARE.ID = MACHINE_SOFTWARE_JT.SOFTWARE_ID and SOFTWARE.DISPLAY_NAME like '%Remote Update Manager%')) ))
We have two different patching schedules for lab machines vs. staff machines, so I have two smart labels to identify which patching schedule a machine with Adobe RUM is installed:
Adobe Updates - Lab Patching
SELECT MACHINE.NAME AS SYSTEM_NAME, SYSTEM_DESCRIPTION, MACHINE.IP, MACHINE.MAC, MACHINE.ID as TOPIC_ID FROM MACHINE WHERE (((1 in (select 1 from LABEL, MACHINE_LABEL_JT where MACHINE.ID = MACHINE_LABEL_JT.MACHINE_ID AND MACHINE_LABEL_JT.LABEL_ID = LABEL.ID AND LABEL.TYPE <> 'hidden' and LABEL.NAME like '%AdobeRUM%')) ) AND ((1 in (select 1 from LABEL, MACHINE_LABEL_JT where MACHINE.ID = MACHINE_LABEL_JT.MACHINE_ID AND MACHINE_LABEL_JT.LABEL_ID = LABEL.ID AND LABEL.TYPE <> 'hidden' and LABEL.NAME like '%Lab Patching%')) ))
Adobe Updates - Patch Production
SELECT MACHINE.NAME AS SYSTEM_NAME, SYSTEM_DESCRIPTION, MACHINE.IP, MACHINE.MAC, MACHINE.ID as TOPIC_ID FROM MACHINE WHERE (((1 in (select 1 from LABEL, MACHINE_LABEL_JT where MACHINE.ID = MACHINE_LABEL_JT.MACHINE_ID AND MACHINE_LABEL_JT.LABEL_ID = LABEL.ID AND LABEL.TYPE <> 'hidden' and LABEL.NAME like '%AdobeRUM%')) ) AND ((1 in (select 1 from LABEL, MACHINE_LABEL_JT where MACHINE.ID = MACHINE_LABEL_JT.MACHINE_ID AND MACHINE_LABEL_JT.LABEL_ID = LABEL.ID AND LABEL.TYPE <> 'hidden' and LABEL.NAME like '%Patch Production%')) ))
Now that machines are in smart labels according to their patching schedule you can create a script that will launch the Remote Update Manager. The script can be configured to allow the user to snooze in case they are working in a CC application and need to save their work.
The script I have setup targets both MacOS and Windows machines and launches the correct update script bases on OS. There are two dependencies uploaded:
adoberum.cmd:
@echo offecho Changing to Remote Update Manager foldercd %ProgramFiles%\Common Files\Adobe\OOBE_Enterprise\RemoteUpdateManager\echo Launching Remote Update ManagerRemoteUpdateManager.exeecho All done here
adoberum.sh
/usr/sbin/RemoteUpdateManager
cp ~/Library/Logs/RemoteUpdateManager.log /tmp
Different tasks verify the OS and architecture of the system and launch the appropriate script. I then upload the log file to the inventory so that we can troubleshoot any issues.
