Security for Virtualized Environments Version 1.2.1 Release Notes
Security for Virtualized Environments (SVE) is the first comprehensive security solution for virtualized datacenters. The solution protects virtualized Windows, Linux, and Solaris systems, both servers and desktops. While integrated with VMware vShield, the unique architecture of the solution allows it to be leveraged when using any system virtualization offering.
This article provides information on the improvements introduced in Security for Virtualized Environments version 1.2.1 (released on May 29, 2012), the list of known issues and the upgrade procedure.
Version 1.2.1 is a minor update to version 1.2 (it is also referred to as Version 1.2 Update 1). This version delivers only a few minor improvements for VMware vSphere and fixes some of the known issues mentioned in Version 1.2 Release Notes.
New License Exceeded notifications, configurable from the Settings > Notifications page. By configuring this type of notifications, admins can be notified in a timely manner when the ratio between the number of license seats in use and the total number of seats allowed by the license exceeds a specified threshold.
Product documentation, including help files and PDF guides, is now available in German, French and Spanish. Localized documentation is now loaded based on the display language of Security Console.
The following known issues occurring in VMware vSphere environments have been fixed:
- When removing the Security Virtual Appliance from a host, although the quarantined files stored on the appliance are removed, they still show up on the Quarantine page of Security Console.
- If a VM on which a task has been configured to run is deleted while the task is pending or running, or if the user rights on the VM are removed, the VM disappears from the task details page.
- The following known issue occurring in Citrix XenServer/XenDesktop and Microsoft Hyper-V environments has been fixed:
- Memory leaks occurred on Linux clients after on-demand scan endurance tests.
Except for the resolved issues, all other known issues mentioned in Version 1.2 Release Notes are still present. Product and corresponding documentation for Citrix and Microsoft environments is still only available in English. There are no other known issues for this release.
For information on upgrading from a version prior to 1.2, refer to this KB article.
To upgrade from version 1.2, follow the information provided hereinafter. You need to upgrade both the SVE appliances and agents.
Upgrading from version 1.2 in VMware vSphere
Upgrade can be performed from Security Console:
- Prerequisite: Check that all Security Virtual Appliance instances installed in your environment are up and running and that they communicate with the Security Console appliance. For example, appliances must be powered on.
- Connect to Security Console via HTTPS.
- Go to the Computers > Security VMs page. You can see that updates are available for installed appliances.
- Click the Update link corresponding to the Security Console appliance to upgrade all installed appliances.
- Wait for all appliances to be upgraded.
If you have deployed Silent Agent on virtual machines, go to the Computers > Silent Agents page to upgrade them.
- Select all VMs listed in the table.
- Click Actions and choose Upgrade Silent Agent.
Upgrading from version 1.2 in Citrix XenServer/XenDesktop and Microsoft Hyper-V
The upgrade procedure requires manually updating each installed appliance from the command line interface of each virtual machine.
Upgrade can be performed by following these steps:
Upgrade Security Console by running the following commands in the appliance’s CLI:
$ apt-get update
$ apt-get install bitdefender-web-server
Upgrade Security Virtual Appliance by running the following commands in the appliance’s CLI:
$ apt-get update
$ apt-get install bitdefender-scan-server
Windows Silent Agent is automatically upgraded during regular update process. Linux Silent Agent must be upgraded by reinstalling it using the new packages available in the upgraded Security Console version. For more information on installing Linux Silent Agent, refer to the Administrator’s Guide.