Applixure release notes for 2021/Q1

In the past few months, we have brought to you the following new features, changes and enhancements to existing functionality:

  • Improvements for Alerts & Warnings visualisations in dashboards

    Active Warnings and Alerts in the main dashboard views (Devices, Software, Issues and Use) are now by default shown in collapsed state, making the screen more easier to read. You can expand the Warnings or Alerts showing the actual list of them by clicking on the bar.

    Additionally we have introduced trend history for the Alerts and Warnings that is automatically shown underneath the active list for all of those Alerts and Warnings that are either currently active, or have been still in the past couple of weeks. The trend line shows the number of devices that are associated with the Alert or Warning, making it easier to see if particular issue is being increasing in your device fleet or decreasing. This is also true for software -related Alerts and Warning, which also are plotted based on the devices, not number of software products in those Alerts or Warnings.

    The graph automatically hides the trend lines for those Alerts or Warnings that are no longer in active state, but you can easily show them by clicking on the label underneath the graph - ones in grayed out text are currently being hidden from the graph.

  • Automatic tagging based on OU membership for Windows Agents

    Automatic tagging functionality for Windows Agents has been expanded with possibility of creating automatic tags for devices based on their Organization Unit (OU) location in the Active Directory environment.

    This feature allows you to easily see or filter the agents on the Applixure Web UI based on the OU membership, as the automatic tags will keep up to date if the device object is moved within AD's OU structure.

    You can download the updated Group Policy Template allowing you to enable OU auto-tagging from our Help Center article: and read more about configuration options from Help Center article on automatic tagging:

  • Support for enforcing two-factor (2FA) authentication

    While Applixure users have been able to enable two-factor (2FA) authentication for themselves at the discretion of the user itself, Applixure now supports enforcement of 2FA being enabled on per Applixure Account or Environment -basis.

    This makes it possible to ensure that all of your Applixure user accounts are being extra secure for logon and that no user accounts may access your Applixure environment's data without having that extra verification in effect.

    2FA enforcement can be enabled in the Applixure Account's general settings under Settings / Account settings (access is restricted only for user accounts having Full account administrator -privileges for the Account), and turning Require two-factor authentication for user accounts owned by this account -option on under Security and restrictions -section:


    Enabling this setting will require all Applixure user accounts owned by the Account to configure and turn on 2FA for their user accounts, if they have not not done so already. Please note that this setting only affects user accounts owned directly by the Account itself, not for any user accounts owned by the Environment(s) owned by the Account.

    Similarly for Applixure Environments, identical settings exist, accessible under Settings / Environment settings (access is restricted only for user accounts having Full administrative -privileges for the Environment).


    For Environments, you can enable the enforcement of 2FA for user accounts owned by the Environment just like with the Account's setting, but you can also enable the enforcement for all user accounts just having the access to the Environment. This means that if you have authorized user accounts from elsewhere in the Applixure system (another Applixure user organisation for example) or have user accounts having inherited access privileges from the Account owning the Environment, those users can also be enforced to enable 2FA before they can access this particular Environment.

  • Support for Web -based applications

    Unlike traditionally (locally) installed software products and applications, web -based applications that are used through some client application - typically an Internet browser such as Firefox, Edge or Chrome - cannot be found and tracked for usage automatically by Applixure.

    For this reason, we have introduced a new feature by which these kind of applications can be included in the software inventory in your Applixure environment just like any locally installed software found on the PCs. The feature is based on creating specific profiles for each web application on per-environment basis you would like to include and Applixure Agents on that enviroment will automatically start doing tracking for them.


    As Applixure doesn't go inside any client software being used to access these web applications and must operate from the outside, there exists some limitations which web applications can effectively be tracked by the Applixure Agent and currently web application usage tracking is only available for Applixure Agents running on Windows.

    You can read more about web application profiles and creating them from our Help Center article:

  • Critical system services -related issue reporting

    Applixure Agent now detects and reports on service -related issues for selected number of Windows' built-in services that are important for well-functioning Windows system.

    These detected issues are categorized for three different type issues:

    • Service being disabled
    • Service failing to start
    • Service having other issue(s)

    If any of these issues are detected for an Agent, they are displayed on individual Agent's screen:


    You can read more about critical service issues from our Help Center article:

  • User profile information for user-installed products

    Previously, Applixure was only able to show that particular software product on Agent device was installed in user context (a green icon next to device name in the software -specific screen) or - more recently - in the popup tooltip shown when placing mouse cursor over software's name in the Agent -specific screen, under Installed software & usage -section, showing the actual product version(s) found for the software.

    We have improved this information so that the tooltip now also shows the user name/user account name for those instances that are installed in user context.
    This makes it easier to find possible dormant user profiles on a device having outdated software version installed into user context (profile), or which users have older versions of the same software installed into their profile than what is deployed also on machine-wide context on the same device:


  • Mass-import of user-settable software attributes

    It is now possible to import user-settable software attributes through Settings / Environment settings / Bulk operations -page using custom CSV file.

    Importing these attributes on per environment -basis makes it possible to set required attributes (such as Approval -status) for multiple known software products in one go instead of needing to change them one-by-one through individual software asset's screen.

    Please note that setting attributes in this manner will only set the attributes for matching(per software name [and version]) and found software products at the time of the import operation, but if new software products appear later on in an environment, these will not automatically be matched post-import. You then might want to do the import on a regular basis if the churn in the software inventory composition also changes regularly.

    You can read more about web application profiles and creating them from our Help Center article:

  • Number of fixes for miscellaneous technical issues, minor functionality improvements and visual enhancements
Have more questions? Submit a request


Please sign in to leave a comment.
Powered by Zendesk