Kaspersky Security for Virtualization 1.1

 
 
 

Known issues in Kaspersky Security for Virtualization 1.1  (version 1.1.0.54)

Back to "Troubleshooting"
2012 Dec 03 ID: 8459
 
 
 
 
  • The application cannot be used with Kaspersky Security Center via a connection gateway.
  • After changing or reinstalling vCenter Server, all existing policies and tasks would stop functioning. It is recommended to delete all the existing policies and tasks and create new ones.
  • After reconnecting vCenter Server to a new Administration server or changing/reinstalling Kaspersky Security Center 9.0 (without backup), it is recommended to reinstall Kaspersky Security for Virtualization 1.1 on each ESXi host by running the uninstallation wizard and the setup wizard afterwards.
  • If there are several virtual machines with the same ID, the protection profile assigned to any of them would be applied to all of them. You can change the ID by deleting the duplicate and adding it to vCenter Server Inventory. Then assign the protection profile to this virtual machine in the policy.
  • The only possible update source to download antivirus updates databases from is the Kaspersky Security Center Administration server repository. It is impossible to use a local folder or a public resource as an update source.
  • The application updates databases only from the storage of the Kaspersky Security Center Administration Server. A local directory or public resource cannot be used as a source of updates.
  • Virtual machine counters are not supported:
    • The statistics view functionality is not implemented.
    • Object counters are not supported: number of infected objects, disinfected objects, skipped objects, instances of failed disinfection, deleted objects, objects that caused scan errors. 
    • Threat type counters are not supported (threat detection statistics).
    • Virtual machine counters are not supported: number of scanned virtual machines, number of skipped virtual machines, number virtual machines queued for scanning, number of virtual machines that caused scan errors.
  • The application does not support updates to the SVM image. Updating an SVM image involves deleting the previous SVM image and installing a new one.
  • There is no quarantine for infected objects. Protection settings can be configured in a way that causes infected files to be blocked instead of being deleted.
  • There is no backup for objects (deleted or modified during disinfection).
  • The application does not protect virtual machines that are disabled or suspended (offline).
  • There is no report on completed scan tasks. Instead, the history of scan tasks can be viewed in Kaspersky Security Center.
  • System and custom variables of the Windows operating system cannot be used to configure exclusions in scan tasks and in protection settings.
  • The "*" and "?" masks are not supported for the purposes of specifying file extensions.
  • Automatic distribution of keys through Kaspersky Security Center is not supported.
  • The application does not support command line control.
  • All SVMs need to be reinstalled after Kaspersky Security Center has been updated. The certificates authorizing application connection to Kaspersky Security Center change after Kaspersky Security Center has been updated.
  • Remote reinstallation of certificates authorizing connection to Kaspersky Security Center is not supported.
  • The Pause and Resume commands are not supported for the scan task.
  • The application does not scan network folders during the scan task. Network folders are scanned as part of the protection functionality.
  • By default, the application does not scan removable drives during the scan task. Removable drives can be scanned by directly specifying a path to them in the scan task settings.
  • Handling of a situation involving a forced shutdown of a virtual machine or an SVM:
    • The application does save the status of scan tasks when a protected virtual machine is shut down or suspended. As soon as the virtual machine is enabled (goes online), the application places it in the scan task queue.
    • The application does save the status of scan tasks when an SVM is shut down or suspended. The subsequent launch of scan tasks is controlled by Kaspersky Security Center: tasks are launched when the SVM is enabled or according to the task schedule.
  • The application saves a list of virtual machines before running a scan task and does not update this list during tasks. If new virtual machines appear in the VMware virtual architecture after the scan task has started, they are not scanned.
  • There is no functionality for forcing a file unblocked if the application has blocked access to it. The administrator has to either add this file to exclusions in policy settings or temporarily disable protection in order to manage this file (delete, copy, etc.).
  • Due to technological restrictions of VMware vShield Endpoint platform, the application does not work on VMware clusters in Fault Tolerance mode and does not protect virtual machines with the Fault Tolerance mode enabled. We recommend installing Kaspersky Endpoint Security for Windows on virtual machines with the Fault Tolerance mode enabled.
  • The application does not support VMware vCenter Server Linked Mode.
    VMware Distributed Power Management on a VMware cluster stops working properly if SVMs are installed and running on VMware ESXi hosts.
  • The VMware ESXi host will not go into standby mode as long as an SVM is running.
 
 
 
 
Did the provided info help you?
Yes No
 
 
 

Applies To:

  • Kaspersky Security for Virtualization 1.1