Posted on 08-05-2019 09:18 AM
Started yesterday on only certain machines. Doesn't seem to be causing issues when clicked off. Cannot find anything reasonable in logs about what it is attributed to.
Posted on 08-05-2019 09:45 AM
We are seeing this popping up constantly on a 10.13.6 machine (build 17G5019) and have a call from another user that sounds like it might be similar.
Posted on 08-05-2019 09:46 AM
jamf's new restricted software ui
https://macadmins.slack.com/archives/C19MR7EM9/p1564858232221600?thread_ts=1564847604.216900&cid=C19MR7EM9
Posted on 08-05-2019 09:54 AM
Thanks @Garci4, much appreciated!
Posted on 08-05-2019 10:06 AM
In our case it appears to be a restriction we have for Siri.
Posted on 08-05-2019 10:55 AM
Our computers are all in Mojave and this popup was driving me crazy since this morning, thanks for the information @Garci4 .
It was our Chrome update restriction.
Too bad jamf let this kind of bug pass to release...
Posted on 08-05-2019 11:23 AM
I've read on Slack that the fix is in Jamf 10.15 and they couldn't get it ready in time for 10.14. This is a show-stopping issue for users and Jamf should NEVER have allowed the "blank box" bug to ship!
Posted on 08-09-2019 02:48 AM
i'm not a slack user, and can't read what's posted there. is the work-around to not have any software restrictions?
Posted on 08-09-2019 04:16 AM
@lkowitzbmi There isn't a lot more information on slack than here. About your question, I guess it depends the kind of software restriction you are applying.
In our case, we changed the Chrome plist with a config profile to disable its software updates instead of using a restriction policy. If you want to prevent the launch of a given application, I don't think a regular policy would work well.
You might have to write and deploy a local LaunchAgent or LaunchDaemon running a script that permanently blocks a given app. Not so simple in other words. Maybe someone else here might propose a simpler way to do that ?
Posted on 08-09-2019 09:51 AM
Also see https://www.jamf.com/jamf-nation/discussions/32879/weird-pop-up
...specifically the comment from @diradmin with a PI #.