What happened to Self Service Notifications? I get tons of notifications in Self Service for apps that are configured in Patch Management, saying update available, but the latest version has not been uploaded yet. We only want the notification when it is available. Is this a new "feature" or am I missing something?
We have the exact same problem. Jamf introduced a new "improvement" to the Self Service UI in 10.24.1. but it has been anything but that for us. Old notifications hang around in the Notification pane forever and you can even toggle them on and off which serves no purpose. It causes a lot of confusion with our users who think they have an update to install but there is no "Update" button present. We have an open ticket for this problem but no resolution yet.
I'm seeing the same thing. Also even when notifications are cleared out, they come back within a day or two, even when no new updates are published. I opened a ticket with Jamf about it and we're testing a few things, but they suspect it's a product issue. If you're seeing the same thing you should open a ticket so hopefully it can be fixed in a future release.
Thought I would share in case anyone else comes across this.
Its a known product issue
|PI-009167||Self Service may incorrectly display notifications for old patch policy updates.|
We are having the same issue.
What I am testing right now is disabling the "Enable Reminder Notifications" under User Interaction page of the Patch Policy. I have only started doing this for apps that keep appearing in Self Service for about a week or 2 now but so far it appears to be working better at eliminating those false update notifications.
I turned this setting off for Chrome, Firefox, and a couple others that were constantly being listed even after being patched and so far I have not seen them appear again after clearing them out.
I will try to give an update in a few weeks to see if they show up again.
Hard to say exactly if it was an update to Jamf Pro or the result of me disabling that option. However, after disabling this option I did notice the duplicate update notifications in Self Service no longer appeared, which I believe was also resulting in those false update prompts after the apps were already updated.
We have since switched to an external patching system. We still use Jamf to manage our macs but switched patching to Desktop Central as its more automated for 3rd party applications and we also use that to patch our Windows machines as well. This was deployed just prior to Jamf finally supporting automatic updates on some 3rd party apps of course :/.
Gotcha! Thanks for the info!
I went ahead and disabled the whole section "Display notifications for the patch policy"
and noticed that it actually seems to have resolved the issue. I still get prompted to update when theres an actual update but I don't get those annoying "update available" message with no update button.
I think this may be the fix.
This is an example of my set up prior to switching to Desktop Central.
Our notification bubbles actually stopped working properly, probably macOS update breaking things again. So I actually had a script that would launch Self Service once every day in the background without actually opening the window and have it on the Dock. This would then display the number of updates available if any on the SS icon so users were aware. But also you will need a script to then close the app or else the next time it runs it will pop the window up which can cause an annoyance to some ppl. I work for a development company and some of our devs can get irritated when things pop up on them randomly while they are coding.
I tested many things and that was the best end user experience I could come up with.
Yeah, seems like the whole notification system in Jamf has gotten worse with later macOS updates, its a little irritating. I just have a policy set up and under files and processes its running this command:
open -a "Software Center" --hide
Then to close the app I run this command:
osascript -e 'quit app "Software Center"'
On the close command I have it scheduled to only run within a cpl hour window at the EOD. This prevents it from closing early in the morning or mid day in case machines check in cycle get out of whack.
I have created a workaround that seems to be working
Issues for us has been when we directly assign or target All computers in the scope of the patch policies.
So we started using Smart groups for the app and version we are applying the patch to
We need to update Zoom.us to Ver 5.11.10 (10279)
So for first we create a smart group for all computers not yet at that version
then add this to scope of the Patch policy
User is notified of the update and once installed they are automatically removed from the smart group, thus not getting any more notifications.
Hope this helps.