-
Notifications
You must be signed in to change notification settings - Fork 0
2 Customizing Scripts
There are some changes you need to make to the Registration.sh and Branding-Customizations.sh scripts to use them in your environment.
If you plan to use a workflow utilizing the standard signed and notarized Baseline package, you will need to use the Branding-Customizations.sh script to download a custom Baseline-Branding-Customizations.pkg. The script and custom package need to be hosted on a public https site, like GitHub or an AWS S3 bucket.
The Branding-Customizations.sh script is used to download branding and other customizations needed when using the standard Baseline installer package. If you plan on using a name other than Baseline-Branding-Customizations.pkg, change the customizationsPkgName variable to match the name you use. Change the hostUrl variable to the URL you use to host your package.
The Registration.sh script provides three functions. First, it checks whether the device is running on battery or not and displays a message to the end user requiring connection of the power cord before proceeding. Second, it displays an End User License Agreement and requires the user to agree to the license. Lastly, it provides the "Register Your Mac" functionality to gather data about the device being enrolled. In its current form, the script collects the following required information:
- Asset Tag - User entered 5-digit number with regular expression validation
- Computer Name - User entered computer name
- Department - User selected department from a provided list of departments - must match list in Jamf Pro
- Building - User selected building from a provided list of buildings - must match list in Jamf Pro
- Set Up By - User selected technician name from a provided list of technicians
- Deployed - User selected period of device deployment
The "Set Up By" and "Deployed" information can be easily changed to collect other information relevant to your provisioning workflow. Or you can remove it altogether. Search the Registration.sh for "setUpBy" and "deployed" to find the relevant parts in the script.
If you have no need for the end user license agreement dialog, you can search for "eula" in the Registration.sh script and remove those parts. You would no longer need to provide a eula.md file in your installer packages.
The script writes a provisioning report called BaselineConfigData.plist to /Users/Shared/ which contains the following information: asset tag number, serial number, device uuid, building, department, set up by name, provision timeframe, provision date, username and EULA response.