Bug: User-initiated Enrollment issue with M3 chip #130

Closed
opened 2026-01-19 18:31:38 +00:00 by michael · 6 comments
Owner

Originally created by @ecanault on GitHub.

Hi,

When manually enrolling a Mac with M3 chip, we deploy the Setup Manager package with a policy using the Enrollment Complete trigger.
We have checked that the configuration profile is deployed before the package, but unfortunately when Setup Manager is launched, there is no customized deployment: it opens generic texts and icons, performs the steps 1 to 6 preparation, then asked to Continue without deploying anything.

No probem with M3 chip and Automated Device Enrollment process when the Setup Manager package is deployed through a PreStage profile.
No problem also with M1 chip and either Automated Device Enrollment or User-initiated Enrollment.

Thanks,
Emmanuel Canault

Originally created by @ecanault on GitHub. Hi, When manually enrolling a Mac with M3 chip, we deploy the Setup Manager package with a policy using the Enrollment Complete trigger. We have checked that the configuration profile is deployed **before** the package, but unfortunately when Setup Manager is launched, there is no customized deployment: it opens generic texts and icons, performs the steps 1 to 6 preparation, then asked to Continue without deploying anything. No probem with M3 chip and Automated Device Enrollment process when the Setup Manager package is deployed through a PreStage profile. No problem also with M1 chip and either Automated Device Enrollment or User-initiated Enrollment. Thanks, Emmanuel Canault
michael added the bug label 2026-01-19 18:31:38 +00:00
Author
Owner

@ecanault commented on GitHub:

@scriptingosx

I took the time to test 1.1beta with :

  • macOS 14.5
  • macOS 15.0
  • macOS 15.0.1
  • macOS 15.1beta7

Setup Manager was working as expected each time now: I think you can close this one 😊

Thanks,
Emmanuel

@ecanault commented on GitHub: @scriptingosx I took the time to test 1.1beta with : - macOS 14.5 - macOS 15.0 - macOS 15.0.1 - macOS 15.1beta7 Setup Manager was working as expected each time now: I think you can close this one 😊 Thanks, Emmanuel
Author
Owner

@ecanault commented on GitHub:

macOS 14.5 was used.

We check the configuration profile deployment by keeping System Settings opened on the Profiles pane (as it displays contents dynamically) and having also the Utilities folder opened to sees that the app appears after the configuration profile.

@ecanault commented on GitHub: macOS 14.5 was used. We check the configuration profile deployment by keeping System Settings opened on the Profiles pane (as it displays contents dynamically) and having also the Utilities folder opened to sees that the app appears after the configuration profile.
Author
Owner

@scriptingosx commented on GitHub:

Have you tested this with Setup Manager 1.1beta?

@scriptingosx commented on GitHub: Have you tested this with Setup Manager 1.1beta?
Author
Owner

@ecanault commented on GitHub:

Have you tested this with Setup Manager 1.1beta?

Hi Armin,
Yes, but not specifically for this issue; I should be able to do that next wednesday I hope.
Regards,
Emmanuel

@ecanault commented on GitHub: > Have you tested this with Setup Manager 1.1beta? Hi Armin, Yes, but not specifically for this issue; I should be able to do that next wednesday I hope. Regards, Emmanuel
Author
Owner

@scriptingosx commented on GitHub:

Which version of macOS?

How did you check "that the configuration profile is deployed before the package"?

@scriptingosx commented on GitHub: Which version of macOS? How did you check "that the configuration profile is deployed **before** the package"?
Author
Owner

@scriptingosx commented on GitHub:

Awesome! Thank you! (BTW: you can close issues, as well)

@scriptingosx commented on GitHub: Awesome! Thank you! (BTW: you can close issues, as well)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: jamf/Setup-Manager#130