Default Configuration (06:41; no audio; edited for time)
A default Configuration is required before being able to generate a customized script with SYM-Helper.
We’ve already completed our Jamf Pro policy pre-work and have dedicated enrollment policies, so let’s filter on “enrollment.”
You can easily add policies from the left column to the selected configuration by double-clicking.
Click the plus button to add a validation.
Multiple triggers can be displayed to the user as a single item by first selecting them, then clicking “group.”
Next, we’ll add a Local validation for “filevault,” which is built-in to Setup Your Mac.
"listitem": "FileVault Disk Encryption",
"progresstext": "FileVault is built-in to macOS and provides full-disk encryption to help prevent unauthorized access to your Mac.",
We’ll continue adding policies from the list on the left by double-clicking.
When you use the so-called “filepath” validation, you can use the “select” button to navigate in the filesystem for the desired app, then manually enter:
You’ll always want to end with a Local Validation of “recon” and also specify the command of “recon” to update your Jamf Pro server for the newly enrolled Mac.
"listitem": "Computer Inventory",
"progresstext": "A listing of your Mac’s apps and settings — its inventory — is sent automatically to the Jamf Pro server daily.",
Let’s search for
policyJSON= and you’ll notice that the Validations we manually added are missing data for:
(While we could have specified
progresstext in SYM-Helper for the Local Validations, I purposely didn’t for the sake of this demo.)
The so-called “Welcome” screen looks good and here we see the missing information from our
On the left, we have a sample
policyJSON from the GitHub repo, which we’ll use to copy-pasta the missing information in our customized Setup Your Mac script.
With the updates now in-place, let’s re-run the script.
… Deep, Cleansing Breath …
I don’t want to continue filling out all these fields for the rest of the demos, let’s turn off most of the fields in SYM-Helper.
We’ll toggle off most of the prompts and then click “Generate Script” and replace our previous script. If you look at the VS Code window in the background, you’ll see the changes we manually made are blown away when we re-generated the script in SYM-Helper.
We’ll re-copy-pasta, save and re-run the script … nice! Now we only have to enter Asset Tag.
Hey! Everything is now showing up!