Kaspersky Security for Virtualization 6.2 Light Agent

Updating Kaspersky Security databases and application modules

The update functionality (including anti-virus signature updates and code base updates) may not be available in the solution in the territory of the USA.

Updating the databases and application modules of the Kaspersky Security solution ensures up-to-date protection of virtual machines. New viruses and other types of malware appear worldwide on a daily basis. Kaspersky Security databases contain information about threats and ways of neutralizing them. Kaspersky Security databases include antivirus databases and other Kaspersky databases important for the security of the protected infrastructure. Updating Kaspersky Security application modules lets you promptly receive important updates to Kaspersky Security solution components. To enable the Kaspersky Security solution to promptly detect threats, you need to update the solution's databases and modules regularly.

If the Kaspersky Security databases have not been updated for a long time, a notification appears in Kaspersky Security Center in the SVM properties window (in the Events section, if you are working through Kaspersky Security Center Administration Console; on the Events tab, if you are working through Kaspersky Security Center Web Console).

Updating Kaspersky Security databases and application modules may change certain Kaspersky Security settings, for example, the heuristic analysis settings that improve the effectiveness of protection and scans.

Updates of Kaspersky Security databases and application modules require a current license to use the application.

Updating Kaspersky Security databases and application modules involves the following steps:

  1. Downloading an update package to a Kaspersky Security update source

    An update source is a resource that contains database updates and application module updates of Kaspersky applications. The Kaspersky Security Center Administration Server repository is the source of updates for Kaspersky Security for Virtualization 6.2 Light Agent.

    To download updates to the Administration Server repository, use the Download updates to Administration Server repository task. The task is created automatically by the Kaspersky Security Center Initial Configuration Wizard. If the "Download updates to Administration Server repository" task is not in the list of tasks for the Administration Server, you need to create it. For details, please refer to the Kaspersky Security Center help.

    The contents of the update package that Kaspersky Security Center creates in the Kaspersky Security repository depends on the update download settings configured in the Protection Server policy. By default, an update package contains the database updates required for the operation of the Protection Server, Light Agent for Linux, and Light Agent for Windows. You can configure the downloading of updates as well as enable application module updates for Kaspersky Security components.

    If the current version of the solution supports more than one version of Light Agent for Linux or Light Agent for Windows, make sure that the update settings in the Protection Server policy specify the same version of Light Agent that you are using.

  2. Downloading an update package from the Administration Server repository to a folder on the SVM

    To download update packages to SVMs, use the Database update task for the Protection Server.

    You can use the Update databases and solution modules task, which is created automatically after installing the MMC plug-in or the Protection Server web plug-in in Kaspersky Security Center. This task is created for the Managed devices administration group and lets you download an update package to all SVMs that are part of the Managed devices group or any nested administration group. The task is started every time an update package is downloaded to the Kaspersky Security Center Administration Server repository.

    If necessary, you can change the settings of the automatically created update task or delete it and create a new Database update task for the Protection Server.

    For the Protection Server to successfully download an update package from the Administration Server storage, the SVM on which the Protection Server is installed must have access to the Kaspersky Security Center Administration Server. The SVM connection to the Administration Server is configured when SVMs are deployed or reconfigured.

    If Kaspersky Security databases and application modules have not been updated for a long time, the size of the update package may be large. Downloading this update package may generate additional network traffic (up to several dozen megabytes).

  3. Installing database updates from a folder on the SVM

    The Protection Server automatically installs on SVMs the database updates necessary for the operation of the Protection Server.

    Light Agent checks the availability of an update package in the folder on the SVM to which it is connected.

    To receive updates to databases and application modules, the Light Agent must interact with the Protection Server via the HTTP protocol.

    If an update package is available, Light Agent installs the application database updates required for the operation of Light Agent on the protected virtual machine. Database and application module updates for Light Agent are obtained using the Update local predefined task. This task is created automatically in applications running in Light Agent mode. In this task, a folder on the SVM is specified as the update source. The task starts automatically in the following cases:

    • when connecting the Light Agent to the SVM, if the Kaspersky Security databases on the Light Agent are missing or do not correspond to the databases installed on the Protection Server;
    • 120 minutes after the previous successful update or 20 minutes if the update fails.

    You can also run the Update task manually. For details, see the Help for the application running in Light Agent mode.

  4. Installing Kaspersky Security application module updates from a folder on the SVM

    If application module updates are included in the update package, they are installed in the following way:

    • Updates to the Protection Server modules are installed on the SVM by running the Solution module update on the SVM task for the Protection Server.

      From the command line, you can view the list of installed application module updates on the SVM by running the patch_list.pl script, which is located in the /opt/kaspersky/la/patching/ directory.

    • Updates to Light Agent application modules are installed on virtual machines automatically by running the preset Update local task.

    After installing application module updates for Kaspersky Security components, the performance of each Protection Server and Light Agent is checked. If problems are detected, the application module update is automatically rolled back.

    If errors occur in the operation of the Protection Server after updating application modules, you can manually roll back the module update on the SVM.

