The Kaspersky applications installed on managed devices must be licensed by applying a key file or activation code to each of the applications. A key file or activation code can be deployed in the following ways:
You can add a new active or reserve license key by any of the methods listed above. A Kaspersky application uses an active key at the current moment and stores a reserve key to apply after the active key expires. The application for which you add a license key defines whether the key is active or reserve. The key definition does not depend on the method that you use to add a new license key.
Automatic deployment
If you use different managed applications and you have to deploy a specific key file or activation code to devices, opt for other ways of deploying that activation code or key file.
Kaspersky Security Center allows you to automatically deploy available license keys to devices. For example, three license keys are stored in the Administration Server repository. You have enabled the 自動分發的產品授權金鑰 option for all three license keys. A Kaspersky security application—for example, Kaspersky Endpoint Security for Linux—is installed on the organization's devices. A new device is discovered to which a license key must be deployed. The application determines, for instance, that two of the license keys from the repository can be deployed to the device: license key named Key_1 and license key named Key_2. One of these license keys is deployed to the device. In this case, it cannot be predicted which of the two license keys will be deployed to the device because automatic deployment of license keys does not provide for any administrator activity.
When a license key is deployed, the devices are recounted for that license key. You must make sure that the number of devices to which the license key was deployed does not exceed the license limit. If the number of devices exceeds the license limit, all devices that were not covered by the license will be assigned Critical status.
Before deployment, the key file or activation code must be added to the Administration Server repository.
How-to instructions:
Note that an automatically distributed license key may not be displayed in the virtual Administration Server repository in the following cases:
Adding a key file or activation code to the installation package of a managed application
For security reasons, this option is not recommended. A key file or activation code added to an installation package may be compromised.
If you install a managed application using an installation package, you can specify an activation code or key file in this installation package or in the policy of the application. The license key will be deployed to managed devices at the next synchronization of the device with the Administration Server.
How-to instructions: Adding a license key to an installation package
Deployment through the Add license key task for a managed application
If you opt for using the Add license key task for a managed application, you can select the license key that must be deployed to devices and select the devices in any convenient way—for example, by selecting an administration group or a device selection.
Before deployment, the key file or activation code must be added to the Administration Server repository.
How-to instructions:
Adding an activation code or a key file manually to the devices
You can activate the installed Kaspersky application locally, by using the tools provided in the application interface. Please refer to the documentation of the installed application.
Page top