Setup manager 1.3 and JamfSetupEnrollmentDone attribute not working in MacOS 15.6 #48

New Issue

michael · 2026-01-19T18:31:21Z

michael commented

2026-01-19 18:31:21 +00:00

Originally created by @bygeorgeio on GitHub.

Setup manager is stuck on ‘getting ready’ after installing macOS 15.6.

It worked perfectly fine in 15.5.

There have been no changes to my environment apart from upgrading to macOS 15.6.

After a period of time the dredded something went horribly wrong. Stopping everything message is displayed.

In the library /logs setup manager log
There’s nothing too obvious.

One interesting thing I see is that one of my config profiles that was using a computer attribute based on jamf setup being complete (JamfSetupEnrollmentDone echoing 'done) has been ignored (I use this attribute to make sure it avoids network and 8021x payloads until setup manager is done because for some reason network payloads with 8021x seem to interrupt setup manager) So as a result setup manager now cannot continue.

So it’s almost as if this attribute is getting ignored on smart groups and useless with config profiles after moving to macOS 15.6.

As I mentioned I’ve done zero changes apart from upgrade to 15.6.

Originally created by @bygeorgeio on GitHub. Setup manager is stuck on ‘getting ready’ after installing macOS 15.6. It worked perfectly fine in 15.5. There have been no changes to my environment apart from upgrading to macOS 15.6. After a period of time the dredded something went horribly wrong. Stopping everything message is displayed. In the library /logs setup manager log There’s nothing too obvious. One interesting thing I see is that one of my config profiles that was using a computer attribute based on jamf setup being complete (JamfSetupEnrollmentDone echoing 'done) has been ignored (I use this attribute to make sure it avoids network and 8021x payloads until setup manager is done because for some reason network payloads with 8021x seem to interrupt setup manager) So as a result setup manager now cannot continue. So it’s almost as if this attribute is getting ignored on smart groups and useless with config profiles after moving to macOS 15.6. As I mentioned I’ve done zero changes apart from upgrade to 15.6.

michael added the Support label 2026-01-19 18:31:21 +00:00

michael closed this issue

2026-01-19 18:31:21 +00:00

michael commented

2026-01-19 18:31:21 +00:00

@scriptingosx commented on GitHub:

Please ensure that you have “Clear extension attribute values” enabled in Settings > Global > Re-enrollment in Jamf Pro. (You probably want all options there enabled.)

If the extension attribute is not cleared on re-enrollment, the smart group will retain that computer and the profile will be in scope immediately after enrollment. Even though this certainly affects the Setup Manager workflow, this is not a Setup Manager issue or something we could fix within Setup Manager.

I cannot recreate the issue in my test environment. If the problem persists for you, please open a ticket with Jamf Support.

One possible workaround could be to delete the computer record before re-enrolling.

@scriptingosx commented on GitHub: Please ensure that you have “Clear extension attribute values” enabled in Settings > Global > Re-enrollment in Jamf Pro. (You probably want all options there enabled.) If the extension attribute is not cleared on re-enrollment, the smart group will retain that computer and the profile will be in scope immediately after enrollment. Even though this certainly affects the Setup Manager workflow, this is not a Setup Manager issue or something we could fix within Setup Manager. I cannot recreate the issue in my test environment. If the problem persists for you, please open a ticket with Jamf Support. One possible workaround could be to delete the computer record before re-enrolling.

michael commented

2026-01-19 18:31:21 +00:00

@bygeorgeio commented on GitHub:

all those things have been checked off of course. the timing is suspicious. I will raise a ticket with support. as you suggested this may not be an issue with setup manager but may be related to something weird going on with how often smart groups are being refreshed. ill close this off.

@bygeorgeio commented on GitHub: all those things have been checked off of course. the timing is suspicious. I will raise a ticket with support. as you suggested this may not be an issue with setup manager but may be related to something weird going on with how often smart groups are being refreshed. ill close this off.

michael commented

2026-01-19 18:31:21 +00:00

@bygeorgeio commented on GitHub:

Update. I excluded the profile and now setup manager works. So the extension attribute that utilises JamfSetupEnrollmentDone done result is being ignored and it just installs all profiles anyway.

My Computer Extension attribute script is as follow:

if [ -f "/private/var/db/.JamfSetupEnrollmentDone" ]; then
echo "done"
else
echo "incomplete"
fi

@bygeorgeio commented on GitHub: Update. I excluded the profile and now setup manager works. So the extension attribute that utilises JamfSetupEnrollmentDone done result is being ignored and it just installs all profiles anyway. My Computer Extension attribute script is as follow: if [ -f "/private/var/db/.JamfSetupEnrollmentDone" ]; then echo "<result>done</result>" else echo "<result>incomplete</result>" fi

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: jamf/Setup-Manager#48