Is there any benefit or drawback to installing config profiles through prestage (where it says "Use this section to add configuration profiles to the PreStage enrollment") vs. after enrollment (a config profile scoped to all computers)?
If the former is advised, would I then remove all scopes in the actual config profile(s)?
As it stands, right now we don't install via prestage. Rather it enrolls, it does its thing, then installs policies and config profiels.
Thanks folks! :)
Benefit of installing during PreStage is if you have software or settings you need on the device as the device is enrolling or before any enrollmentComplete items happen. For example, you may want to deploy a FileVault PRK redirect profile during PreStage along with Jamf Connect settings so that when the device has completed Setup Assistant the Jamf Connect login window is presented and if you are turning on FileVault at login, you can ensure the PRK is properly escrowed.
Or, if you have a requirement to get certificates for 802.1x or settings for your security software, you can get those profiles on the device before enrollment is finished.
Benefit of installing during PreStage is if you have software or settings you need on the device as the device is enrolling or before any enrollmentComplete items happen. For example, you may want to deploy a FileVault PRK redirect profile during PreStage along with Jamf Connect settings so that when the device has completed Setup Assistant the Jamf Connect login window is presented and if you are turning on FileVault at login, you can ensure the PRK is properly escrowed.
Or, if you have a requirement to get certificates for 802.1x or settings for your security software, you can get those profiles on the device before enrollment is finished.
Thanks Steve! This helps :D
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.