To ensure up-to-date protection of non-persistent virtual machines, you are advised to regularly update Light Agent databases and application modules on the virtual machine templates from which non-persistent virtual machines have been deployed.

If you enabled VDI protection mode during installation of Light Agent on the virtual machine template, updates that require restarting the protected virtual machine are not installed on non-persistent virtual machines. On receiving updates that require restarting the protected virtual machine, Light Agent installed on a non-persistent virtual machine sends a message to Kaspersky Security Center informing it that the protected virtual machine template needs to be updated.

In this Help section

Configuring settings for downloading updates to SVMs

Creating a Database update task

Creating a Solution module update on the SVM task

Rolling back the last update of Kaspersky Security databases and application modules

Page top
[Topic 255465]

Configuring settings for downloading updates to SVMs

You can configure the following settings for downloading database and application module updates to SVMs:

  • Enable updating of application modules of Kaspersky Security components.

    If updating application modules is enabled, the Protection Server adds application module updates of Kaspersky Security components to the update package.

    Updates to Light Agent application modules are installed automatically on protected virtual machines. To install Protection Server application module updates, use the Solution module update on the SVM task.

  • Select the versions of Light Agents for which the Protection Server will receive updates. By default, an update package contains the database updates required for the operation of the Protection Server, Light Agent for Linux, and Light Agent for Windows.

    Only Light Agents for which database updates are downloaded to this SVM can connect to the SVM.

    If the current version of the solution supports more than one version of Light Agent for Linux or Light Agent for Windows, make sure that the update settings in the Protection Server policy specify the version of Light Agent that you are using.

You can use the Web Console or the Administration Console to configure update download settings in a Protection Server policy.

Expand all | Collapse all

How to configure settings for downloading updates to SVMs in Kaspersky Security Center Web Console

To configure the downloading of updates on an SVM:

  1. In the main window of Kaspersky Security Center Web Console, select Assets (Devices)Policies and policy profiles.

    A list of policies opens.

  2. Select the administration group containing the SVM with the Protection Server whose settings you want to configure. To do so, click the link in the Current path field located above the list of policies and policy profiles, and select an administration group in the window that opens.

    The list displays only the policies configured for the selected administration group.

  3. Click on the name of the desired policy in the list.
  4. In the policy properties window that opens, select the Application settings tab and go to the Update settings section.
  5. In the right part of the window, configure the Update solution modules setting.

    Enables/disables receiving updates for Kaspersky Security application modules along with updates to the solution databases.

    If the check box is selected, the Protection Server receives updates of application modules for Kaspersky Security components along with database updates from the Kaspersky Security Center Administration Server storage.

    This check box is cleared by default.

    If you edit a setting, the new value is applied the next time the database update task on the Protection Server runs.

  6. If necessary, use the check boxes to configure the list of versions of Light Agents for which the Protection Server will receive updates. At least one version must be selected.

    The list contains the supported versions of Light Agents. If the version of the Light Agent you want to receive updates for is not listed, click the Refresh button.

  7. Click the Save button.

How to configure settings for downloading updates to SVMs in Kaspersky Security Center Administration Console

