Jamf Pro 10.4 and Quick Add package Bug

The big question now is for people who had the old quickadd/enroll run that had the missing line, do we have them re-enroll or rerun quickadd or just push that quickfix script out above to all folks?

@obing Just run the script above by @ubcoit and have it run once on each Mac.
It should not hurt anything and would fix any that need it.

Thanks to everyone who confirmed PI-005852 was fixed, but not called out in the release notes.

The release notes for 10.6 have now been updated.

Thanks again!

Are we confirming this is fixed? @kricotta seems to still be having issues with it, per his post here

I have two JSS' working fine on 10.6.0.
No idea why his isn't. You'll have to try your own to see what happens I guess.

@kricotta same here. I can confirm the script corrects my bug issues on current machines and the new 10.6 recon builds new quickadd packages with correct postflight scripts. I've personally verified the old and new quickadd packages from 10.5 and 10.6.

Having more issues with the QuickAdd package for enrollment. Really really annoying. I can enroll OK using URL, but back to having "unmanaged" Macs if I use a new QuickAdd.
Re-opened my case with Jamf.

I'm trying this on Mojave beta and wasn't able to enroll via the URL (which doesn't seem to visibly download a quickadd package - it just adds the policy certs and goes from there...), so I upgraded to 10.6.0 and still can't enroll my machine. I thought this might have been a mojave issue, but it looks like it's more of a Jamf Pro issue then? I'll try the script by @ubcoit and see if making the /usr/local/bin folder and chown'ing it to root:wheel helps.

@isterling.goaaa - that's what I'm seeing here on 10.13.6. Never downloads the QuickAdd package using the URL.
If I make a QuickAdd, it shows up "unmanaged" and it isn't managed.
Also on JSS 10.6.0. I have a case open with Jamf, please do the same so they put some attention to this mess.

I just realized that the script from @ubcoit won't work for me. What I'm observing is that aside from downloading the certs, nothing else happens. No files are downloaded and no /usr/local/jamf folder is created, so there's nothing to symlink.

To clarify, I'm experiencing this issue on my QA (non-production) JAMF Pro server, which is running 10.6.0.

My production JAMF Pro server, which runs 10.3.1, is not exhibiting this behavior.

I have an issue where the computer enrolls, but it shows up on the JSS as [No Name]. Yet the computer has the correct name when i check the computer.
Yet, we where using it yesterday with no problem... it just stop working.
This is a big problem because of how we assign policies, config profiles and software.

This really needs to be fixed.

I hope you guys @steve117 and @isterling.goaaa have opened cases with Jamf?

@scottb I haven't yet, but I will today.

So ... I filed a ticket and JAMF closed it as a known issue. The "work around" is to create a quickadd package which doesn't work half the time.

I've added a fresh Mojave-installed mac to my QA environment running JAMF Pro 10.7.1 and after installing the CA Cert and the MDM Profile that get fed to my system by the web server, nothing else happens. You'd figure they'd've fixed this by 10.7.x, no?

@isterling.goaaa - lovely, right?

@scottb So there's a solution to that, actually, and it works quite well:

https://path.to.jss:8443/enroll/?type=quickadd

This will tell the JSS that you want a quickadd package instead of the automatic push via the browser. I've tested it in a couple of cases in my QA environment and it seems to work. I still have a little more testing to do, but for now this seems to be the fix.

Special thanks to the JAMF support engineers for giving me this tip.

@isterling.goaaa Thank you so much for sharing! This solved it for me. I spent probably 2 hours troubleshooting with no success.