Posted on 02-28-2018 11:50 AM
As you can see in my log DEP goes well via splash buddy then after the naming script runs jamf goes into looking for "network state change" and my next AD bind script does not run which is number 55 policy. See screen shot of my policy.
Posted on 02-28-2018 11:31 PM
There is a bug where the networkStateChange trigger will interrupt and basically "kill" the enrollmentComplete trigger, PI-004144.
I guess changing the hostname affects a file that the networkStateChange trigger is monitoring, thus firing the trigger.
Posted on 03-01-2018 01:50 AM
instead of doing all of them from the enrolment trigger why not set them to work off a different trigger then just make a simple enrolment policy that fires that trigger from a script, would that not fix the issue?