2018 MacBook Pro 15" Enrollment Complete Policies A No Go?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on
09-06-2018
07:49 AM
- last edited on
03-04-2025
04:47 AM
by
kh-richa_mig
Hey all,
With this model, it doesn't seem like the enrollment complete policies kick off during DEP. I checked the logs and it seems like it checks but doesn't run any after enrollment. Turned off the Secure boot just in case but still a no go.
Is this 10.13.6 on the new models some type of special build like in the past? We are also still on JAMF 10.6.0 so wondering if there was a fix in 10.6.2.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 09-06-2018 01:58 PM
@Jae Have you disabled:
Settings > Computer Management > Check-In > Allow Network State Change Triggers ?
We've had enough Enrollment Complete policies fail that we have a policy in Self Service scoped to just support personnel which runs jamf policy -event enrollmentComplete

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 09-09-2018 12:34 PM
We DEP built our first 2018 MBPs and the enrollment trigger kicked off with no problems on both of them

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 09-10-2018 04:56 AM
@marklamont what version of JAMF are you using?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 09-15-2018 11:14 AM
bit late replying but 10.5 at the moment

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 09-19-2018 02:51 PM
I was able to see the issue with the enrollment. We have the scope configured to not included encrypted machines for the enrollment trigger. Since the 2018 ones show up as encrypted regardless of Filevault not being enabled, this was causing the policy to not trigger at all.
