For correct functioning, Kaspersky Security 3.0 Light Agent must be connected to the Secure Virtual Machine (SVM).
By default, the SVM search option is enabled in Kaspersky Security 3.0 Light Agent:
As soon as Kaspersky Security 3.0 Light Agent is installed and running on a virtual machine, it receives the information about available SVMs on all hypervisors of the virtual infrastructure. By default, Kaspersky Security 3.0 Light Agent connects to the SVM installed on the same hypervisor.
If the SVM is unavailable on the hypervisor where Kaspersky Security 3.0 Light Agent is installed, the application selects an available SVM with the least number of client machines from another hypervisor. In this case, virtual machines are protected but no tags can be specified for these protected virtual machines.
As soon as the SVM on the same hypervisor becomes available, Kaspersky Security 3.0 Light Agent connects to it.
In some cases, you may need to disable the SVM search option and specify an SVM manually.
If Kaspersky Security 3.0 Light Agent is not connected to any SVM for more than 30 minutes, it notifies Kaspersky Security Center that protection components are disabled.
Release of antivirus database updates (required to protect your computer/server/mobile device)
Providing technical support over phone / web
Release of patches for the application (addressing detected bugs)
To run Kaspersky Security for Virtualization on an SVM, the following minimum system resources are required:
For correct work of the application in the virtual infrastructure, one of the following hypervisors must be installed:
It is only possible to connect Light Agent to an SVM and ensure the correct functioning of the application if you have deployed Light Agent and the SVM on the platforms for which they are intended. That is, connecting Light Agent deployed on Hyper-V or Citrix platforms to SVMs installed to VMware hypervisors is not supported. Conversely, connecting Light Agent deployed on a VMware platform, to SVMs installed on Hyper-V or Citrix hypervisors is not supported.
For installation and correct work of SVMs installed on a VMware ESXi hypervisor, VMware vCenter server version 5.5 or 6.0 with all available updates must be installed in the virtual infrastructure.
To deploy an SVM on a KVM hypervisor running the CentOS, you must remove or comment out the Defaults requiretty line in the /etc/sudoers configuration file of the hypervisor's operating system.
Installing an SVM on a Microsoft Windows Server (Hyper-V) hypervisor that is not a part of an Active Directory domain requires that Windows Remote Management (WinRM) version 3.0 be installed on the hypervisor. WinRM 3.0 is a part of the Windows Management Framework 3.0 distribution that is available for download on Microsoft official website.
Protected virtual machines require one of the following guest operating systems:
Core Edition is not supported for the following operating systems:
Supported versions of Citrix XenDesktop, Citrix PVS, and VMware Horizon.
Kaspersky Security 3.0 Light Agent Maintenance Release 2 (version 184.108.40.20624):
Kaspersky Security 3.0 Light Agent Service Pack 1 (version 220.127.116.1177):
For installation of the Light Agent component to a virtual machine with Windows 10 as a guest operating system, use the latest Windows 10 installer version with all available updates.
Please let us know how we can make this website more comfortable for you
Enter your feedback here (max. 500 characters)
Thank you for submitting your feedback.
We will review your feedback shortly.