To configure the downloading of updates on an SVM:

  1. In the Kaspersky Security Center Administration Console tree, in the Managed devices folder, select the administration group containing the SVM with the Protection Server whose settings you want to configure.
  2. In the workspace, select the Policies tab.
  3. Select a Protection Server policy in the list of policies and right-click to open the Properties: <Policy name> window.
  4. In the policy properties window, select the Update settings section in the list on the left.
  5. In the right part of the window, configure the Update solution modules setting.

    Enables/disables receiving updates for Kaspersky Security application modules along with updates to the solution databases.

    If the check box is selected, the Protection Server receives updates of application modules for Kaspersky Security components along with database updates from the Kaspersky Security Center Administration Server storage.

    This check box is cleared by default.

    If you edit a setting, the new value is applied the next time the database update task on the Protection Server runs.

  6. If necessary, use the check boxes to configure the list of versions of Light Agents for which the Protection Server will receive updates. At least one version must be selected.

    The list contains the supported versions of Light Agents. If the version of the Light Agent you want to receive updates for is not listed, click the Refresh button.

  7. Click the Apply button.

If you have modified the list of Light Agent versions for which the Protection Server must get updates, we recommend starting the database update process after completing the synchronization of the Network Agent on the SVM with the Administration Server (by default, the synchronization period is 15 minutes after changing the policy settings).

Page top
[Topic 255525]

Creating a Database update task

You can create database update tasks on the Protection Server using the Web Console as well as the Administration Console.

Expand all | Collapse all

How to create a Database update task in Kaspersky Security Center Web Console

To create a database update task:

  1. In the main window of Kaspersky Security Center Web Console, select Assets (Devices) → Tasks.

    A list of tasks opens.

  2. Click the Add button.

    The New Task Wizard starts.

  3. At the first step of the Wizard:
    1. In the Application drop-down list, select Kaspersky Security for Virtualization 6.2 Light Agent – Protection Server.
    2. In the Task type drop-down list, select the Database update task type.
    3. In the Task name field, enter the name for the new task.
    4. In the Select devices to which the task will be assigned section, select a method for determining the task scope. A task scope is a set of SVMs on which a task will run.
      • Select the Assign task to an administration group option to execute the task on all SVMs belonging to the specified administration group.
      • Select the Specify device addresses manually or import from list option to execute the task on the specified SVMs.
      • Select the Assign task to selected devices option to execute the task on the SVMs included in the selection of devices according to a predefined criterion. For details on creating a selection of devices, please refer to the Kaspersky Security Center help.

    Proceed to the next step of the wizard.

  4. Depending on the selected method for defining the task scope, do one of the following:
    • In the administration group tree, select the check boxes next to the required administration groups.
    • In the list of devices, select the check boxes next to the required SVMs. If the required SVMs are not listed, you can add them in the following ways:
      • Using the Add devices button. You can add devices by names or IP addresses, add devices from the specified IP address range, or select devices from the list of devices detected by the Administration Server when polling the organization’s local network.
      • Using the Import devices from file button. Addresses are imported from a TXT file with a list of addresses of SVMs, with each address in a separate row.

      If you import a list of SVMs from file or specify the addresses manually and the SVMs are identified by name, the list of SVMs for which the task is being created can be supplemented only with those SVMs whose details have already been included in the Administration Server database upon connection of SVMs or following a poll of the local area network.

    • In the list, select the name of the selection containing the required SVMs.

    Proceed to the next step of the wizard.

  5. Select the Open task properties window after creation check box to configure the task launch schedule, and click the Finish button to exit the wizard.
  6. In the properties window that opens for the new task, go to the Schedule tab. In the Scheduled start drop-down list, select When new updates are downloaded to the repository.

    If necessary, configure other task launch schedule settings. For more information about the task schedule, see the Kaspersky Security Center Help.

  7. Click Save in the policy properties window.

How to create a Database update task in Kaspersky Security Center Administration Console

