#Jamf pro variables install#
I called mine “Script Preference” and set it to install to computer level. I want a file on every desktop named “Read me, !.txt Write the values you need in your script to the device using a Jamf Pro external application settings profile then read them into your script with “defaults read”.
That is a potentially dangerous practice since the user or someone that’s pwned their device to get at them.
But that requires us to provide API credentials to the clients. There’s some talk on Jamf Nation about pulling the values down to the running script via API. Jamf doesn’t replace that with the actual username assigned to the computer the way it does when distributing profiles. The script runs and the value of $4 is literally “$USERNAME”. If you’re like me, you’d look in the Admin Guide under Policy Scripts and find no mention of any kind of variable parameters there, and then try entering $USERNAME into a parameter value and running the policy just to see if it works. In the example URL below, “id=2” indicates the extension attribute ID number:įor more information, see Computer Extension Attributes. (computer-level profiles only)Username of the user logging in to the computerĮxtension Attribute ID Number Note: The ID number is found in the extension attribute URL. Username associated with the computer in Jamf Pro You’re probably familiar with the many variables we can use when construction profiles. ($1.$3 are automatically populated with some commonly used values - mount point, computer name, and username.) But what if we need to run the script with different parameter value for each computer? Then when adding the script to a policy, we could tell Jamf to send a value to use when running the script and it would show up in “$4”. For a shell script these would be $1.$11.
In Jamf Pro you can add a script under Settings and label the parameters.
0 kommentar(er)
