Custom End-User Notifications

Follow

 

Custom Notifications is available today as a beta feature to Full plan subscribers. If you are interested in early access to the feature, please contact us at support@automox.com.

Custom Notifications provide three new options when enabled: Do Not Notify UsersNotify Before Patching and Rebooting, and Notify Before Rebooting. Each can be used to tailor the end user notification experience.

  • Do Not Notify Users - No end user notifications will be sent for any patching event

  • Notify Before Patching and Rebooting - End user notifications will be sent out for all patches, including those that do not require a reboot. Custom messages can be set for each patch type in place of Automox's default message.

  • Notify Before Rebooting - End user notifications will only be sent out for patches that require a reboot, with an option for a custom message in place of Automox's default message.

 

Custom Messaging

With Custom Notifications enabled, you can set custom messages for both patch and reboot operations depending on the notifications that you have selected. This allows more flexibility in informing end users of what is being patched, the severity of the patch, or your expectations for regular patching.

By default, Automox’s own patch messages will always be sent, unless a custom message is provided. If the field is left blank, default messages will be sent.


custom.png
Patch and reboot message options

To set a custom message for patching and/or reboot, fill the textbox with messaging of your choosing. Messages can be up to 150 characters, can contain Unicode characters, and will display in Windows and Mac default notification windows.

 

Screen_Shot_2018-09-27_at_12.15.36_PM.png
Windows

justmacnotificaiton.png

MacOS

 

Remediation time for the patching window can also be optionally provided to the end user by using the `{{remediationTime}}` tag. This tag will automatically fill in the patch window for the policy, giving the end user more context around when to expect patch or reboot operations.



Custom Deferral Times

You can set up to three deferral times for notifications, allowing end users to push off a patching operations for a number of hours. By default, users will be able to defer for 1, 4, or 8 hours. You can override these settings to provide different time intervals based on your needs.

To set custom deferral times, fill in the three boxes for the first, second, and third deferral options. All numbers will be represented as hours, only integers are accepted, and the maximum single deferral time is 24 hours. You can set up to three deferral times, or fewer if you only want to offer end users 1 or 2 deferral times.

 

Screen_Shot_2018-09-27_at_12.27.59_PM.png

All options provided are presented to the user before a patching window begins.

image.png

Windows

Screen_Shot_2018-09-26_at_7.49.44_PM.png

MacOS

Custom Number of Deferrals

You can also set a custom number of deferrals for notifications. When set, the end user be able to defer patching up the provided number of deferrals. On the last possible deferral, the patch will be applied as guided by the policy.

If a user misses the patch notification, their system will be patched and/or rebooted 15 minutes after the missed notification.

To set the number of deferrals, fill in a number in the “Number of Deferrals Allowed” field. The default number of deferrals available is 3. You can set as few as 1 deferral or as many as 10.

Screen_Shot_2018-09-27_at_12.27.59_PM.png

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.