To create a Database update task:

  1. In the Kaspersky Security Center Administration Console, perform one of the following actions:
    • If you want to create a task that will run on SVMs included in the selected administration group, select this administration group in the console tree. Then in the workspace, select the Tasks tab and click the New task button.

      A wizard starts to create a task for devices of the selected administration group.

    • If you want to create a task that will run on one or more SVMs (a task for a set of devices), select the Tasks folder in the console tree and click the New task button in the workspace.

      A wizard starts to create a new task for a set of devices.

  2. At the first step of the wizard, select Kaspersky Security for Virtualization 6.2 Light Agent – Protection Server and the Database update task type.

    Proceed to the next step of the wizard.

  3. If you are creating a task for a set of devices, the wizard will prompt you to define the task scope. A task scope is a set of SVMs on which a task will run.
    1. Specify the method for defining the task scope: select SVMs from the list of devices discovered by the Administration Server, manually specify the SVM addresses, import a list of SVMs from a file, or specify a previously configured selection of devices (for details, see the Kaspersky Security Center Help).
    2. Depending on the specified method for defining the scope, perform one of the following operations in the window that opens:
      • In the list of detected devices, specify the SVMs on which the task will be run. To do so, select the check boxes in the list, on the left of the device names.
      • Click the Add or Add IP range button and enter the addresses of SVMs manually.
      • Click the Import button, and in the window that opens select a TXT file with the list of addresses of SVMs.
      • Click the Browse button, and in the window that opens specify the name of the selection containing the SVMs for which you want to create the task.

    Proceed to the next step of the wizard.

  4. In the Scheduled start drop-down list, select When new updates are downloaded to the repository.
  5. If necessary, configure other task launch schedule settings:
    • Run skipped tasks

      If you want the solution to start missed tasks immediately after an SVM appears on the network, select this check box.

      If this check box is cleared, in Manually mode, the task is started only on SVMs that are visible on the network.

    • Use automatically randomized delay for task starts

      By default, the time of task start on SVMs is randomized with the scope of a certain time period. This period is calculated automatically depending on the number of SVMs covered by the task:

      • 0–200 SVMs – task start is not randomized
      • 200–500 SVMs – task start is randomized within the scope of 5 minutes
      • 500–1000 SVMs – task start is randomized within the scope of 10 minutes
      • 1000–2000 SVMs – task start is randomized within the scope of 15 minutes
      • 2000–5000 SVMs – task start is randomized within the scope of 20 minutes
      • 5000–10000 SVMs – task start is randomized within the scope of 30 minutes
      • 10000–20000 SVMs – task start is randomized within the scope of 1 hour
      • 20000–50000 SVMs – task start is randomized within the scope of 2 hours
      • over 50000 SVMs – task start is randomized within the scope of 3 hours

      If you do not need to randomize the time of task start within the scope of an automatically calculated time period, clear the Use automatically randomized delay for task starts check box.

      This check box is set by default.

    • Use a random delay to start the task in an interval (min)

      If you want to start the task at a given time within a specified period after manual launch, select this check box. In the corresponding text box, specify the maximum task run delay time. In this case, after manual start, the task is started at a random time within the specified period.

      This check box can be changed if the Use automatically randomized delay for task starts check box is cleared.

    For more information about the task launch schedule settings, refer to the Kaspersky Security Center help.

    Proceed to the next step of the wizard.

  6. In the Name field, enter the name of the new task and proceed to the next step of the new task wizard.
  7. If you want the task to start as soon as the New Task Wizard finishes, select the Run task when the wizard is complete check box.
  8. Finish the wizard.

The task is started every time the update package is downloaded into the storage of the Administration Server. You can also run the Database update task manually on the Protection Server at any time.

Page top
[Topic 255622]

Creating a Solution module update on the SVM task

You can create solution module update tasks on SVMs using the Web Console as well as the Administration Console.

Expand all | Collapse all

How to create a Solution module update on the SVM task in Kaspersky Security Center Web Console

To create a Solution module update task on an SVM:

  1. In the main window of Kaspersky Security Center Web Console, select Assets (Devices) → Tasks.

    A list of tasks opens.

  2. Click the Add button.

    The New Task Wizard starts.

  3. At the first step of the Wizard:
    1. In the Application drop-down list, select Kaspersky Security for Virtualization 6.2 Light Agent – Protection Server.
    2. In the Task type drop-down list, select the Solution module update on the SVM task type.
    3. In the Task name field, enter the name for the new task.
    4. In the Select devices to which the task will be assigned section, select a method for determining the task scope. A task scope is a set of SVMs on which a task will run.
      • Select the Assign task to an administration group option to execute the task on all SVMs belonging to the specified administration group.
      • Select the Specify device addresses manually or import from list option to execute the task on the specified SVMs.
      • Select the Assign task to selected devices option to execute the task on the SVMs included in the selection of devices according to a predefined criterion. For details on creating a selection of devices, please refer to the Kaspersky Security Center help.

    Proceed to the next step of the wizard.

  4. Depending on the selected method for defining the task scope, do one of the following:
    • In the administration group tree, select the check boxes next to the required administration groups.
    • In the list of devices, select the check boxes next to the required SVMs. If the required SVMs are not listed, you can add them in the following ways:
      • Using the Add devices button. You can add devices by names or IP addresses, add devices from the specified IP address range, or select devices from the list of devices detected by the Administration Server when polling the organization’s local network.
      • Using the Import devices from file button. Addresses are imported from a TXT file with a list of addresses of SVMs, with each address in a separate row.

      If you import a list of SVMs from file or specify the addresses manually and the SVMs are identified by name, the list of SVMs for which the task is being created can be supplemented only with those SVMs whose details have already been included in the Administration Server database upon connection of SVMs or following a poll of the local area network.

    • In the list, select the name of the selection containing the required SVMs.

    Proceed to the next step of the wizard.

  5. Select the Open task properties window after creation check box to configure the task launch schedule, and click the Finish button to exit the wizard.
  6. In the properties window that opens for the new task, go to the Schedule tab. In the Scheduled start drop-down list, select Manually.

    It is not recommended to use other launch schedule options for the Solution module update on the SVM task.

    If necessary, configure other task launch schedule settings. For more information about the task schedule, see the Kaspersky Security Center Help.

  7. Click Save in the policy properties window.

