The File Version basic rule is used when creating or modifying custom updates in the Custom Updates Publishing Tool. Most often it is used as an applicability or installed type rule. A specific file and version are verified with what is found on the client. If the rule does not pass verification, the custom update is considered not applicable or not installed on the client. The File Version rule has the following configuration settings:
- Common Paths: Specifies a common folder where the file
is located. This is an optional field when specifying an absolute
path in the Path field, but required when a relative path is
used. For example, if you know that Notepad.exe is located in the
Windows folder, but the drive location is unknown, the Windows
common path can be used to specify the folder location and
Notepad.exe can be used in the Path field to specify the
- Path: Specifies the path to the file. The path is an
absolute (c:\Windows\Notepad.exe) or relative path
(MyFolder\Notepad.exe). This is a required field.
- Comparison: Specifies whether the file version on the
client is less than, less than or equal to, equal to, greater than
or equal to, or greater than the configured version. This is a
- Version: Specifies the version of the file. The version
must be a valid format or the required field indicator displays.
This is a required field.