Omnilert Desktop Alert can track which PCs have/have not displayed an alert and, optionally, which PCs have had a user click "cancel" to acknowledge the alert on the screen.
This information is returned as delivery "Status Codes".
In logs and exports from Omnilert, these codes translate as follows:
|Alert Sent||(Not acknowledged / Display not started) - This could mean the PC is not online, app not installed, or just hasn’t polled the server yet.|
|400||Alert Start / Displaying||The message is playing or starting to play on the PC.|
|401||Acknowledged||The message was dismissed by a user. (They closed or acknowledged the message)(OPTIONAL)|
|402||Expired||The message played on the PC until it expired. (Not acknowledged.)|
|403||Alert cancelled||The alert was canceled by an admin in Omnilert before or during display.|
|404||Alert replaced||The message was replaced by a new message sent to the PC.|
|405||Message Unread||The PC never retrieved the alert from Omnilert's servers.|
The information in the message history can help track down potential issues with client PCs.
For example, if a PC regularly returns "405" ("Message Unread") for desktop alerts sent, it may be offline (turned off), have had the client app removed/uninstalled, or having difficulty reaching Omnilert's servers to retrieve alerts.
A PC must have the client app installed, running, and able to reach Omnilert's servers to display alerts.