The Community is now in read-only mode to prepare for the launch of the new Flexera Community. During this time, you will be unable to register, log in, or access customer resources. Click here for more information.
Inventory gathered by the inventory component (ndtrack) does not include details about files named “java.exe” found on Windows computers unless the PerformOracleJavaAuditScan preference is enabled (set to TRUE).
The intention of the PerformOracleJavaAuditScan preference is that it should be enabled in order to gather data about Oracle Java installations to assist with Oracle Java audits. Due to this issue, this preference must also be enabled in order to gather basic data about files named “java.exe” on Windows computers. If this preference is not enabled, these details will not be gathered.
This issue does not affect non-Windows computers.
Enable the PerformOracleJavaAuditScan preference to include details of files named “java.exe” in the generated inventory NDI file. This preference can be enabled through agent policy by checking the Enable collection of Oracle Java audit data check box located on the Inventory Settings page.
Additional details about this preference can be found in Flexera One IT Asset Management documentation: PerformOracleJavaAuditScan.
If ndtrack.exe is being invoked directly, the preference can be enabled using command line options. For example:
ndtrack.exe -o IncludeDirectory=c:\Path\To\Java\Install -o PerformOracleJavaAuditScan=true
Details about java.exe files that have been successfully gathered will normally appear in inventory NDI files similarly to the following example:
<Content MD5="NO_MD5" Size="46832"> <Instance Path="C:\Path\To\Java\Install\bin\java.exe" DateTime="20220421T192028"/> <Property Name="JavaVersion" Value="11.0.15+10-LTS"/> [...] </Content> <Package Evidence="Java" Name="OpenJDK Runtime Environment Zulu11.56+19-CA" Version="11.0.15+10-LTS"> <Property Name="Publisher" Value="Azul"/> <Property Name="InstallLocation" Value="C:\Path\To\Java\Install\bin"/> </Package>
To reproduce this behavior, execute the ndtrack.exe inventory gathering process as follows, including specifying the full path to a directory containing an installation of Java that includes the file “java.exe”:
ndtrack.exe -o IncludeDirectory=c:\Path\To\Java\Install -o PerformOracleJavaAuditScan=false
The generated inventory NDI file will include details of .exe files under the identified directory except for any files named “java.exe”.
Fixed versions of the inventory component now gather basic details about java.exe files found on the filesystem of Windows computers regardless of the value of the PerformOracleJavaAuditScan preference.
Note that this preference must still be enabled (set to true) in order to gather details about Java installations required to assess Oracle Java license requirements. This preference can be enabled through agent policy by checking the Enable collection of Oracle Java audit data check box located on the Inventory Settings page.
Also see the following article which describes another possible cause for details about files named “java.exe” not being included in inventory:
This issue has been fixed in the following FlexNet Manager Suite releases: 2023 R1.4 / Oct 2023 (Cloud), 2023 R2 (On Premises)
Affected components: Agent, Inventory
Master issue ID: IOK-1060108
Also known as: ITAM-3022
Aug 17, 2023 02:27 PM - edited Nov 20, 2023 01:27 PM
@DiannaB - I understand the PerformOracleJavaAuditScan agent preference was introduced in a 2022 R1.x release (agent 18.x version number), so this particular issue likely would not affect your 2021 R1.x (17.x) agent version.
When this issue occurs, no details about java.exe files found on the filesystem will appear in your inventory NDI file. As you are seeing some details about java.exe files in your inventory, that is a good indication that this issue is not affecting you.
@DiannaB - I believe this issue will affect all agent releases (including 2022 R2.x/19.x) from when the PerformOracleJavaAuditScan preference was introduced. The "Fix status" section in this article will be updated when the issue is fixed to indicate the agent version containing the fix.
@ChrisG , does this applies to FNMS on-prem as well? If so, where can this setting be found? Would it be this?
@ppyrzynski - yes, this issue and configuration applies both to FlexNet Manager Suite on-premises and Flexera One ITAM deployments. Your screenshot shows the correct setting enabled.