Kaspersky Security for Virtualization 6.2 Light Agent

Preparing the Protection Server for operation

After completing the SVM deployment procedure, it is recommended to use virtual infrastructure tools to check the system date on the SVM. A discrepancy between the system dates on Kaspersky Security Center Administration Server and the SVM may result in an error when connecting the SVM to Kaspersky Security Center as well as incorrect operation of Kaspersky Security solution components.

After deploying the SVM on a hypervisor, you can modify the resources allocated to the SVM, for example, to match those recommended by Kaspersky experts. You can regulate the performance of the SVM using the resources assigned to it.

To prepare the Protection Server for operation, you must perform the following actions:

1. Make sure that new SVMs are connected to the Integration Server. You can view the list of connected SVMs in the Integration Server Console or in the Integration Server Web Console.
2. Activate the solution on all new SVMs.

   To activate the solution on SVMs, you must add a license key to the SVMs by using the Solution activation task. After installing the Light Agent component on virtual machines and connecting the Light Agents to the SVMs, the Protection Server component sends license information to the Light Agents.

3. Update the databases of the solution on all new SVMs and download database updates for Light Agents to the SVMs. By default, database updates required for the operation of the Protection Server, Light Agent for Linux, and Light Agent for Windows are downloaded to the SVMs from the Administration Server repository.

   If the current version of the solution supports more than one version of Light Agent for Linux or Light Agent for Windows, you need to make sure you are downloading database updates for the correct version of Light Agent. If you have different versions of Light Agent installed on protected devices, updates for all installed versions must be downloaded to the SVM.

   To configure the downloading of updates for the correct versions of Light Agent:

   1. In the Protection Server policy, specify the versions of Light Agents for which the Protection Server must receive updates.

      The Administration Server needs some time to download database updates for Light Agents. 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).

   2. Manually run the Download updates to the repository task.
   3. Download the update packages to the SVM. To download update packages to the SVM, you can use an automatically created Protection Server task, Updating databases and solution modules.