1 ACCEPTED SOLUTION
Hi m.kindelberger,
I changed as you sad and it worked for me. Thank you.
@MDM The following seems to be working for us:
The important bits from two of the scripts are below; please let me know if your mileage varies too greatly.
Microsoft Teams Clean-up
#!/bin/sh
####################################################################################################
#
# ABOUT
#
# Removes user-specific files prior to upgrading Microsoft Teams
#
####################################################################################################
#
# HISTORY
#
# Version 1.0, 12-Dec-2017, Dan K. Snelson
#
####################################################################################################
# Variables
loggedInUser=$(stat -f%Su /dev/console)
applicationPath="Microsoft Teams.app"
# Check if the specified application is installed ...
testDirectory="/Applications/${applicationPath}"
if [ -d "${testDirectory}" ] ; then
echo "/Applications/${applicationPath} located; proceeding ..."
echo "Removing ${loggedInUser}-specific files for ${applicationPath} ..."
/bin/rm -Rf /Users/${loggedInUser}/Library/Caches/com.microsoft.teams*
/bin/rm -Rf /Users/${loggedInUser}/Library/Application Support/Microsoft/Teams
/bin/rm -Rf /Users/${loggedInUser}/Library/Application Support/com.microsoft.teams
echo "Removed ${loggedInUser}-specific files for ${applicationPath}."
exit 0
else
echo "/Applications/${applicationPath} NOT found; nothing to do."
exit 0
fi
exit 0Application Permission
#!/bin/sh
####################################################################################################
#
# ABOUT
#
# Sets permissions on the application passed as Parameters 4 & 5.
#
####################################################################################################
#
# HISTORY
#
# Version 1.0, 12-Dec-2017, Dan K. Snelson
#
####################################################################################################
# Variables
loggedInUser=$(stat -f%Su /dev/console)
applicationPath="$5"
# If Parameter 5 is blank, exit ...
if [ -z "${applicationPath}" ]; then
echo "Application Path not specified; exiting."
exit 1
fi
# Check for a specified owner (Parameter 4)
# Defaults to currently logged-in user
if [ "$4" != "" ] && [ "$owner" == "" ]; then
owner="${4}"
else
echo "Parameter 4 is blank; using "${loggedInUser}" as the owner."
owner="${loggedInUser}"
fi
# Check if the specified application is installed ...
testDirectory="/Applications/${applicationPath}"
if [ -d "${testDirectory}" ] ; then
echo "/Applications/${applicationPath} located; proceeding ..."
echo "Setting permissions on /Applications/${applicationPath} ..."
/usr/sbin/chown ${owner} "/Applications/${applicationPath}"
echo "Set owner of "/Applications/${applicationPath}" to ${owner}."
exit 0
else
echo "/Applications/${applicationPath} NOT found; nothing to do."
exit 0
fi
exit 0
@maziboss Thanks for the questions. Hopefully the following will clarify using this script:
In Settings > Computer Management > Scripts > {Script Name} > Options, set:
PARAMETER 4 to: Owner (defaults to current user)
PARAMETER 5 to: Application (i.e., Microsoft Teams.app)
So, leave Parameter 4 blank in your policy.
No, I don't change any permissions when creating the .PKG. (We use a customized version of @mm2270's App Packager to create the .PKG we're deploying.
