Creating Custom File Date Offset Checks


This custom check enables you to determine if a specific file on your scanned machines is considered current or out-of-date. How old a file is in relation to the current date will often indicate the validity of the file's content. Examples of this are antivirus signature files, application data files, or specific operating system files with known security flaws.  


This custom check compares the file modification date to the current date.  Based on criteria that you specify, machines with files found to be out-of-date will be flagged as out of compliance. For example, you may create a custom check that determines if an antivirus signature file is more than three days old. Machines with signature files older than three days would be out of compliance and would require updated files.  


Note: Custom File Date Offset checks are not currently enforceable. Enforcement may be available in a future release of VMware vCenter Protect - Configuration Management.

  1. To create a new custom File Date Offset check from scratch, from the Custom Check Wizard click Create New Custom Check.

The following dialog is displayed:


  1. Select the desired operating system levels and then click Next.

Tip: To determine the operating system being used on a particular machine, on the machine's desktop right-click My Computer and then select Properties. The operating system is listed on the General tab.

The General Properties dialog is displayed.


  1. Type a unique name for the custom check and a description.

  2. In the Type box select File Date Offset and then click Next.

The Specific Properties dialog is displayed. For example:


  1. In the File Path box, specify the full path name to the file for which you want to create a custom check.

If you don't know the exact location of the file, click Select File to locate the file.

Tip: You can specify standard Windows environment variables within the path name (for example: %windir%, %systemroot%, etc).

  1. Click Test Check.

This test has two purposes. It validates that the file can be found in the designated location and it displays the number of days since the file located on the console machine was last modified. If the test comes back unable to locate the file it means the check is not properly defined.

  1. Click Next.

The Operator and Value dialog is displayed.


  1. Select an operator, specify an expected value, and then click Next.

The Operator can be any of the following:

The Expected Value is the number of days from the scan date. For example, if you are testing to see that a file is not more than three days old, you would specify <= 3.

  1. Click Next.

The following dialog is displayed.



  1. (Optional) If you want to export this custom check to an XML file to use it as the starting point for other custom checks, click Export to File.

For more information, see Exporting Custom Checks.

  1. Click Finish.

The custom check is displayed within the policy. For example: