In a previous role, I had created custom scripts with Parameter values to be used in Jamf Remote by my IT support colleagues. This provided a simple interface for common support tasks while also being able to supply custom values to scripts without having to copy & paste complex command line arguments.
In the case where a Mac had an incorrect hostname, a support technician would simply launch & authenticate into the Jamf Remote app, select the appropriate device and script, enter the desired hostname in the appropriate Parameter value field, and click Go!
This was made possible by the fact that:
- All our Macs were on-premise or remotely connected via VPN.
- Our Jamf Pro Server was also on-premise.
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. That said, there are still plenty of use cases where this functionality is useful. This is limited by the fact that scripts attached to policies can have custom variables assigned at the policy level but not at runtime. 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 <custom value>. Depending on the level of your support team, this may simply not be an option.
As 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.
Thankfully, a fellow Jamf user commented on a related feature request with a solution. 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!
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.
To utilize this bash function, you’ll need to complete the following:
- Copy & paste the
checkCustomParamatersfunction to your desired script(s) and call the function.
- In your script where you normally use
$9, instead assign the appropriate
$pXValuewhere X is the parameter value.
- Assign your script to a policy and make it available on an Ongoing basis with a custom trigger.
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.
sudo jamf policy -event <custom trigger name> -p1 <p1 value> -p2 <p2 value> ...
Now, we can accomplish the task of remotely changing a Mac’s hostname:
sudo jamf policy -event sethostname -p1 "new_hostname" Password: Checking for policies triggered by "sethostname" for user "testuser"... Executing Policy Change Mac Hostname Running script SetHostname... Script exit code: 0 Script result: P1 value is new_hostname Successfully changed hostname to new_hostname! Running Recon...