Jamf App Catalog Patch Management Dialog Prompt

[_aDiedericks]

Hi there,

Jamf App Catalog is great at patching applications. The only caveat is the method that it uses to communicate with the end-user that an update is pending. Most of our users ignore or are unaware of the notification from Jamf App Catalog when a new update is pending and as a result complain of their apps getting abruptly closed. This is compounded by an ongoing issue of inconsistent notifications (an issue that has been open for a couple of years).

Is there a way to mitigate the above issue by maybe a passthrough of a notification to a prompt or dialog box that the user can interact with? All my attempts at trying to resolve this issue is cut short by there being no direct feedback on the local machine that is recording Jamf App Catalog interactions with the local machine i.e a log that can be leveraged to base notification triggers on a Jamf Pro policy and Notifier App.

I thought to leverage IBM Notifier for this task as it would be ideal. Except that once again we would need to be able to reference a trigger based on log data from Jamf App Catalog that doesn't seem to exist on the user's local machine.

If you have engaged with this issue and found a workaround please let me know.

[jamf-42]

deploy the config profile - set the 'end user experience' as required.. works for nearly all the apps.. nothing is ever closed without notification and even then you can apply a grace time. 

[_aDiedericks]

The core premise is to improve the user experience by leveraging an 'impossible to miss' dialog box similar to IBM Notifier. In our environment, the toast notification in the right top corner is just not working for everyone.

[AJPinto · Accepted solution]

Jamfs App Catalog uses Apples Managed App Distribution toolset which is a part of the MDM framework. Jamf must use Apples notifications, and they cannot customize this. If your users cannot or will not pay attention to Apples toast notifications, there is not really anything else you can do unfortunately. 

[_aDiedericks]

Thanks for providing a direct answer to this. Our comms with Jamf support left it open ended. Your explanation is very clear.