Applixure release notes for 2019-02-11

Since the last release notes, we have brought to you the following new features, changes and enhancements to existing functionality:

  • Issue occurrences heatmap is now shown

    Device and Software issue event history now shows a heatmap underneath the calendar view which plots all the shown issue events for the past month (sans not responding conditions) on a 24 hour timescale based on the event's occurrence starting timestamp's hour component. 


    This information can help to get better understanding on what time of the day are most issues concentrating on - if there are any patterns to them - augmenting the weekly -based temporal information from the calendar view above.

    We also now provide these timestamps in the Connect API data for your own analysis purposes for most of the issue history events.

  • More details available for high-memory conditions

    We have added capability for Applixure Agent to track which applications/processes and software products (if any) those applications relate to are consuming most of the physical  and virtual memory during detected high-memory condition. This information can help you to further pinpoint those applications and/or background processes that might potentially be the main reasons for high memory usage on certain devices.


    Please note however, that presence of application in the list during high-memory usage does not necessarily in itself be a problem or indicate any problem as such, as the situation might be as intended if the application's use case is such that it needs a lot of memory. Reported processes and applications are just the ones that - in relative to other processes - use the biggest share of the memory.

    This data is also now available through the Applixure Connect API.

  • Issue history now shows when Agent has been last seen

    In the Agent device's issue event history for the past month and if Applixure hasn't had any contact from the said device for some number of past days, the days of no data are now indicated with light shading so that is more clear if the issues have actually stopped happening or if it is only due to Agent not reporting anything at all.


  • New user preference in Applixure Web UI

    There are now two new user preferences in the Applixure's Web UI that you can configure from Settings -> User account settings -> Change settings.

    First one of these settings allows customizing the export file format when exporting devices or software from the list view. Previously, it was only possible to export in CSV format (i.e. comma separated values) but since the parsing of the CSV files can be locale-dependent especially when using Microsoft Excel, we now provide direct XLSX (i.e. Excel worksheet) export format for better compatibility for Excel-based workflows. This setting is now the default, and if you rather would like to continue exporting in CSV format - such as when reading in exported data using some more generic tool - you will need to change your puser references to use CSV.

    A second setting is to select a specific timezone by which to display timestamps in the Applixure UI. By default, all the timestamp -based data in the Applixure is stored and provided in UTC timezone to allow correlation of timestamps across multiple timezones - such as in the Connect API data - but sometimes it is desirable to view those timestamps in the UI using the actual timezone the devices are physically locating in. For this purpose, you can now select a timezone setting in your user preferences and the Applixure UI will show timestamps converted to use that timezone instead of the by default UTC.


    Please note that this setting ONLY concerns the display of the timestamps, and will not change the underlying timestamp data from the neutral UTC format. As of now, these displayed timestamps can be found as Agent's last seen timestamp and the issue event history's heatmap's plotting of the event starting time per each hour of the day.

  • Updates for Applixure Mac Agent

    We have added the tracking of powered-on time and user logon utilization to the Mac Agent to bring it into more feature-parity with the capabilities of the Applixure Windows Agent.

    Alongside with the new capabilities, Mac Agent's inner workings have recently been heavily optimized to further reduce its CPU and memory footprint on a machine.

  • New Windows 10 servicing ring names

    For newer Windows 10 releases after Microsoft changed its terminology from the old "Current Branch" and "Current Branch for Business" to "Semi-Annual" and "Semi-Annual Targeted", Applixure will also now report these servicing rings using the correct terminology. For any older Windows 10 releases still in use in Agent devices, the old terminology is maintained to correspond to the at-the-time usage of it.

    Similarly, terminology for long-term servicing (LTS) releases of Windows 10 are changed starting from 1809 release (i.e. "Windows 10 Enterprise LTSC 2019") where the new term is "Long-term Servicing Channel" instead of the previous "Long-term Servicing Branch".

  • Filtering of device & driver problems for known VPN adapters

    Previously, in the device & driver problems reported by Applixure for Agent device, VPN adapter devices such as Cisco AnyConnect etc. could be reported as having problem as being "User disabled". Since the default operating mode for VPN tunnel adapters is such that they are disabled as device by the VPN application when not in use, this could cause false alerting for normally operating [virtual] devices.

    Applixure now ignores any device problem reported by Windows as "User disabled" for devices that are detected by the type or by name as VPN adapter, and will not raise these into device & driver problem list. 

  • Agent harddisk data in Connect API

    In the Agent information provided in the Connect API, list of harddisks detected for the device are now included alongside with firmware version and serial numbers (if known). This information is not currently provided in the Web UI. 

  • Fixes for miscellaneous technical issues and minor functionality improvements.


Have more questions? Submit a request


Article is closed for comments.
Powered by Zendesk