The File Modified Date 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 its last modified date 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 Modified Date 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
file location.
- 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 modified date. This is
a required field.
- Modified Date: Specifies the date the file was last
modified. Use the Modified Date check box to enable this
property and then specify the last modified date and time of the
file. The default value is the current date and time. This is a
required field.