I’m trying to implement Jamf Setup Manager. I have everything aligned regarding the configuration profile and the Jamf Setup Manager PKG assigned as an enrollment package. But the PKG won’t install. I’m not seeing any logging or the app in the Utilities folder after enrollment. Any suggestions would be appreciated.
Question
Deploy Jamf Setup Manager via Prestage Enrollment
+4
+8I’m trying to implement Jamf Setup Manager. I have everything aligned regarding the configuration profile and the Jamf Setup Manager PKG assigned as an enrollment package. But the PKG won’t install. I’m not seeing any logging or the app in the Utilities folder after enrollment. Any suggestions would be appreciated.
Hi
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.
+4On 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.
+20Ran 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.
+20Should 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?
Is your Pre-stage package signed, as it deploys before the device enrolls it has to be signed….
Had the same issue with SetupManager 1.3.1-610 and 1.3-601 pkg.
Configuration at enroll but tried at login to and got the same result.
It Works at the beginning, at a time Setup Manager would’nt install, got the setup assistant directely.
Reupload the package but still works at the beginning then stop.
Didn't found yet what's wrong.
Sometimes the management history from Jamf shows the install SetupManager action but nothing is on the Mac.
+20Out of curiosity, are you able to test version 1.2 or 1.1?
It seems resolved for me. I will confirm in the following days if Setup Manager still works.
Had an issue with packages downloading from jamf. (It appears after the Setup Manager case)
“Error: Package was not successfully downloaded. 401
Error: *****.pkg is not available on the HTTP server.” in jamf log.
When using the URL of the policies return error 400.
The Jamf CloudOps team update ccm_settings by mysql command then restart TomCat.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.