Running Entire Script as Logged In User

Maybe deploy the script to /var/tmp using composer.

Then trigger it from JAMF like this at login/recurring:

CURRENT_USER=$(/usr/bin/stat -f "%Su" /dev/console)

sudo -H -u $CURRENT_USER bash -c '/private/var/tmp/script.sh'

Might need to check the -c option again, and adjust the shell accordingly. Maybe check the .she has executable permissions for the staff group.

Could get really fancy and use conditional statements to check if they already have the templates in location already.

On another note, I remember I had some issues with our auto mount of a NAS as MacOS got newer.

I think I cheated JAMF into running an Osascript as current user by having it in its own policy with a custom trigger, set to ‘Ongoing’.

The actual script that runs calls:

sudo JAMF policy -trigger triggerName

In the console application on the device it looks like “looking to run ‘policy’ as ‘user’”

Yeah, probably the wrong way to go about it, but it did the trick… so happy days.

Last note: I always had issues with using $USER, so switched to the one above ($CURRENT_USER) to assure that part actually works.

Thanks @Qwheel!  Sorry if I'm sounding like a noob here but how would you do that in Composer?  Do you mean to build a package with the script inside?

That’s the one ;)

plonk the script in /var/tmp

Cool.  Will give it a try now. 

There's no need to run a script to deploy Office templates to user home folders. Deploy them instead to '/Library/Application Support/Microsoft/Office365/User Content.localized/' for all users of the computer.

See this document:

https://macadmins.software/docs/UserContentIn2016.pdf

Hi @talkingmoose the folder /Library/Application Support/Microsoft/Office365/User Content.localized/...  does not exist on my test machine where I have Office installed.  The only folder in there is something called MAU2.0.

If you plan to use the content on a recurring nature, so that it is available fore the script to run after a restart, then you do not want to store in any 'tmp' folder. I would suggest creating a folder somewhere, like in /var or in /Library, that is specific to your org and storing there. The contents of a 'tmp' folder may get deleted on reboot.

If you create the folder structure, the O365 applications should respect it. So, create the /Library/Application Support/Microsoft/Office365/User Content.localized/Templates folder and deploy your templates there.

Ok I will do some testing and come back to you guys.  Thanks for the help and clarification. :)

So I have created the folder structure and deployed the templates there but Word is not picking them up?  Are they supposed to appear in the Personal section or Work section in Word when you click New?  Maybe Office needs permissions to the new folder structure or something?  

Nevermind.  Used a chmod 555 command and this is now working!  Great help @stevewood @talkingmoose !