How to create a Solution module update on the SVM task in Kaspersky Security Center Administration Console

To create a Solution module update task on an SVM:

  1. In the Kaspersky Security Center Administration Console, perform one of the following actions:
    • If you want to create a task that will run on SVMs included in the selected administration group, select this administration group in the console tree. Then in the workspace, select the Tasks tab and click the New task button.

      A wizard starts to create a task for devices of the selected administration group.

    • If you want to create a task that will run on one or more SVMs (a task for a set of devices), select the Tasks folder in the console tree and click the New task button in the workspace.

      A wizard starts to create a new task for a set of devices.

  2. At the first step of the wizard, select Kaspersky Security for Virtualization 6.2 Light Agent – Protection Server and the Solution module update on the SVM task type.

    Proceed to the next step of the wizard.

  3. If you are creating a task for a set of devices, the wizard will prompt you to define the task scope. A task scope is a set of SVMs on which a task will run.
    1. Specify the method for defining the task scope: select SVMs from the list of devices discovered by the Administration Server, manually specify the SVM addresses, import a list of SVMs from a file, or specify a previously configured selection of devices (for details, see the Kaspersky Security Center Help).
    2. Depending on the specified method for defining the scope, perform one of the following operations in the window that opens:
      • In the list of detected devices, specify the SVMs on which the task will be run. To do so, select the check boxes in the list, on the left of the device names.
      • Click the Add or Add IP range button and enter the addresses of SVMs manually.
      • Click the Import button, and in the window that opens select a TXT file with the list of addresses of SVMs.
      • Click the Browse button, and in the window that opens specify the name of the selection containing the SVMs for which you want to create the task.

    Proceed to the next step of the wizard.

  4. In the Scheduled start drop-down list, select Manually.

    It is not recommended to use other launch schedule options for the Solution module update on the SVM task.

  5. If necessary, configure other task launch schedule settings:
    • Run skipped tasks

      If you want the solution to start missed tasks immediately after an SVM appears on the network, select this check box.

      If this check box is cleared, in Manually mode, the task is started only on SVMs that are visible on the network.

    • Use automatically randomized delay for task starts

      By default, the time of task start on SVMs is randomized with the scope of a certain time period. This period is calculated automatically depending on the number of SVMs covered by the task:

      • 0–200 SVMs – task start is not randomized
      • 200–500 SVMs – task start is randomized within the scope of 5 minutes
      • 500–1000 SVMs – task start is randomized within the scope of 10 minutes
      • 1000–2000 SVMs – task start is randomized within the scope of 15 minutes
      • 2000–5000 SVMs – task start is randomized within the scope of 20 minutes
      • 5000–10000 SVMs – task start is randomized within the scope of 30 minutes
      • 10000–20000 SVMs – task start is randomized within the scope of 1 hour
      • 20000–50000 SVMs – task start is randomized within the scope of 2 hours
      • over 50000 SVMs – task start is randomized within the scope of 3 hours

      If you do not need to randomize the time of task start within the scope of an automatically calculated time period, clear the Use automatically randomized delay for task starts check box.

      This check box is set by default.

    • Use a random delay to start the task in an interval (min)

      If you want to start the task at a given time within a specified period after manual launch, select this check box. In the corresponding text box, specify the maximum task run delay time. In this case, after manual start, the task is started at a random time within the specified period.

      This check box can be changed if the Use automatically randomized delay for task starts check box is cleared.

    For more information about the task launch schedule settings, refer to the Kaspersky Security Center help.

    Proceed to the next step of the wizard.

  6. In the Name field, enter the name of the new task and proceed to the next step of the new task wizard.
  7. If you want the task to start as soon as the New Task Wizard finishes, select the Run task when the wizard is complete check box.
  8. Finish the wizard.

