The Snow Inventory Java Scanner is a Java-based application that requires an appropriate Java binary on the target computer to operate. This design ensures platform independence, allowing the tool to run "anywhere." However, it introduces a challenge: Java must be installed for the tool to detect Java installations or their removal.

This article explains how Java data collected by the Snow Inventory Java Scanner (SIJS) is removed and the implications for your OMO Java reporting.

Java installation removal

Java installations can be removed from a previously inventoried computer in Snow License Manager (OMO) reporting and GUI in two ways:

1. Detected removal: The Java scanner reports the removal of a previously detected Java installation.
2. Aged off: The Java installation "ages off" due to a lack of reporting.

Example scenarios

Detected removal

1. A computer has two Java installations.
2. The Java scanner runs, the snowpack is ingested by the inventory server, and overnight processing (DUJ/OMO services) completes successfully.
3. Both installations are visible in the OMO GUI and the all Java installations report.
4. An end user uninstalls one of the Java installations.
5. The agent and Java scanner run, and the snowpack is delivered and processed.
6. Only one Java installation is visible in the OMO GUI and report the next day.

Since the Java scanner continued running, it detected the removal, which is reflected in Snow License Manager in real time.

Aged off

1. A computer has one Java installation.
2. The end user uninstalls the only Java installation.
3. The agent runs, but the Java scanner does not start due to the absence of a Java binary.
4. The agent sends the snowpack without any Java scanner result, and it is processed as usual.
5. The OMO GUI and reports still show the computer as having one Java installation.

In this scenario, Java reporting is inaccurate because the OMO system cannot determine the reason for the lack of update. The system assumes Java is still present unless updated information is received.

Configure the Java deletion threshold

To address potential inaccuracies, you can configure the system to limit how long it waits for an update before considering Java uninstalled.

1. Navigate to Snow Management and Configuration Center > Configuration > Basic Settings
2. Configure your settings:
• JAVADELETETHRESHOLD: Number of days until a not updated Java installation is considered uninstalled.
• JAVADELETETHRESHOLD_ACTIVE: Activates the deletion of not updated Java installations.

After the configured number of days with no new Java scan result, and if the JAVADELETETHRESHOLD_ACTIVE box is ticked, all Java installations from the machine will be removed.