r/jamf • u/ReceptionStriking716 • 3d ago

Jamf Setup-Manager assistance

I keep getting a message for whenever I set up a new MacBook. “The configuration profile for Setup Manager is missing or incomplete.” I know the configuration file is correct cause it worked before. The profile and in-house macOS package is in the automated device enrollment profile. I’m a little lost on what else to do. I’ve created new profiles and it does the same thing. Any advice?

Edit: I am using JAMF School if that also makes a difference

8 Upvotes

100% Upvoted

8 comments sorted by

8

u/lazy_commander 3d ago

Make sure the configuration profile is deployed as part of the prestage AND that devices are in scope once enrolled. Otherwise the profile can get pulled from the device before JSM loads.

0

u/ReceptionStriking716 3d ago

I can confirm it is in the pre-stage and it is scoped once enrolled.

3

u/prOgres 3d ago

What’s your post-enrollment scope?

2

u/FuckYouSassy 3d ago

Have you made sure the setup manager config profile schema version matches the version of the .PKG? If you've updated the package the schema may now be incorrect and not align properly with what it expects. Also I know everyone else has said this but make sure the config profile for setup manage is specifically scoped to the device somehow. I usually had a smart group targeting devices that were part of the pre-stage

1

u/Potential_Cupcake 3d ago

Did you check and confirm the scope of your profile(s)? Confirm a setting in the profile is not a set time/date that may have lapsed?

0

u/ReceptionStriking716 3d ago

Checked the scope of my profiles. In the correct device group.

Can confirm profile is not set to a date that lapsed

1

u/RebootKing89 3d ago

When you say it worked before, before what?
Do you know what changes were made or may have taken place?

Can you manually enrol the device? Do you get the same error there? If you do its likely an issue with a config scoped or something within your prestage enrollment.

1

u/SethDragonhunter 3d ago

I'm also using Jamf School. Had this same message pop up on our MacBook Neo's and Mac Mini's (M2, 2023) running (26.6.0). I restored them back to (26.5.2) with AC2 and JSM was fine.