You can run the Solution module update on the SVM task manually at any time.

Page top
[Topic 255623]

Rolling back the last update of Kaspersky Security databases and application modules

After Kaspersky Security databases and application modules are updated for the first time, the ability to roll back databases and application modules to their previous versions becomes available.

Every time a database update is started on the Protection Server, Kaspersky Security creates a backup copy of the existing databases and application modules and only then proceeds to update them. This makes it possible to return to the previous version of databases and application modules if necessary. The ability to roll back an update is useful if, for example, the new version of the application database contains an invalid signature that causes Kaspersky Security to block a safe application.

A rollback of the last update of Kaspersky Security databases and application modules is performed as follows:

  1. The Protection Server component rolls back the last update of Kaspersky Security databases and application modules on SVMs. You can roll back the last update of databases and application modules on one or more SVMs:

    When rolling back the latest update of databases and application modules on the SVM, the Protection Server also rolls back updates of Light Agent databases, which are located in a folder on the SVM. The Protection Server sends Light Agents an event indicating that an update is required.

  2. After the database and application module update is rolled back on the SVM, a special Update local task is automatically launched on the Light Agents connected to the SVM. In this task, a folder on the SVM is specified as the update source.

    The update task causes the Light Agent to switch to using the previous set of Kaspersky Security databases.

In this section:

Creating a Database update rollback task

Rolling back an application module update on an SVM

Page top
[Topic 255673]

Creating a Database update rollback task

You can create Database update rollback tasks using the Web Console as well as the Administration Console.

How to create a Database update rollback task in Kaspersky Security Center Web Console

To create a Database update rollback task:

  1. In the main window of Kaspersky Security Center Web Console, select Assets (Devices) → Tasks.

    A list of tasks opens.

  2. Click the Add button.

    The New Task Wizard starts.

  3. At the first step of the Wizard:
    1. In the Application drop-down list, select Kaspersky Security for Virtualization 6.2 Light Agent – Protection Server.
    2. In the Task type drop-down list, select the Database update rollback task type.
    3. In the Task name field, enter the name for the new task.
    4. In the Select devices to which the task will be assigned section, select a method for determining the task scope. A task scope is a set of SVMs on which a task will run.
      • Select the Assign task to an administration group option to execute the task on all SVMs belonging to the specified administration group.
      • Select the Specify device addresses manually or import from list option to execute the task on the specified SVMs.
      • Select the Assign task to selected devices option to execute the task on the SVMs included in the selection of devices according to a predefined criterion. For details on creating a selection of devices, please refer to the Kaspersky Security Center help.

    Proceed to the next step of the wizard.

  4. Depending on the selected method for defining the task scope, do one of the following:
    • In the administration group tree, select the check boxes next to the required administration groups.
    • In the list of devices, select the check boxes next to the required SVMs. If the required SVMs are not listed, you can add them in the following ways:
      • Using the Add devices button. You can add devices by names or IP addresses, add devices from the specified IP address range, or select devices from the list of devices detected by the Administration Server when polling the organization’s local network.
      • Using the Import devices from file button. Addresses are imported from a TXT file with a list of addresses of SVMs, with each address in a separate row.

      If you import a list of SVMs from file or specify the addresses manually and the SVMs are identified by name, the list of SVMs for which the task is being created can be supplemented only with those SVMs whose details have already been included in the Administration Server database upon connection of SVMs or following a poll of the local area network.

    • In the list, select the name of the selection containing the required SVMs.

    Proceed to the next step of the wizard.

  5. Select the Open task properties window after creation check box to configure the task launch schedule, and click the Finish button to exit the wizard.
  6. In the properties window that opens for the new task, go to the Schedule tab. In the Scheduled start drop-down list, select Manually.

    If necessary, configure other task launch schedule settings. For more information about the task schedule, see the Kaspersky Security Center Help.

  7. Click Save in the policy properties window.

