Hi folks,
I'm currently creating a new process for user initiated enrollments using DEPNotify. For testing, I'm removing all local device jamf components and running API scripts to unmanage/ un-enroll the device and de-selecting the "Allow Jamf Pro to perform management tasks", but keeping the JSS record intact. Then performing changes to the build script / procedure and re-enrolling again for testing purposes.
However, what I've found is that if I don't delete the JSS record for the device, although the the device successfully appears to re-enroll, the actual script that is supposed to run and start DEPNotify on the Enrollment complete trigger does not startup. It's as if it performs a "silent" re-enroll. I'd like the build process to be consistent regardless if it's a new enrollment or a re-enroll. We may have instances where devices have their management disabled in the JSS and need to be re-enrolled, and if it's end users performing the enrollment then it would be helpful to have on-screen feedback to show progress.
If I delete the JSS record before enrolling the device, the setup process works as expected, starting DEPNotify and other setup policies.
I'm probably missing something obvious, but does anyone know why this would be happening? I'd like to keep the process consistent.
Many thanks for any help.
