DEP goes well up until name change why?

NealIV
Contributor

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.aac38ff68e834ba39e4886a88f7a518a
f1c3fde73cf1481d9f0555db5b4ee82b

2 REPLIES 2

Chris
Valued Contributor

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.

marklamont
Contributor III

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?