No, running from Self Service makes no difference.
I used a newer Version of the OutlookFontPoke from here:
https://github.com/AlyaKoni/OutlookFontPoke/tree/master
I created a PKG for that script which installs into
/usr/local/OutlookFontPoke/
My Script for setting up Font parameters via Jamf Policy:
#!/bin/bash
#send command to OutlookFontPoke v2.1 by Paul Bowden
#https://github.com/pbowden-msft/OutlookFontPoke/archive/refs/heads/master.zip
#pbowden@microsoft.com
# Variables
nameFont=$4 #eg "Arial"
echo "### nameFont - $nameFont"
sizeFont=$5 #eg "11.0pt"
echo "### sizeFont - $sizeFont"
colorFont=$6 #eg "gray"
echo "### colorFont - $colorFont"
pathToScript="/usr/local/OutlookFontPoke/OutlookFontPoke-2.1.sh"
#Get Current User
loggedInUser=$(/bin/ls -l /dev/console | /usr/bin/awk '{ print $3 }')
echo $loggedInUser " is logged in"
#fix permissions
chmod +x "$pathToScript"
# Run command as current logged in user
sudo -u $loggedInUser $pathToScript $nameFont $sizeFont $colorFont
exit 0
My settings for the Script in the Jamf Console look like this:
And the Policy settings are like this:
The Script runs once per day and log in, this ensures that things are ready before Outlook starts.
I didn't think so but I wasn't sure if triggering it from Self Service might run it AS the user.
Anyway, it worked for me without creating a package or any of that extra stuff though. I just used the original (https://github.com/pbowden-msft/OutlookFontPoke) but changed lines 125-127:
FONTNAME="$4"
FONTSIZE="$5"
FONTCOLOR="$6"
I did it on my user, which already had Outlook setup and everything, I just changed all the font preferences before running it. I just feel like I must be missing something, because I'm not that good of a script writer for it to be that easy of a fix.
