Hi ​@gwhaley262 ,

Maybe you missed this part:
JSM installs the package through Policies using the Custom trigger at a custom event.
Name the custom event according to the package name (for example: GoogleChrome)..

Then, add it to the JSM section under Policy Trigger.
 

On github @ https://github.com/jamf/Setup-Manager/blob/main/Docs/JamfPro-QuickStart.md

it says:

• scope the configuration profile to the computers you want to run Setup Manager on
• create a new Prestage or duplicate an existing one
• add the Setup Manager pkg and the configuration profile to the Prestage
• when installing and using Jamf Connect Login, ensure you have the latest version
• ensure that 'Automatically advance through Setup Assitant' is disabled
• have at least one Setup Assistant option which shows before user creation disabled (so that is displayed), we recommend the Location Services or Terms and Conditions pane
• ensure your test Mac(s) is (are) assigned to the Prestage

I have the configuration profile built with the Enrollment Actions to install other applications.

Ran into something similar earlier in the year while setting it up. What version of Jamf are you on? And what version of Jamf Setup Manager are you using?

Do you have any other packages checked off in your prestage? Or is Jamf Setup Manager the only package?

If I recall correctly, there was a bug in Jamf Pro that was causing the JSM package to fail. A test workaround was I created a policy to install so I could see JSM in action. But this isn’t the intended way to use it.

I’m using an on-premise version of 11.19.1 and the current 131.1-610 version of JSM.

Should be good then with versions.

Any other packages in your prestage? And what is the macOS version of the client you’re testing it on?

Sequoia 15.6.1