File Evidence Property Reference
• | Unrecognized File Evidence |
• | Discovered File Evidence |
• | Inactive File Evidence |
• | Ignored File Evidence |
• | All File Evidence |
Note:Most lists in IT Asset Management only show a selection of the properties in the underlying database. Some columns are displayed by default and others can be displayed using the column chooser control, including any custom properties that you have added. For information on using the column chooser, see Managing Columns in a Table.
Column Name |
Details |
|||||||||
Assigned |
Displays Yes when the evidence is matched to at least one application, and otherwise displays No. This assignment may have been done automatically through the Application Recognition Library rules, or manually by the operator. This data is read-only. |
|||||||||
Company |
The name of the publisher, as reported by the evidence. For the manually-created records, this field is editable in the General tab of the evidence properties. |
|||||||||
Description |
The file description either entered manually or reported during the inventory import. For the manually-created records, this field is editable in the General tab of file evidence properties. |
|||||||||
Language |
The language specific to this evidence (if any). For the manually-created records, this field is editable in the General tab of the file evidence properties. |
|||||||||
Matches |
Displays the number of times the file evidence is found in the new inventory. Note: The same file evidence might be identified in multiple folders on a single system. A figure displayed in the Matches column may not reflect the number of installations of the software applications: the installation count is displayed in the Installed column on the Applications tab of the evidence properties. These figures may be different for the following reasons:
This data is read-only. |
|||||||||
Name |
The name of the file evidence. The file evidence is derived from the executables and other common program files that are installed on the computer's hard disk. For example, on Windows devices this includes the .exe and .dll files; on UNIX platforms it includes all files with no file extension; and so on. Tip:Clicking the hyperlink on the Name value opens the properties for that piece of file evidence. In those properties, selecting the Devices tab lists all the inventory devices where that file evidence has been reported in inventory. This data is read-only. |
|||||||||
Path |
On Windows (where this value is not used for application recognition), this is the most common location in which this evidence was found on inventory devices. On UNIX, the value is returned along with the file name, and is included for application recognition (where the file evidence is so used). For the manually-created records, this field is editable in the General tab of the file evidence properties. For evidence supplied through the Application Recognition Library, the file path is not editable. |
|||||||||
Product name |
The name of a product retrieved from the file evidence. For the manually-created records, this field is editable in the General tab of the file evidence properties. Product names supplied by the Application Recognition Library are not editable. |
|||||||||
Product version |
The Product version specific to the application that includes the file evidence. |
|||||||||
Size |
Indicates the size of the evidence file. |
|||||||||
Source |
The source of this evidence rule:
For the manually-created records, editable in the General tab of the File Evidence Properties. For evidence supplied through the Application Recognition Library, the Source field is not editable. |
|||||||||
Version |
The version of the installed application, as reported by the evidence. For the manually-created records, this field is editable in the General tab of the evidence properties. An evidence version retrieved from Application Recognition Library is not editable. Note:Incorrectly editing a version may stop the inventory agent from recognizing the applications linked to the evidence. If you edit the version number, be sure to check the association with the application and ensure that the rule (or wildcards) still applies to the modified evidence. Tip:While each piece of evidence should have a distinct version, you can link them to an application using the percent wildcard character (%). This represents zero or more characters. For example, the evidence versions reported for a single application on 3 different computers might be 10.1.123.0045, 10.1.126.0000, and 10.1.123.0048 (they might represent different service packs and hot-fixes). On the linked application, you can merge this evidence to a single rule for version 10.1.%. Then license calculations will link all three pieces of evidence to the same application. Note:The period and a comma characters are counted as matching each other. There is no single wildcard character. |