JAMF PRO PRESTAGE ENROLLMENT SERIAL
JAMF PRO PRESTAGE ENROLLMENT MANUAL

Having a standard naming convention for all of your PreStage Enrollments is important. With DEP, the PreStage Enrollment configurations are the new foundational layer that everything else uses to determine whether or not settings, software, configuration profiles, etc. Additionally, a big shoutout to for creating the rename-comp.py script that makes our automated computer naming possible! Step 1: PreStage Enrollment ConfigsĬoming from an imaging deployment workflow, the static or smart configuration was the basis for determining what software was installed on a given machine. The DEP setup & MDM configuration process is beyond the scope of this post. Here is that resulting A to Z guide for DEP enrollments with Jamf. Giving credit where credit is due, this workflow in large part came out of the work by and discussions with an admin at Red Hook Central Schools.

A second post-enrollment policy activated via custom trigger to bind the automatically named Mac.

JAMF PRO PRESTAGE ENROLLMENT MANUAL

A script run at the end of the previous policy to verify the hostname and trigger either a manual rename policy (if verification fails) or another series of enrollment policies.

A post-enrollment policy activated via custom trigger to automatically set our Mac’s hostname as listed in the previous file.

JAMF PRO PRESTAGE ENROLLMENT SERIAL

A web server with a CSV file or Google Sheet containing your Mac serial #s and associated hostnames.A PreStage Enrollment configuration w/ DEP Macs assigned.We subsequently implemented a workflow utilizing Jamf’s Encrypted Strings to more securely provide account passwords as part of scripts with an account that had the necessary privileges.īelow is the basic structure for this part of our large deployment workflow: Unfortunately, at the time we did not realize that the account we were using to unbind the Mac did not have sufficient privileges to remove the record in AD, so we were having to manually delete the incorrect records afterward. This was prone to errors, which meant having to unbind, rename the Mac, and bind it again. When we were still imaging (via Jamf Imaging & NetBoot, R.I.P.), we were naming our Macs as part of selecting the applicable Jamf Imaging config. If you don’t happen to bind your Macs, that’s OK too, as this post is more focused on the automatic naming process we’ve employed which occurs prior to binding. While you may not be binding your Macs anymore, this post is meant to share our current workflow to copy or modify as you see fit. I’ve spent the last two years refining our deployment process to make it as smooth as possible.

Jamf pro prestage enrollment