Rules for editing configuration files of Kaspersky Endpoint Security

January 20, 2022

ID 161266

When editing a configuration file, adhere to the following rules:

  • You must specify all mandatory settings in the configuration file. You can specify individual task settings without a file by using the command line.
  • If a parameter belongs to a certain section, place it only in that section. Within the confines of one section, you can place the settings in any order.
  • Enclose the names of sections in square brackets [ ].
  • Enter the values of parameters in the format parameter name=value (spaces between the parameter name and its value are not processed).

    Example:

    [ScanScope.item_0000]

    AreaDesc=Home

    AreaMask.item_0000=*doc

    Path=/home

    Space and tab characters are ignored before the first quotation mark and after the last quotation mark of a string value, and at the beginning and end of a string value that is not enclosed in quotation marks.

  • If you need to specify several values for a parameter, repeat the parameter the same number of times as the number of values that you want to specify.

    Example:

    AreaMask.item_0000=*xml

    AreaMask.item_0001=*doc

  • Be case-sensitive when entering values for the following types of parameters:
    • Names (masks) of scanned objects and excluded objects.
    • Names (masks) of threats.

    The remaining parameter values are not case-sensitive.

  • Specify Boolean parameter values as follows: Yes – No.
  • Use quotation marks to enclose string values containing a space character (for example, names of files and directories and their paths, expressions containing the date and time in the format "YYYY-MM-DD HH:MM:SS").

    You can enter the remaining values with or without quotation marks.

    Example:

    AreaDesc="Scan mail databases"

A single quotation mark in the beginning or end of a string is considered an error.

Did you find this article helpful?
What can we do better?
Thank you for your feedback! You're helping us improve.
Thank you for your feedback! You're helping us improve.