How are the pkg built?

We use the adobe admin console to create the packages and set it to disable updates and not allow users to update from the cc client (for labs) but enable rum (remote update manager) so we can run the rum commands if needed.

@Andrewpants1 Here are a few snippets from a larger script which may prove helpful:

### Variables

loggedInUser=$( /usr/bin/stat -f%Su /dev/console )  # Currently logged in user



### Functions

killProcess(){

    echo "Quit Adobe-related process: "${1}" ..."

    /usr/bin/pkill -l -U ${loggedInUser} "${1}"

}

…

killProcess "Creative Cloud"

killProcess "CCLibrary"

killProcess "Core Sync"

killProcess "Core Sync Helper"

killProcess "Adobe Desktop Service"

killProcess "CCXProcess"

### Variables

loggedInUser=$( /usr/bin/stat -f%Su /dev/console )  # Currently logged in user



### Functions

killProcess(){

    echo "Quit Adobe-related process: "${1}" ..."

    /usr/bin/pkill -l -U ${loggedInUser} "${1}"

}

killProcess "Creative Cloud"

killProcess "CCLibrary"

killProcess "Core Sync"

killProcess "Core Sync Helper"

killProcess "Adobe Desktop Service"

killProcess "CCXProcess"

The only issue I have found is that some of the Adobe applications will throw up a Crash Report when they are killed in this fashion.

But otherwise, it works exactly as desired.