Installing GlobalProtect and copying plist to $USER preferences library
I can install the globalprotect pkg with the k1000 without issue, but I just cannot get the plist for it set or deployed.
I've tried with kscript and shell script.
I've installed the globalprotect software and configured the portal and settings for our org, then I copied the two plist files created in the user's preferences.
I zipped up GlobalProtect.pkg, com.paloaltonetworks.GlobalProtect.plist, and com.paloaltonetworks.GlobalProtect.settings.plist to GlobalProtectMacs.zip. I associated this file with the k1000 software inventory item and then used the following custom command on the managed installation:
sudo cp -R com.paloaltonetworks.GlobalProtect* /Users/$USER/Library/Preferences/ && sudo installer -pkg GlobalProtect.pkg -target /
I can manually run the following from terminal and all works, but I can't get the k1000 to do it on its own.
sudo cp -R com.paloaltonetworks.GlobalProtect* ~/Library/Preferences/ && sudo installer -pkg GlobalProtect.pkg -target /
Any suggestions much appreciated. Thanks.
2 Comments
[ + ] Show comments
-
Yes, that was what I figured, so did run it as system user via script, it failed as well... but at that point i had finished pulling all my hair out after many misfires... not the least of which was recalling that I can't use a mac to compress files together as the OS 'helps' us by creating the _MACOS directory that screws up managed installs... sigh. Anywho... I'm going to start fresh today and try again with just a scripted install. Thanks! - kpm8 6 years ago
-
You're welcome! - ondrar 6 years ago
Answers (1)
Answer Summary:
Please log in to answer
Posted by:
ondrar
6 years ago
Top Answer
I don't have any experience with Macs, but I think the issue is that Managed Installs always run as System (on Windows) or the Mac equivalent on Macs. Since you're using the $USER variable, you would need to have KACE run the command as the logged in user, which is an option only available on a KACE Script. Try running the command from a Script as the logged in user, and I think it should work.