This sub-Section allows activating the recount of software licenses based on OS-specific criteria. In addition, it allows you to track any type of file or set of files regardless of their nature.
In the simplest cases, the presence of a single executable file could mean that a particular software is installed on a PC. However, a single file cannot always guarantee the true and correct installation of a given program. In order to provide a solution that is adapted to all situations, Synexsys Inventory allows counting the softwares based on the presence of files and tracers. These files can be EXEs or DLLs, as well as INIs or LNKs (start menu shortcuts) or even DATs or LICs. If you normally include tracers in software installations, these tracers will help you differentiate officially installed software from pirated software.
One of the best ways of controlling piracy is to include a tracer as a file in the software installation disk (an internal_code.dat file, for instance). The presence of the tracer will guarantee that the installation is official and will allow you to distinguish non-authorised installations easily. Some of the companies that use Synexsys manage their licenses only based on these tracers, and do not take into account the own application's files.
![]() |
Creating Rules from queries and the "Software" / "Software EXE" tab Many times, creating software recognition rules and/or adding files based on query results or the PCs' software EXE summaries is simpler. Click on any of the two links to learn more. |
![]() |
Viruses, screensavers, mpeg, etc. : With Synexsys you can easily detect them based on a single file. In the "File" sub-Section of the Queries Section, you may query the database on all of a file's features. For instance, its name, path, version, size, etc. Query criteria can be rough. For example, you can enter "winz*.exe" to find winzip.exe, winzip32.exe, winzip80.exe, etc. Then, you can add the files you wish to track in the software tracking rules. In the "Software tracking" view you may then see which of the PCs have the tracked files on its disk. |
This window divided into 3 panes:
Software to track
|
|
![]() |
List of applications or sets of files for which recognition rules have been set.
|
Properties
|
|
![]() |
Name: Name given to the software you want to trace |
![]() |
Description: Description of the software |
![]() |
Licenses number : Number of purchased licenses |
![]() |
Suite: Allows you to visually differentiate suites and stand-alone software |
![]() |
Active: Allows displaying or hiding the package from the views. The aim of this function is to avoid a specific package from being seen in the views when recognition tests have not yet been validated. This option allows allows keeping recognition rules so they are systematically included in the statistics.
|
![]() |
Number of mandatory files: This makes the recognition rule more flexible. If all the values are " 0 ", the window "Complete recognition" of the Software Tracking view will only contain the PCs that fully match all rules. For instance: for MS-Office, if the rule requires the presence of 4 files: EXCEL.EXE, WINWORD.EXE, POWERPNT.EXE, and MSACCESS.EXE for a complete recognition, a PC having all of them except one will be classified under partial recognition. If certain values are not "0", the number of conditions that are required for a complete recognition can be reduced. The advantage is not explicitly citing such conditions. For instance: if you do not want to make a distinction between MS-Office and MS-Office Pro licenses, you can create a rule that would require EXCEL.EXE, WINWORD.EXE, POWERPNT.EXE, and MSACCESS.EXE files but then enter a "3 " in the field "EXE=" for the "Number of mandatory files".
|
RulesTake into account:
|
|
![]() |
File name: the file's name (with extension) is taken into account in the recognition. This is the main recognition criteria. As soon as you enter the file extension, the other fields become adapted to the context. You cannot use substitution characters in the file name. The file name should be entered exactly with its extension. For instance: babylon.exe |
![]() |
Other properties: Contrary to the file name, which is mandatory, there is no need to use other file properties for software recognition. Nevertheless, sometimes those fields can be very useful to determine the language of a software. Apart from the file Size and the Date, the other properties accept substitution characters.
|
|
Substitution Characters
|
![]() |
* (star): Replaces a character string. For instance *:\progra* |
![]() |
?: Replaces a character. For instance ?:\program files\babylon |
![]() |
[a,b,c]: Restricts the search to the named characters. For instance [c, d, e]:\progra* |
![]() |
[c-e]: Allows you to work with a range of values. For instance [c-e]:\progra* |
![]() |
[!f-z]: Allows you to exclude values or ranges of values. For instance: [!f-z]:\progra* |
![]() |
All substitution characters can be combined together. |