The report contains information on computer OS, location, corporate unit etc. If several evidences led to the recognition of one installed application, there will be several rows in the report. The report shows all installations for the product named entered in the search filter (exact match on Product Name) and looks up all raw evidences that match this title for recognition (files (mandatory, at least one as a recognition rule, not ignored), installer (not ignored) or WMI (added with v5 of the report).
NOTE THAT THIS REPORT HAS BEEN RELEASED WITH ITAM 2021 31.4 / FNMS 2022R1. There is however a need (for Java particularly) to understand what is the underlying exact version of the evidences that have been recognized into the application (major version). The applications are often normalized at major version level. The Flexera ARL normalizes the raw evidences to make the data manageable and align with the licensing requirements. Recognized Applications Transparency Report (NR) Business need and the raw versions of the evidences that allowed to recognize the applications. A report mitigates this issue and allows to understand (for all products) the recognized applications. The downside is a loss of visibility on recognized applications. The April announcement for the change can be found here: This build level management forced Flexera to change from a quite granular “update level recognition” to a “major version level” normalization, to avoid the mess of having tens of recognized builds and versions. To address this need, Flexera ARL had to link evidences based on their build level (available in Windows, the Unix agent will bring this capability in June). The list of public and restricted updates and builds are at the bottom of this answer.
An example in the Java Standard 8 release notes.
0 kommentar(er)
