Knox Guard 1.23 release notes

KG Rest API error return improvements

API calls can only be made to device in a specific state. However, too many “device_state_invalid” errors have been encountered, and each time such an error occurs it’s difficult to determine a device’s accurate status to properly troubleshoot the problem.

To resolve this issue, rather than calling “get device info” to obtain the state, the Knox Guard server will return the device state whenever a “device_state_invalid” error is triggered.

Disable blink reminders for scheduled intervals

Customers have reported blink notifications can bother their device users, especially at night and on weekends, and have requested the ability to disable them for specific configurable periods.

With this release, customers can now disable blink reminders for a configurable period of time without stopping or starting the blink reminder again. During the time blink reminders are disabled, they will remain as notifications.

Phone number or email address required for contact information

With this release, either a phone number or email address is required when setting a blink reminder, lock (automatic lock), offline lock (warning), or SIM control lock. With this requirement satisfied, a contact resource is now available if the device is rendered inoperable due to a device or SIM control lock.

Last Seen parameter added for requesting customers

A LAST SEEN column is now also available as a display option within the Knox Guard Devices screen. This column displays the last time a listed device IMEI/SN connected to the KG server. Both the Last Seen and Carrier fields are gated behind a feature flag so they can only be enabled for requesting customers.

For more information on enabling this feature, contact your Knox Guard Samsung admin.

Re-defined device log policies

This update does not represent a change to existing Knox Guard statuses, and maintains the use of ~ing for various event states. However, sent has been added to the event description to better distinguish what we sent clearly. For example, Unlock device has been updated to Unlock device sent. Additionally, there has been so many device errors showing in device log that it becomes confusing for the customer to discern legitimate errors from non-essential internal errors.

To remedy this confusion, the Knox Guard team has reduced the number of unnecessary internal errors and now only maintains valid errors interpreted as important to users.

License usage dashboard improvements

To date, when a license is added into Knox Guard and is activated the same month, the license utilization count within the Knox Guard Dashboard does not properly increment and accurately reflect the update.

To remedy this situation, the Dashboard has been updated to accurately reflect license activations within the same month they were added into the Knox Guard console.