1 ACCEPTED SOLUTION
What is the scoping on the "updatePolicy"? Also, if you are trying to trigger using "updatePolicy" as the trigger, did you set "Custom Event" in the updatePolicy? You do not use the name of the policy, you use the value you put in the "Custom Event" field after selecting "Custom".
Thanks for replying! notifyPolicy is currently scoped to a single computer for testing/building. I want the "notifyPolicy" policy to execute first so that a user gets a popup to acknowledge. The acknoledgement then is supposed to trigger the "updatePolicy" policy which is what actually installs the .pkg i feel like i'm really close to getting this working.
Okay, I changed the parameter to "updateWorkspace" but now Jamf is giving me this error message: I did get the popup I wanted, which is nice! But I'm still not getting the activation of the update policy. what gives?
So, i came up with this as a new option for my notify policy
#!/bin/sh
# variable and function declarations
export PATH=/usr/bin:/bin:/usr/sbin:/sbin
# get the currently logged in user
currentUser=$( echo "show State:/Users/ConsoleUser" | scutil | awk '/Name :/ { print $3 }' )
# global check if there is a user logged in
if [ -z "$currentUser" -o "$currentUser" = "loginwindow" ]; then
echo "no user logged in, cannot proceed"
exit 1
fi
# now we know a user is logged in
# get the current user's UID
uid=$(id -u "$currentUser")
# convenience function to run a command as the current user
# usage:
# runAsUser command arguments...
runAsUser() {
if [ "$currentUser" != "loginwindow" ]; then
launchctl asuser "$uid" sudo -u "$currentUser" "$@"
else
echo "no user logged in"
# uncomment the exit command
# to make the function exit with an error when no user is logged in
# exit 1
fi
}
## Parameters for new software version
appPath="$4" # Path to application, escape spaces, no quotes
appName="$5" # Name of App
newVersion="$6" # target App Version
policyTrigger="$7" # name of install policy to be triggered
# main code starts here
OSASCRIPT="/usr/bin/osascript"
runAsUser $OSASCRIPT -e 'display dialog "'"$appName"' is outdated. Please quit '"$appName"', then click OK to update." buttons {"OK"} default button 1'; killall $appName; jamf policy -event $policyTrigger
fi
exit 0and after I get it to run, i get this in the Jamf logs
Not sure if I have too many fi statements or whatever.
i have also created this to try and follow @stevewood 's advice:
#!/bin/sh
# variable and function declarations
export PATH=/usr/bin:/bin:/usr/sbin:/sbin
# get the currently logged in user
currentUser=$( echo "show State:/Users/ConsoleUser" | scutil | awk '/Name :/ { print $3 }' )
# global check if there is a user logged in
if [ -z "$currentUser" -o "$currentUser" = "loginwindow" ]; then
echo "no user logged in, cannot proceed"
exit 1
fi
# now we know a user is logged in
# get the current user's UID
uid=$(id -u "$currentUser")
# convenience function to run a command as the current user
# usage:
# runAsUser command arguments...
runAsUser() {
if [ "$currentUser" != "loginwindow" ]; then
launchctl asuser "$uid" sudo -u "$currentUser" "$@"
else
echo "no user logged in"
# uncomment the exit command
# to make the function exit with an error when no user is logged in
# exit 1
fi
}
## Parameters for new software version
appPath="$4" # Path to application, escape spaces, no quotes
appName="$5" # Name of App
newVersion="$6" # target App Version
policyTrigger="$7" # name of install policy to be triggered
# main code starts here
OSASCRIPT="/usr/bin/osascript"
if [[ $version != $newVersion ]]; then
notifyUser="display dialog \"$appName is outdated. Please quit $appName, then click OK to Update.\" buttons {\"OK\"} default button 1"
runAsUser displayDialog=$( /usr/bin/osascript -e "$notifyUser" )
pgrep "$appName" | xargs kill -15
/usr/local/bin/jamf policy -event "$policyTrigger"
exit 0and I'm waiting to see if that helps
