The workflow that creates the local admin during the pre-stage does not run during device enrollment when the *.jamfcloud.com/enroll method is used. If you need to put your local admin account on devices that are manually enrolled, you will need to create a policy to add the account at enrollment.
Generally speaking, you do not want to use Device Enrollment (User-initiated enrollment) for anything beyond lab testing, and you want all devices enrolling with Automated Device Enrollment (PreStage).
The workflow that creates the local admin during the pre-stage does not run during device enrollment when the *.jamfcloud.com/enroll method is used. If you need to put your local admin account on devices that are manually enrolled, you will need to create a policy to add the account at enrollment.
Generally speaking, you do not want to use Device Enrollment (User-initiated enrollment) for anything beyond lab testing, and you want all devices enrolling with Automated Device Enrollment (PreStage).
Well, in a perfect world, maybe. But many don't have AxM and you need that.
We have clients on both sides, and both work fine. One is just a little easier...
@AJPinto wrote:
The workflow that creates the local admin during the pre-stage does not run during device enrollment when the *.jamfcloud.com/enroll method is used. If you need to put your local admin account on devices that are manually enrolled, you will need to create a policy to add the account at enrollment.
Generally speaking, you do not want to use Device Enrollment (User-initiated enrollment) for anything beyond lab testing, and you want all devices enrolling with Automated Device Enrollment (PreStage).
