Viewing the key usage report

25 March 2022

ID 58851

To view the key usage report:

  1. Open the Administration Console of Kaspersky Security Center.
  2. In the workspace of the Administration Server node, go to the Reports tab.
  3. In the list of report templates, select the Key usage report template and open the report window by using one of the following methods:
    • By double-clicking.
    • Right-click to open the context menu and select Show report.

    This opens a window containing the report that was generated from the Key usage report template.

The chart in the upper part of the window, shows the following key usage details for each key:

  • Number of licensing units on which the key is already in use
  • Number of licensing units on which the key can be used according to the licensing restrictions
  • Number of licensing units by which the licensing restrictions for the key are exceeded

The key usage report consists of two tables:

  • The summary table contains information about the keys in use
  • The detailed information table contains information about SVMs on which keys have been added, or about virtual machines for whose protection the key is used

You can configure the content of fields shown in each table. See Kaspersky Security Center documentation on how to add or remove fields in the report tables.

The summary table contains information about the keys in use:

  • Key. A unique alphanumeric sequence.
  • Total keys used as active. Depending on the key type:
    • For a server or desktop key – the number of virtual machines for whose protection the key is used.
    • For a key with a limitation on the number of processor cores – the number of physical processor cores used on all VMware ESXi hypervisors on which SVMs are deployed.
    • For a key with a limitation on the number of processors – the number of physical processors used on all hypervisors whose virtual machines you can protect.
  • Total keys used as additional. The number of SVMs on which the key has been added as an additional key.
  • Limit. Depending on the key type:
    • For a server key – the maximum number of virtual machines with a server operating system that you can protect.
    • For a desktop key – the maximum number of virtual machines with a desktop operating system that you can protect.

      For server and desktop keys, the license restriction count includes all virtual machines that were under the protection of the application over the last 30 days, even if those virtual machines are currently powered off. If you do not want a virtual machine to be included in the license restriction count, you can exclude the virtual machine from the protected virtual machines.

    • For a key with a limitation on the number of processor cores – the maximum number of physical processor cores used on all hypervisors whose virtual machines you can protect.
    • For a key with a limitation on the number of processors – the maximum number of physical processors used on all hypervisors whose virtual machines you can protect.
  • The license expiration date. The date when your right to use the application activated with your current key expires.
  • Use key until. The key's expiration date.
  • Total keys used as active for workstations. The number of virtual machines with desktop operating systems for whose protection the key is used.
  • Total keys used as active for servers. The number of virtual machines with server operating systems for whose protection the key is used.
  • Service info. Service information relating to the key and license.

    The row below contains the following consolidated information:

    • Keys. Total number of keys in use.
    • Keys are more than 90% used. Total number of keys that have been used up by more than 90% of the usage time available under the licensing restriction. For example, the restriction is set at 100 virtual machines. A key is used on two SVMs: the first one protects 42 virtual machines and the second one protects 53 virtual machines. The key is therefore 95% used and is included in the number of keys specified in this field.
    • Keys with exceeded limit. Total number of keys that have exceeded the limit imposed on the number of protected virtual machines with server or desktop operating systems or the number of physical processor cores used on all hypervisors (depending on the key type).

The detailed information table shows information about the SVM on which the key has been added (for keys of all types) and information about the protected virtual machine for which the key is being used (for a server or desktop key):

  • Group. The administration group that includes the SVM with the added key.
  • Device name. The name of the SVM for which the key was added or the name of the protected virtual machine for which the key is used.
  • Application. The name of the application that was activated by adding this key on the SVM.
  • Version number. The version number of the application that was activated by adding this key on the SVM.
  • Active key. The key that was added as an active key on the SVM or that is used for protection of the virtual machine.
  • Additional key. The key that was added as the additional key on the SVM.
  • License valid until. The expiration date for using the application with this key.
  • IP address. The IP address of the SVM on which the key was added or the IP address of the protected virtual machine.
  • Visible. The date and time when the SVM or virtual machine was last visible on the corporate LAN.
  • Last connection to Administration Server. The date and time of the last connection between the SVM and the Kaspersky Security Center Administration Server.
  • NetBIOS name. The name of the protected virtual machine and the path to it in the virtual infrastructure.
  • DNS name. The domain name of the SVM or the name of the protected virtual machine and the path to it in the virtual infrastructure.
  • Use key until. The key's expiration date.
  • Used. Depending on the type of key:
    • For a server or desktop key – the number of virtual machines with desktop or server operating systems that are under the protection of the application.
    • For a key with a limitation on the number of processor cores – the maximum number of physical processor cores used on all hypervisors on which SVMs are deployed.
    • For a key with a limitation on the number of processors – the number of physical processors used on all hypervisors on which SVMs are deployed.
  • Used for workstations. The number of virtual machines with desktop operating systems that are under the protection of the application.
  • Used for servers. The number of virtual machines with server operating systems that are under the protection of the application.

If both a server key and desktop keys have been added on an SVM, the Kaspersky Security Center key usage report displays the following information about the combination of the server key and desktop key:

  • Key, Active key, Additional key. A unique combination of a server key and a desktop key.
  • Earliest date of key expiration. The later of the following two following dates: the end date of application usage under the server key, or the end date of application usage under the desktop key.
  • Use key until. The later of the following two dates of key expiration: server key expiration date or desktop key expiration date.
  • Used as active. The total number of virtual machines with desktop and server operating systems for whose protection the key is being used.
  • Limit. The sum of the following values: the maximum number of protected virtual machines with desktop operating systems plus the maximum number of protected virtual machines with server operating systems.
  • Used. The total number of virtual machines with desktop and server operating systems that are under the protection of the application.

Did you find this article helpful?
What can we do better?
Thank you for your feedback! You're helping us improve.
Thank you for your feedback! You're helping us improve.