Microsoft .NET Framework 4.0 or later is installed on a computer with the Kaspersky Security Center Administration Console installed. Microsoft .NET Framework 4.0 or later is required for the work of the setup wizard.

The XenTools application is installed on virtual machines managed by Citrix XenServer hypervisor.

The VMware Tools application is installed on virtual machines you are planning to protect with the VMware ESXi hypervisor.

The computer on which Kaspersky Security Center Administration Console is installed connects to the VMware vCenter™ server not using proxy server.

No third-party antivirus software is installed on virtual machines you are going to protect with Kaspersky Security 3.0 Light Agent. If there is any third-party antivirus software installed, we recommend to remove it; otherwise, serious conflicts may arise.

Network traffic is allowed to pass through certain ports so that components be installed and run.

If you want the credentials of the hypervisor administrator account to be transmitted encrypted during the installation of the SVM, establish a protected SSL connection between the hypervisor on which the SVM will be installed and the computer with the Kaspersky Security Center Administration Console which will be managing the installation (for detailed information, see the Microsoft knowledge base);

If you want virtual machines with Kaspersky Security 3.0 Light Agent components installed to be transferred into administration groups automatically after the installation, in the Kaspersky Security Center Administration Console, create administration groups and set the rules for automatic transfer of virtual machines to administration groups.

If you want Kaspersky Security 3.0 Light Agent to connect to a certain SVM, disable SVM search before installing the component.

For correct installation and functioning of Kaspersky Security for Virtualization 3.0, the following Kaspersky Security Center components listed below are required.

Administration Server with the following services configured:

Activation Proxy is required for activating Kaspersky Security for Virtualization 3.0. You can configure Activation Proxy in the properties window of Kaspersky Security Center Administration Server. If Activation Proxy is disabled, it will be impossible to activate the software with the activation code.

KSN Proxy is required for the exchange of data between Kaspersky Security for Virtualization 3.0 and the Kaspersky Security Network services. You can configure KSN Proxy in the properties window of Kaspersky Security Center Administration Server. If KSN Proxy is disabled, no data will be transferred between Kaspersky Security for Virtualization 3.0 and the Kaspersky Security Network services.

Administration console. The component must be installed on the administrator's workstation.

Activation. To activate Kaspersky Security for Virtualization 3.0 Light Agent, create a key distribution task to distribute the key to all SVMs.

Databases update. To update the databases of Kaspersky Security Light Agent, download the updates from the Administration server repository to a folder on the SVM. To download the updates, create an update task on the SVM.

Installing Kaspersky Security Center Network Agent on all virtual machines on which you would like to manage Kaspersky Security Light Agent via Kaspersky Security Center.

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: