1. Check the SIJS log
   • Run a scan with SIJS and review the log file (trace level minimal):

C:\ProgramData\SnowSoftware\Inventory\Agent\script-output\SnowInventoryJavaScanner\sijs.rotation0.log

2. • Confirm whether the file flagged is a false positive (not an actual Oracle Java installer).

3. Edit the SIJS configuration
   • Exclude MSI files by adding them to the JavaMsiIgnore section in sijs.config.
   • Example configuration:

<JavaMsiIgnore>

  <Filename>ExampleInstaller.msi</Filename>

  <Filename>AnotherFalsePositive.msi</Filename>

</JavaMsiIgnore>

4. • Add one <Filename> element for each MSI file you want to exclude.
5. Run the scanner again
   • After the next scan, check the SIJS log to confirm the file is detected but ignored.

6. Verify in Snow License Manager
   • After overnight processing, Snow License Manager records will update, and the excluded MSI files will no longer appear as Oracle Java commercial features in use.

False positives from non-Java MSI files are excluded from SIJS scans. As a result, Snow License Manager reports are more accurate and do not incorrectly show licensed Oracle Java features in use.

Following overnight processing, the records in Snow License Manager have been updated and no longer show the feature in use on this machine.

• Oracle FAQ – MSI Enterprise JRE Installer
• Snow Inventory Java Scanner 3.3.5 release notes
• Configuring the Java scanner