Now you can call your policy with your selected custom variables! The added benefit of this method is that you have more than just the normal parameter 4 – 9 values available in Jamf scripts. Assign your script to a policy and make it available on an Ongoing basis with a custom trigger.In your script where you normally use $4 – $9, instead assign the appropriate $pXValue where X is the parameter value.Copy & paste the checkCustomParamaters function to your desired script(s) and call the function.To utilize this bash function, you’ll need to complete the following: The function parses the Jamf policy command based on its process ID and then parses the parameter values to be used as part of the script. With a simple bash script function added to your script tied to a policy, you can call Jamf policies on the command line and supply custom variables at runtime! Thankfully, a fellow Jamf user commented on a related feature request with a solution.
#Jamf pro variables pro
Depending on the level of your support team, this may simply not be an option.Īs of Jamf Pro Server version 10.28.0, the previously available jamf runScript for local scripts is being deprecated and while this did not achieve the same functionality of running scripts within Jamf it renewed my interest in finding a replacement.
To accomplish the same hostname functionality would require the support technician to have access and comfort to edit a policy, change a Parameter value associated with it, and trigger the policy from the user’s Mac via sudo jamf policy -event.
This is limited by the fact that scripts attached to policies can have custom variables assigned at the policy level but not at runtime. That said, there are still plenty of use cases where this functionality is useful. In a Jamf Cloud & work from home environment, this simply isn’t possible in the same way even if you are able to remotely connect to your Macs. Our Jamf Pro Server was also on-premise.All our Macs were on-premise or remotely connected via VPN.
0 kommentar(er)
