a week ago
This is honestly totally baffling me. Dock has been set with dock items using a configuration profile in our environment. To this day, these profiles are still configuring the dock correctly to newly deployed machines, with the dock items we set initially. Today I went to add a dock item only to see NONE of them listed. It's so bizarre. This very configuration profile is still setting dock items in on a test machine - but again, this policy seems to have NO dock items listed. Anyone seen this? See screenshot.
a week ago
a bit of a long shot, however did you have some config profiles setting the dock up and then deleted them, while the the profile were still scoped? if so they can stick around longer then you intend even after deleted/ If so they may be listed as orphaned profiles in the management console, as jamf tries and fails to sort them out.
If so you can create a config profile with the matching ID of the orphaned profile, without any set or scoped and then jamf will clear them out. If you don't remember the IDs, jamf support can help you out. hope that helps.
Tuesday
I am experiencing the exact same issue. Thank you for documenting it so clearly. The good news is that it is not affecting current Dock Payloads, but the bad thing is you can't see anything to make any changes. I put in a support case with Jamf Pro and hopefully they figure out the issue soon.
Wednesday
Hello - so, really fascinating - I think it is down to a display bug in Jamf cloud - Here's what I discovered. If I go to edit my dock items in my policy and ADD and SAVE a "blank" dock item - after a beat - POOF they all suddenly appear again!
I have to do this every time. I have an open Jamf ticket and will be reporting this today (as of 12/18/24)
Wednesday