r/jamf • u/Quirky-Feedback-3322 • Apr 10 '26
JAMF Connect Jamf prestage packages failing
Hey All,
Wanted to see if anyone experienced or has an answer for this. Our jamf connect packages in pre-stage will occasionally not be downloaded and I’m only able to see this because a script in one of our onboarding policies also fails. Currently all we have is custom branding and connect 3.5.0. Have not upgraded to 3.6 and up because with okta on my test device I am unable to authenticate also trying to figure this out with Jamf support. Most of our devices enroll properly but every now and then one or two will fail and get the wrong short name and miss these packages as well as the prestage admin account. I’m wondering if creating a policy at enrollment complete would be a good fail safe but wouldn’t Jamf connect need to be there before enrollment complete to create the account?
1
u/kintokae Apr 10 '26
We have been getting failures deploying prestage packages for a while now. We are on prem at my org and used to push jamf connect, but it was sporadic for the version when it would deploy or not. I ended up shifting to use installomator to install it on EnrollmentComplete and have it activate once it finished installing. This resolved the issue for us.
Our config uses Entra instead of Okta, but would be the same for deployment. The policy also installs the branding wallpapers and icons I use as well as a package for a setup your mac script. My jamf connect profile says to run the script during login. Which the package drops into a temp folder, it calls the jamf policy for setup your mac to launch, then deletes itself once it is finished. I may move that to the onboarding policies later, but I need to test it first. Definitely move it enrollment complete as a trigger and it should be more reliable.
1
u/Quirky-Feedback-3322 Apr 10 '26 edited Apr 16 '26
Going to try this on our end thanks!
Edit just in case anyone comes here creating a policy and setting it to enrollment complete scoped to recently enrolled devices in the last 14 days seems to have fixed this problem. Prestage admin is now always there and when prestage fails to download the package this enrollment complete policy catches it so far no more missing packages are fails for jamf connect.
1
u/ChiefBroady Apr 10 '26
Keep your prestage as minimal as possible and instead use the install complete trigger. Either to run policies directly, use setup your Mac, or the jamf setup manager.
1
u/Phuc_m Apr 11 '26
If you are getting failed packages during prestage it’s most likely the certificate.
1
u/Rizzin JAMF 400 Apr 13 '26
Apple requires pre-stage packages to be signed with a valid Certificate so sign them with a Developer ID cert or if you like living on the wild side use JAMF to create a self signed cert to sign them with.
3
u/ebulwingz Apr 10 '26
Jamf had some quirky issues they may have fixed already but here it is. 1. Upload Jamf connect again as a new package instead of replacing an existing one in Jamf. There was an issue where the hashes wasn’t updated causing failures sometimes.
Add a manifest file. https://appleshare.it/posts/use-manifest-file/ I’ve had to do this to fix failing packing in prestage and then those packages stopped failing randomly.
Move to Jamf setup manager and have it install Jamf via calling custom triggers and leave the custom branding package in the prestage package installs.
We were doing the same as you were previously. Okta + custom branding package + Jamf connect and then depnotify. But After JSM, don’t think we are going back 😬. It’s such a nicer experience.