Known limitations in Kaspersky Security for Virtualization 3.0

 

Kaspersky Security for Virtualization 3.0 | Light Agent

 
 
 

Known limitations in Kaspersky Security for Virtualization 3.0

Back to "Version Info"
2018 Apr 19 ID: 10704
 
 
 
 

There are a number of limitations in Kaspersky Security for Virtualization 3.0:

  1. The license is not updated automatically after an SVM has been rolled back to the snapshot. For example, if an SVM has been activated using a commercial license and then rolled back to the SVM snapshot that had been activated using a trial license, the license is not updated from trial to commercial automatically after the rollback. This issue can be resolved by restarting the SVM using Kaspersky Security Center.

  2. This issue applies to Citrix XenServer hypervisors: The operating system crashes due to a hypervisor error on an SVM with Windows Vista Ultimate SP2 x32 guest operating system and Light Agent installed. 

  3. Light Agent blocks connections to FTP servers established using the standard FTP client of Windows.

  4. After Light Agent is removed and then reinstalled locally on a protected virtual machine (not via Kaspersky Security Center), Light Agent stops sending event information to Kaspersky Security Center. This issue can be resolved by restarting Light Agent.

  5. The SVM Reconfiguration Wizard does not support international domain names (IDN) of virtual machines (names containing non-Latin characters).

  6. A key from the key storage of Kaspersky Security Center cannot be applied to SVMs that have been added to the Managed Computers folder.

  7. Policies are not applied to Light Agent if its protection has been paused. This issue can be resolved by enabling protection before applying the policy.

  8. The Add trusted devices window of the Device Control component of Light Agent displays incorrect information about volumes created on the drive. Physical drive information is displayed correctly.

  9. The functionality that grants temporary access to devices does not work in the Device Control component of Light Agent.

  10. A file can be restored from Backup only to the drive folder from which the file had been moved to Backup. The file cannot be restored to a folder at a different path.

  11. If Light Agent has been installed to a folder with the name containing non-Latin characters, these characters appear as question marks in Light Agent reports.

  12. If Light Agent has been installed to a folder with the name containing non-Latin characters, the email scan plug-in is not installed in Microsoft Outlook.

  13. During local installation of Light Agent, the Initial Configuration Wizard can take a long time to open (up to 30 seconds).

  14. The actual start time of scheduled tasks can differ from the configured start time due to time zone differences between Light Agent and Scan Server. Light Agent receives information about available licenses, updates, and database rollbacks according to the time setting of Scan Server without regard for the time zone setting of Light Agent. The time zone of Scan Server corresponds to UTC.

  15. By default, Kaspersky Security Center does not include the pre-installed installation package of Light Agent (in the Preinstalled packages section).

  16.  The "Protection components are disabled" message with the description "Post-infection system restore is required" sometimes appears in Kaspersky Security Center reports after Light Agent has been installed via Kaspersky Security Center.

  17. When hierarchically interconnected servers of Kaspersky Security Center are used and the hierarchy includes Kaspersky Security Center version 9.2, Scan Servers managed by Kaspersky Security Center that is located hierarchically lower do not receive Anti-Virus database updates. 

  18. A group update task created at the Scan Server installation stage does not generate events and does not reset startup counters. This issue can be resolved by deleting the task created at the Scan Server installation stage and creating this task anew.

  19. After an SVM is rolled back to its snapshot, the tasks created on the SVM after the snapshot was last saved disappear. 

  20. When Anti-Virus databases are updated on Light Agent, the values of download speed counters and the counter of bytes downloaded always appear as zero.

  21. The status of an SVM in the console does not change to Warning (yellow) when the local account that was automatically created during SVM installation is disabled. This issue applies to SVMs deployed on Windows Server 2008 R2 Hyper-V and Windows Server 2012 Hyper-V hypervisors.

  22. After a Block all rule is created in the Firewall settings of Light Agent, the policy is applied on this Light Agent with a 15-minute delay.

  23. Advanced Disinfection technology does not work when Light Agent is installed using Kaspersky Security Center tools. Light Agent installation using Kaspersky Security Center tools fails with the following error: “Error installing driver klim”. This issue applies to configurations with Citrix XenServer hypervisors.

  24. If the config.sys system file is infected, the scan task deletes it without saving a copy in Backup (after the protected virtual machine is restarted).

  25. This issue applies to configurations with Citrix XenServer hypervisors that are part of a pool: after an SVM is migrated to a different pool hypervisor with more processor cores than the original hypervisor, Kaspersky Security Center may start receiving License Agreement violation messages. This error occurs when the SVM is licensed for a smaller number of processor cores than the destination hypervisor has.

  26. When Light Agent is installed for a second time using Kaspersky Security Center tools, a critical error may occur (Fatal error during installation) that interrupts the installation process and corrupts the previously installed Light Agent. This error occurs if Light Agent was first installed with all components included in the installation package, and the installation package was modified before the second installation by disabling certain components (such as the Mail Anti-Virus component).

  27. Each time a new SVM appears in Kaspersky Security Center a tag corresponding to the name of the virtual machine is added. The tag is not deleted after the virtual machine is deleted.

  28. After the additional key is added, the information about the added key is displayed incorrectly in the SVM properties.  

  29. If the device was disabled or restarting during scan, yoy will need to restart the task manually in Kaspersky Security Center.

  30. Kaspersky Security for Virtualization 3.0 Light Agent cannot be installed on terminal servers.

 
 
 
 
Was this information helpful?
Yes No
Thank you
 

 
 

How can we improve this article?

Your feedback will be used for content improvement purposes only. If you need assistance, please contact technical support.

Submit Submit

Thank you for your feedback!

Your suggestions will help improve this article.

OK