If you use Jamf Pro, you can set the
NotifyLogStylekey-value tojamfto automatically display Jamf Pro policy logs as status updates to users.Use custom policy triggers in your script to run essential computer setup management tasks, such as installing essential software.
Since the Notify screen should only display once during computer setup, end the script with the following command that disables the used Notify screen:
/usr/local/bin/authchanger -reset -JamfConnect
To download example scripts as a starting point, see Jamf's jamf / jamfconnect (GitHub).
Advanced Options
Onboarding scripts and policies can be run many different ways. If your onboarding procedure will exceed the standard 15 minute re-occurring check-in period for Jamf Pro, you may consider stopping the re-occurring check-in as part of your onboarding script. Re-occurring check-in can disrupt policies triggered by a custom trigger if the batch of policies exceeds the 15 minute timer.
To disable, run the following commands:
# Wait for enrollment then temporarily disable check-in
# Once Jamf Pro enrollment is complete, a launch daemon will run that automatically
# does re-occurring check-in every 15 minutes (or as set in Jamf Pro settings).
# Set the location of the re-occurring check-in launch daemon file
ld="/Library/LaunchDaemons/com.jamfsoftware.task.1.plist"
# Pause until the file exists which means enrollment is complete
while [ ! -f "$ld" ]; do
sleep 0.1;
done
# Boot out the launch daemon to stop it from running
# Remember to run a policy to turn this back on later!
/bin/launchctl bootout system "$ld"To re-enable check-in later:
# Set the location of the launch daemon file
ld="/Library/LaunchDaemons/com.jamfsoftware.task.1.plist"
# Re-enable the launch daemon to continue re-occurring check-in
/bin/launchctl bootstrap system "$ld"