About activating Kaspersky Security for Virtualization 6.2 Light Agent

Solution activation is the process of activating a license that allows you to use a fully-functional version of the solution until the license expires.

To activate Kaspersky Security for Virtualization 6.2 Light Agent, you need to add the main license key for the solution to all the SVMs. Adding a key to an SVM lets you activate all components of the solution. You do not need to separately activate the applications used as Light Agents in the solution.

If your main license does not include additional Light Agent functionality that you need (for example, integration with the Kaspersky Detection and Response solution), then in order to use this functionality, you need to add a separate license key for activating the additional functionality to the SVM after you add the main license key for the solution.

To add reserve keys to the SVM, use the Solution activation task for the Protection Server. The activation task allows you to add a key that is stored in Kaspersky Security Center key storage of to the SVM.

Automatic distribution of license keys is not supported.

Put a key in the Kaspersky Security Center key storage while creating an activation task or in advance. You can add a key to the Kaspersky Security Center key storage in one of the following ways:

• Using the key file
• Using the activation code

After activating the solution on an SVM, the Protection Server component installed on this SVM sends license information to Light Agents connected to the SVM. If the key status changes, the Protection Server notifies the Light Agents.

If the license information is not sent, the Light Agent ceases to perform its functions.

Information about license keys added to the SVM can be viewed in the Kaspersky Security Center Administration Console or in the Web Console. You can view information about the license used by Light Agent on a protected virtual machine with Light Agent.

The solution must be activated on an SVM with an accurate system date and time. If the system date and time are changed after activation of the solution, the key becomes void. The solution switches to a mode without database updates, and Kaspersky Security Network is unavailable. In this case, you need to redeploy the SVM and activate the solution on the SVM.

If your infrastructure has multiple instances of the Kaspersky Security solution installed running on multiple Kaspersky Security Center Administration Servers that are not organized in a hierarchy, you can activate different instances of Kaspersky Security by adding the same key. A key previously added to an SVM administered by a single Kaspersky Security Center Administration Server can be added to an SVM administered by a different Kaspersky Security Center Administration Server if the validity period of the license linked to the key has not expired.

When license restrictions are checked, the total number of licensing units on which the key is used on all Kaspersky Security Center Administration Servers is taken into account.

To use a previously added key without violating licensing restrictions:

1. Remove SVMs on which the solution has been activated using this key on the same Kaspersky Security Center Administration Server.
2. Create and run a Solution activation task on a different Kaspersky Security Center Administration Server. A key added to the Kaspersky Security Center key storage can be exported in advance from one Kaspersky Security Center Administration Server to another Administration Server (see the Kaspersky Security Center help for details).

Conditions for activating the solution using an activation code

To be able to add a key to the Kaspersky Security Center key storage and activate the solution using an activation code, you need a connection to Kaspersky activation servers. The Key Storage Wizard sends data to Kaspersky activation servers to validate the activation code that was entered.

The activation proxy service establishes a connection to the activation servers. If the activation proxy service is disabled, the key cannot be added to the storage by using an activation code. If Internet access is provided via a proxy server, the proxy server settings must be configured in the properties of the Kaspersky Security Center Administration Server.

For more detailed information about the activation proxy service and proxy server settings, please refer to the Kaspersky Security Center help.

Important considerations when adding keys

When adding keys, you should take the following into consideration:

• You cannot add multiple active license keys of the same type providing basic functionality to a single SVM (for example, multiple server keys or multiple keys with a restriction on the number of processors). If a license key has already been added to an SVM, and you add a new key of the same type, then the new key replaces the previously added key.
• If you are using a licensing scheme based on the number of protected virtual machines that distinguishes server keys and desktop keys, on the SVM you must add a key that matches the type of the guest operating system of the virtual machines you want to protect:
  • If the SVM only protects virtual machines with server operating systems, you need to add a server key to the SVM.
  • If the SVM only protects virtual machines with desktop operating systems, you need to add a desktop key to the SVM.
  • If the SVM protects virtual machines with server operating systems and desktop operating systems, you need to add two keys to the SVM: a server key and a desktop key.

  If you are using a licensing scheme based on the number of protected virtual machines regardless of the operating system type, a licensing scheme based on the number of CPU cores, or a licensing scheme based on the number of CPUs, you need one key (with the corresponding licensing limitation) regardless of the operating system of the protected virtual machines.

• Simultaneous use of keys corresponding to different licensing schemes to activate basic functionality on SVMs is not supported. If a license key providing basic functionality has already been added to an SVM, and you add a new key corresponding to a different licensing scheme, then the new key replaces the previously added key. For example, suppose a desktop key and a server key have been added to SVMs (licensing scheme based on the number of virtual machines), and then you add a core-limited key (licensing scheme based on the number of cores). The task will remove the active and (if any) reserve desktop and server keys. They are replaced by the key with a limitation on the number of processor cores, which is added as an active key.

  A desktop key and server key can be used simultaneously on SVMs — these keys correspond to the same licensing scheme (based on the number of virtual machines).

• A key that was removed from one SVM can be added to another SVM if the term of the license bound to the key has not expired.
• Simultaneous use of commercial keys and subscription keys on an SVM is not supported. For example, if you add a commercial key on an SVM with a previously added subscription key, the subscription key is removed from the SVM. The commercial key is added in its place.
• A reserve key can be added only if an active key has been added The active and reserve keys must have the same license restriction type and must correspond to the same license type (Standard license / Enterprise license).
• A key for additional functionality can be added to an SVM regardless of the type of main license key added to that SVM.
• A key for additional functionality can be added only after adding the main license key for the solution.
• You cannot add multiple active license keys to an SVM to activate the same additional functionality of Light Agents (for example, multiple keys to activate the Kaspersky Endpoint Detection and Response Optimum functionality). If an SVM already has some additional functionality activated and you add a new key to activate the same additional functionality, the new key replaces the previously added key.