Skip to main content

Ver. 11.5.0.2 Official Release

We are excited to announce the official production release 11.5.0.2 of DeskAlerts! Following a beta phase, we gathered valuable feedback from our beta users, allowing us to make targeted improvements and ensure a more stable and efficient experience. This release incorporates these enhancements to address the insights and suggestions provided, improving both functionality and the user interface. We appreciate the active participation of our beta customers, whose contributions have been instrumental in refining our product to better meet your needs.

New Features​

Enhanced User Experience for Scheduling Wallpaper, Screensaver, and Lockscreen Delivery

Version 11.5.0.2 introduces an updated UI for scheduling Wallpaper, Screensaver, and Lockscreen. You can set start and end times separately or choose "Display continuously" if unsure when to stop. This enhancement offers more flexibility and ease of use.

Added Azure AD (Entra ID) Method to Mixed Devices with AD Credentials Only

Administrators can now specify that end-users outside the domain can register using Entra ID (Azure AD) credentials in addition to AD credentials, without enabling other authentication methods. This enhancement provides greater flexibility in user authentication while maintaining security protocols.

Increased Default IIS Limits on Concurrent Connections and Request Queue Length in DeskAlerts Server Installer

This change reduces the time it takes to successfully roll out DeskAlerts for customers with large audiences.

Resolved Issues​

  • Logging out of the DeskAlerts mobile app skewed statistics for recipient alerts.
  • Deleting a user's history in the DeskAlerts client application triggered a physical removal of alerts in the client application database.
  • The DeskAlerts Client icon in the Windows system tray menu would reappear after being configured as hidden.
  • Default images for emergency buttons were not included in the release packages.
  • Instead of survey content, the client app showed an error: Exception of typeDeskAlerts.Core.Exceptions.ProxyBadStatusCodeResponseExceptionwas thrown in sent surveys.
  • Clicking a preview item in the actions (...) menu in the RSVP alert template list didn’t bring up a template preview.
  • "Free Answer" responses in surveys, quizzes, and polls were missing in exported reports.
  • Voting statistics in surveys were calculated incorrectly.
  • Text in Arabic was displayed in an obscure font in the history view of the client application.
  • The default skin was not available when creating or editing a ticker.
  • The "Enable user feedback" option did not appear in the sent scrolling ticker.
  • Scrolling ticker speed was affected by the alert body text size.
  • The skin search filter did not work on pages beyond the first one.
  • Some alert text formatting was ignored when rendered on client apps.
  • Duplicate user records appeared in exported reports for alerts.
  • Sound in video alerts did not stop when the Acknowledgement option was enabled.
  • The "Alert Statistics" widget displayed incorrect information.
  • Edited pop-up alerts could not be saved as drafts.
  • Sending alerts exclusively to either mobile or desktop devices delivered alerts to all device types.
  • Expired wallpapers continued to be displayed as a solid background.
  • Alert "position" setting for emergency alerts defaulted to the bottom right.
  • A blank alert delivery issue was caused by sub-optimal database queries in dashboard widgets.
  • The “Oops! Something went wrong unexpectedly” error appeared after a successful login to the dashboard with Azure AD credentials.
  • Azure AD sync failed with the error "Object reference not set to an instance of an object".
  • Logging into the web interface (dashboard) was interrupted by the “Value cannot be null. (Parameter 'accessToken')” error.
  • Azure AD synchronization didn’t pick up the primary domain for synchronization by default.
  • A domain did not appear in the domain list after a successful synchronization with Azure AD.
  • The open rate shown in the Wallpaper reports section was incorrect when the corresponding alert was sent on a schedule.
  • Exported reports showed UTC server time instead of the user's local time in date/time fields.
  • The Acknowledgement button in alerts brought up a warning "Your Response was Not Recorded.
  • A publisher with a restriction to a specific audience in their user policy could send an alert to "everyone", resulting in a broadcast to the entire connected audience.
  • Resolved some cosmetic UI and localization issues.

System Requirements​

The minimum requirements are 8GB of memory, followed by an additional 2.6GB for every 10,000 connections.

Number of ConnectionsCPU (cores)RAM (GB)
less than 15,00048
15,000 - 40,000816
40,000 - 100,0001632

CPU requirements​

Intel Core i5-13400 | AMD Ryzen 5 7600, or an equivalent.

Storage Considerations​

Application Server Storage Requirement: 300 GB (for the first year)

SQL Database Server​

Storage Requirement: 200 GB (for the first year)

Note: These estimates are based on projected usage for the first year. Storage needs should be reviewed periodically as data grows.

Horizontal scaling considerations​

While installing the DeskAlerts Server, choose a number of сonnection services followed by an additional connection service for every 7,500 connections.

To ensure secure communication, it is necessary to acquire a valid SSL certificate and subsequently install it on your server.

Internet Information Services (IIS) configuration necessitates a default site binding for HTTPS on port 443, utilizing the installed SSL certificate.

DeskAlerts Application Server requirements​

DeskAlerts Desktop Client Applications requirements​

DeskAlerts Mobile Client Applications requirements​

  • Android: Requires Android 8.0 or later
  • iOS: Requires iOS 14.2 or later

Known Issues​

  • Intermittent issue with the CEF framework crashing on one of our test Mac machines.
  • When a publisher procrastinates and clicks the send button after the date/time for the first scheduled alert has passed, we send the alert but mark it as not received in the statistics report.
  • CSV/XLSX report exports for recurring alerts show recipient responses to the last alert only. Note that this issue doesn’t impact surveys.
  • Emergency alerts initiated from client apps show the name and contacts of the person who created the emergency alert template, not the person who initiated the alert.