If profile is only scoped in prestage it may be removed before Setup Manager runs due to PI112111 #120

New Issue

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

michael commented

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

Originally created by @zpropheter on GitHub.

When scoping config profiles in prestage it's presumed they will remain on device until reaching the login screen/desktop.
If you scope only to the prestage for Setup Manager and try to run it will error out saying there's no profile assigned. This appears to be mainly affected when the prestage is affected by PI112111

Originally created by @zpropheter on GitHub. When scoping config profiles in prestage it's presumed they will remain on device until reaching the login screen/desktop. If you scope only to the prestage for Setup Manager and try to run it will error out saying there's no profile assigned. This appears to be mainly affected when the prestage is affected by PI112111

michael closed this issue

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

michael commented

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

@scriptingosx commented on GitHub:

Yes, this is documented: https://github.com/Jamf-Concepts/Setup-Manager/blob/main/Docs/JamfPro-QuickStart.md#scoping-and-prestage

Scope the configuration profile to the computers you want to run Setup Manager on

This is a behavior of Jamf Pro that Setup Manager cannot directly adress or fix

@scriptingosx commented on GitHub: Yes, this is documented: https://github.com/Jamf-Concepts/Setup-Manager/blob/main/Docs/JamfPro-QuickStart.md#scoping-and-prestage > Scope the configuration profile to the computers you want to run Setup Manager on This is a behavior of Jamf Pro that Setup Manager cannot directly adress or fix

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: jamf/Setup-Manager#120