Scenario: I need to figure out how to run the
/usr/local/bin/RemoteUpdateManager at DeepFreeze maintenance cycle. During this maintenance cycle, the computers will restart to the login screen and enter a thaw and locked mode for a period of time. As mentioned we do not have a MDM yet, so I created a launch daemon which to my understanding should run the script at boot without requiring any input or to login.
#!/bin/bash rum=/usr/local/bin/RemoteUpdateManager if [[ -f $rum ]]; then echo "Starting Adobe RemoteUpdateManger..." sudo $rum --action=list #Listing the updates for now, but will install later else echo "Adobe RemoteUpdateManager not found." fi
Based off Adobe's RUM guide, link, you have to use sudo for RemoteUpdateManager
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>EnviromentVariables</key> <dict> <key>PATH</key> <string>/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:</string> </dict> <key>Label</key> <string>com.test.updateschedule</string> <key>ProgramArguments</key> <array> <string>sudo</string> <string>sh</string> <string>/Library/Scripts/Updates.sh</string> </array> <key>RunAtLoad</key> <true/> <key>StandardErrorPath</key> <string>/var/log/EsoUpdateError.log</string> <key>StandardOutPath</key> <string>/var/log/EsoUpdate.log</string>
- Copy update.sh to
/Library/Scripts/and the .plist to
sudo chown root:wheel.sh
sudo chown root:wheel.plist.
sudo launchctl load -w /Library/LaunchDaemons/.plist
- The moment I load the .plist, it creates two logs at
/var/log/. The standardoutpath log lists all the updates which is exactly what I want.
After restarting the computer to see if results stick, I notice that the results cannot be replicated. Instead I receive the following in StandardErrorPath log:
RemoteUpdateManager exiting with Return Code (1)
Based of the RUM guide, Return Code (1) is: "Generic error, for example an internal error. For example, this might be the case where Adobe Application Manager installation is corrupted or network is not present. In this case, typically, the process of downloading or installing updates cannot be started at all."
I went as far to apply chmod 777 and chown root:wheel to both the .sh and .plist, along with `/usr/local/bin/RemoteUpdateManager'. Tried without sudo in the .plist and .sh.