10 Reasoning

Reasoning

Currently when a new JAMF machine gets enrolled there is an enrollmentComplete policy trigger that happens. This trigger is extremely unreliable though as it can be interrupted by multiple items:

1. A transition of the machine from having _mbtsetupuser logged in to having the user account logged in causes the policy call to stop executing
2. A lack of network connectivity causes the enrollmentComplete trigger to not return any polices
3. A network transition in the middle of the enrollmentComplete policy call will cause the policy call to stop due to the NetworkStateChange trigger overriding the call.
4. The machine shutting down or restarting during the enrollment process will cause the trigger to possibly not fire or be interrupted with no recovery on the trigger as it is only called once.

All of these things lead to the JAMF policy call not executing correctly and/or fully. Therefore I developed a better way to do it reliably