AppClarity 5.2.300 release notes – last updated

These release notes contain late-breaking information about AppClarity. For the most up-to-date information, see the online release notes and known issues.

New features

This new release introduces the following enhancements:

  1. Pre-flight reclaim report.
  2. Custom SCCM Uninstall targeted deployment for user, device or both.
  3. Custom SCCM Uninstall for optional policies.
  4. Addition screen to display unidentified executables to enable you to review them and add them to your site-defined Catalog if necessary.
  5. Support for SQL 2017 from AppClarity 5.2.300.14.

AppClarity and the distributed transaction coordinator

If your database server is hosted on a different machine to the AppClarity service, you must enable the distributed transaction coordinator (DTC – a Windows sub-system that allows transactions to be coordinated across multiple machines). Failing to do this results in the AppClarity service not starting – an error message is logged to indicate the issue.

With 5.2.300.11, the dependency on DTC is removed. AppClarity service will start even if DTC is not running. 

AppClarity release history 

5.2.300.14  Web release (17 Jan 2018)

  • Custom Configuration Manager uninstall targeted deployment for user, device or both

  • Custom Configuration Manager Uninstall support for optional policies

  • Additional screen for unidentified executables

  • Support for SQL 2017  Web release (05 May 2017)

  • Junk and Excluded folder and functionality reinstated.
  • Changes for AppClarity Business Intelligence (BI) dashboard  Web release (16 February 2017)

  • Defect fixes  Web release (14 February 2017)

  • Version upgrade in order to support AppClarity upgrade from and earlier 
  • Defect fixes  Web release (10 February 2017)

  • Usage changes
  • Changes in SCCM custom uninstall candidate priority
  • Installer updated to support HTTPS with ActiveEfficieny  Web release (11 January 2017)

  • Usage updates and change in the UI for usage not reported
  • Reduction in the overall synchronization time  Web release (12 December 2016)

  • Support for Configuration Manager CB1610
  • improvements to the usage algorithm to manage mismatched full versions

  • Improvements to catalog product matching with the auto-curation feature  Web release (16 November 2016)

  • Configuration Manager custom uninstall feature
  • Cloud synchronization functionality (downloads and uploads)
  • Support for the resumption of AppClarity's synchronization functionality (it resumes from the point it was interrupted)
  • Performance improvements
  • New unknown usage category displayed in reports (product installation, product optimization and unused software), the policy and summary tab to identify applications which do not have data to calculate their usage

Rolled-up hotfixes

  • Q12923 – AppClarity synchronization restarts when interrupted. Introduced a resume function with or without manual intervention.
  • Q12945 - AppClarity crashing on start-up after 5.1 upgrade 
  • Q12863 - ActiveEfficiency to AppClarity synchronization duration changes
  • Q12839 - Synchroniztion and performance improvements
  • Q12909 - AppClarity synchronization stalls and does not complete
  • Q12849 - 508 compliance updates to the AppClarity console Web release (08 June 2016)

Contained fixes

  • Import entitlements with editions Web release (01 June 2016)


  • New 1E Catalog now includes extended information such as products editions, full version numbers ( The extended fields ensure accurate product matching and improves the accuracy of compliance.
  • Entitlements library:
    • enhancements to support bundles and consolidations
    • mandatory fields such as Title, Edition, Version have a Not Applicable value.
    • support for extended catalog
    • tool to export and import AppClarity 5.1 entitlements if you are considering consolidating your databases or implementing a fresh install.
  • Global dashboard of entitlements across all geographies/management groups.
  • Desktop compliance support for all version validity options i.e. ‘All versions’, ‘Greater than or equal to’ and ‘Equal to’ and ‘Less than or equal to’.
  • The Software Reclaimer:
    • reclaim licensing pack for Windows 10 – the software reclaimer requires a license key
    • HTTPS support for reclaimer
  • Improved installation and usage matching algorithms. Web release (09 October 2015)


  • A new ISO 197703 compliant Entitlement Repository that enables you to manage entitlements with contracts, rights (upgrade/downgrade), limitations, maintenance agreements, metric types and currencies. This includes:
    1. A visualisation library that allows querying/sorting/grouping entitlements in flexible ways to understand important metrics like outgoing maintenance costs per year, total cost of software, upcoming renewals, etc.
    2. A simple tilebased entitlement view page that exposes information about an entitlement in a clear manner
    3. An intuitive mechanism (manual/automated) to add entitlements to the entitlements repository
    4. A mechanism to migrate existing license ledgers to ISO 197703 entitlements
  • Currency management AppClarity can now report in 10 different currencies for regions which can be configured per user. You can also add currencies to the system
  • Catalog integration with Technopedia integration with BDNA's online catalog (Technopedia) for extended information
    1. Enhancements to the Software Reclaimer
    2. Reclaim policies can be configured to reclaim a specific version of a product
    3. The Software Reclaimer can now be customised per locale
  • Integration with Business Intelligence tools AppClarity's reporting views can now be integrated with tools like Qliksense for business intelligence and analysis, so reporting can be customised
  • Multilinking unidentified applications Administrators can now link multiple unidentified applications to an identified version in one operation Web release (02 March 2015)


  • Licenses now have both a start date and expiry date that control when the license is effective. If these are not specified a license is permanent, as previously. Licenses that have either reached their expiry date or have not yet become effective are excluded from compliance calculations and thus behave as if they did not exist.
  • The license ledger highlights expired licenses and licenses not yet effective, in order to be able to easily identify them. In addition, it is possible to sort the ledger by either of these two fields.
  • The license ledger CSV produced by the vendor compliance report includes the expiry and effectivity dates of any licenses.
  • License import from CSV now supports column headers. This allows the CSV file format to be flexible and allows the user to add additional columns which will be preserved across the import and sent to the output file. Column headers not understood by license import are simply ignored. In addition, optional fields can simply be entirely omitted from the license CSV if desired, as long as headers are specified for the mandatory fields (publisher, product, release, quantity)
  • You can specify the management group into which a license is to be imported in the CSV.
  • Notifications can be set up to ensure that license managers are aware of any licenses due to expire in the near future. These notifications are sent through email.
  • The product installation report is no longer limited to 100,000 rows and can also be run for all publishers and all products. Previously this was only possible if a management group other than [global] was selected.
  • The product installation report now includes the usage reason. Previously the only way to retrieve the basis on which usage was calculated (i.e used/rarely used/unused) was by querying the product installation API.
  • The product installation report now includes the actual install date and the last run date for the product.
  • You can now specify a particular product when running the Vendor Compliance report.
  • Compliance risk has been added to AppClarity functionality. A product is at compliance risk if it either has licenses due to expire which would cause it to become noncompliant in the near future, or if the installation count for the product is approaching the total license count for the product. Risk is shown by a yellow traffic light in the console for that product. Additionally License managers can choose to be notified if a product has come to be seen under compliance risk.
  • A new compliance risk report allows the user to view risk details for any or all management groups.

Rolled-up hotfixes

  • Q12651 Service fails to start when deleting a site defined release
  • Q12649 AppClarity ActiveEfficiency connector sync fails intermittently with MERGE error
  • Q12647 Reclaimer Still Says In Progress For Optional Policy Even After Software Uninstalls
  • Q12645 Policy Changes Do Not Stick, Console Says Other Users May Be Making Changes 
  • Q12643 Product Linking Requires Service Restart