Introduction
This document has been written to guide Mac Administrators that are using our Auto-Update for Jamf service through the process of manually creating the Notifications profile.
We would always recommend using the profile provided by your implementation engineer, but this guide also accommodates for if there is a specific need to create one using the Jamf Pro UI.
Process
Step 1: Open your Jamf Pro web interface and navigate to "Computers" > "Configuration Profiles".
Step 2: Create a new Profile with a name and category that matches your own internal process and standards.
Step 3: Add the Notifications Payload.
Step 4: Fill in the details as per the below:
- App Name: [Leave Blank]
- Bundle ID: uk.co.dataJAR.NotifierNotifications
- Critical Alerts: Disable
- Notifications: Enable
- Banner alert type: Temporary
- Notifications on Lock Screen: Display
- Notifications in Notification Center: Display
- Badge app icon: [Not managed]
- Play sound for notifications: Enable
Step 5: Click the "Add" button again to add another Notifications payload and fill in the details as per the below:
- App Name: [Leave Blank]
- Bundle ID: uk.co.dataJAR.NotifierAlerts
- Critical Alerts: Disable
- Notifications: Enable
- Banner alert type: Persistent
- Notifications on Lock Screen: Display
- Notifications in Notification Center: Display
- Badge app icon: [Not managed]
- Play sound for notifications: Enable
Step 6: Click the "Add" button a final time to add a third Notifications payload and fill in the details as per the below:
- App Name: [Leave Blank]
- Bundle ID: com.googlecode.munki.ManagedSoftwareCenter
- Critical Alerts: Disable
- Notifications: Enable
- Banner alert type: Temporary
- Notifications on Lock Screen: Display
- Notifications in Notification Center: Display
- Badge app icon: [Not managed]
- Play sound for notifications: Enable
Step 7: Save this profile and deploy it out to devices running macOS 10.15 or newer and with a UAMDM Approved status. Deploying this device to earlier macOS versions will result in the settings not being honoured when the device is upgraded. Attempting to deploy this to a non-UAMDM Approved device will result in the settings being ignored or the MDM server refusing to deploy the profile.
Need further support?
Automate. Simplify. Succeed. If you still require assistance with us or have any further questions, please raise a ticket with our support team.
Alternatively, please see our frequently updated knowledge base articles for reference.