How to create a Database update rollback task in Kaspersky Security Center Administration Console

To create a Database update rollback task:

  1. In the Kaspersky Security Center Administration Console, perform one of the following actions:
    • If you want to create a task that will run on SVMs included in the selected administration group, select this administration group in the console tree. Then in the workspace, select the Tasks tab and click the New task button.

      A wizard starts to create a task for devices of the selected administration group.

    • If you want to create a task that will run on one or more SVMs (a task for a set of devices), select the Tasks folder in the console tree and click the New task button in the workspace.

      A wizard starts to create a new task for a set of devices.

  2. At the first step of the wizard, select Kaspersky Security for Virtualization 6.2 Light Agent – Protection Server and the Database update rollback task type.

    Proceed to the next step of the wizard.

  3. If you are creating a task for a set of devices, the wizard will prompt you to define the task scope. A task scope is a set of SVMs on which a task will run.
    1. Specify the method for defining the task scope: select SVMs from the list of devices discovered by the Administration Server, manually specify the SVM addresses, import a list of SVMs from a file, or specify a previously configured selection of devices (for details, see the Kaspersky Security Center Help).
    2. Depending on the specified method for defining the scope, perform one of the following operations in the window that opens:
      • In the list of detected devices, specify the SVMs on which the task will be run. To do so, select the check boxes in the list, on the left of the device names.
      • Click the Add or Add IP range button and enter the addresses of SVMs manually.
      • Click the Import button, and in the window that opens select a TXT file with the list of addresses of SVMs.
      • Click the Browse button, and in the window that opens specify the name of the selection containing the SVMs for which you want to create the task.

    Proceed to the next step of the wizard.

  4. In the Scheduled start drop-down list, select Manually.
  5. If necessary, configure other task launch schedule settings:
    • Run skipped tasks

      If you want the solution to start missed tasks immediately after an SVM appears on the network, select this check box.

      If this check box is cleared, in Manually mode, the task is started only on SVMs that are visible on the network.

    • Use automatically randomized delay for task starts

      By default, the time of task start on SVMs is randomized with the scope of a certain time period. This period is calculated automatically depending on the number of SVMs covered by the task:

      • 0–200 SVMs – task start is not randomized
      • 200–500 SVMs – task start is randomized within the scope of 5 minutes
      • 500–1000 SVMs – task start is randomized within the scope of 10 minutes
      • 1000–2000 SVMs – task start is randomized within the scope of 15 minutes
      • 2000–5000 SVMs – task start is randomized within the scope of 20 minutes
      • 5000–10000 SVMs – task start is randomized within the scope of 30 minutes
      • 10000–20000 SVMs – task start is randomized within the scope of 1 hour
      • 20000–50000 SVMs – task start is randomized within the scope of 2 hours
      • over 50000 SVMs – task start is randomized within the scope of 3 hours

      If you do not need to randomize the time of task start within the scope of an automatically calculated time period, clear the Use automatically randomized delay for task starts check box.

      This check box is set by default.

    • Use a random delay to start the task in an interval (min)

      If you want to start the task at a given time within a specified period after manual launch, select this check box. In the corresponding text box, specify the maximum task run delay time. In this case, after manual start, the task is started at a random time within the specified period.

      This check box can be changed if the Use automatically randomized delay for task starts check box is cleared.

    For more information about the task launch schedule settings, refer to the Kaspersky Security Center help.

    Proceed to the next step of the wizard.

  6. In the Name field, enter the name of the new task and proceed to the next step of the new task wizard.
  7. If you want the task to start as soon as the New Task Wizard finishes, select the Run task when the wizard is complete check box.
  8. Finish the wizard.

You can run a Database update rollback task manually at any time.

Page top
[Topic 255675]

Rolling back an application module update on an SVM

A script is used to roll back the Kaspersky Security module update on SVMs.

To roll back an application module update on SVMs,

In the command line on the SVM, run the script named patch_rollback.pl located in the /opt/kaspersky/la/patching/ folder.

The script lets you roll back only the most recently installed application module update. You can view a list of all installed updates by running the command line script named patch_list.pl located in the /opt/kaspersky/la/patching/ folder.

Page top
[Topic 255674]