VMware VirtualCenter 2.0.1 Patch 1
This document contains the following information:
VirtualCenter 2.0.1 Patch 1 (Build 33643) resolves several issues and provides these enhancements:
- Windows-based VirtualCenter clients and VirtualCenter Server can now perform proper SSL server-certificate verification when establishing connections. Note that installing the updated software does not, by default, enable the feature. For information about how to enable this new optional capability, see
Knowledge Base (KB) article 4646606, "Enabling Server-Certificate Verification for Virtual Infrastructure Clients."
- Journal-file handling during rollback operations has been improved to prevent rare, erroneous deletion of VMs. If a VirtualCenter agent crashed at the end of a VM transfer, the successful completion of the transfer was not able to be recorded. A subsequent recovery step thus identified the VM on the destination host as a corrupted partial copy, and deleted it. This logic error has been corrected.
Norwegian locale name support in the English version of VirtualCenter 2.0.1 has been improved. With this update, the work-around for the English version of the 2.0.1 (described in KB article
VirtualCenter 2.0.1 Issues with Certain Norwegian Locales
") is no longer required.
- The CPU idle performance counter now displays with the correct label. The CPU idle performance counter had been erroneously displaying as the CPU wait perf counter.
- Japanese language handling for CD-ROM and other device mountpoints on virtual machines has been improved. In addition, some Japanese and German localization issues for VI (Virtual Infrastructure) clients have been resolved.
- Various other display improvements, including the elimination of garbled text in Event tab for Japanese localized version of VirtualCenter user interface.
This update includes changes to VirtualCenter Server and VirtualCenter Client software. If you upgrade a VirtualCenter Server host using this update, you must also upgrade all VMware VirtualCenter Client hosts that connect to the server. You can upgrade the Windows client hosts by downloading the software from an upgrade VirtualCenter Server host, or by select Virtual Infrastructure Client from the VirtualCenter installation program.
Note these known issues and limitations of the update:
This software update does not resolve the server-certificate verification issue for the MKS (mouse-keyboard-screen) plug-in for the Mozilla Firefox Web browser on either Windows or Linux. This issue will be resolved in a future release.
Before You Begin
As with any upgrade or installation process, you should backup the VirtualCenter database prior to upgrading the VirtualCenter server. Although this update makes no VirtualCenter database schema changes, VMware recommends backing-up the VirtualCenter database prior to an upgrade.
Installing VirtualCenter Server 2.0.1 Patch 1
VirtualCenter software updates require full installation of the software. As with a fresh install, the VirtualCenter installation program examines the local system, identifies any existing VirtualCenter installation, and guides you through the installation (or upgrade) process.
If VirtualCenter components are already installed on the host machine, the installation program prompts for confirmation that you want to upgrade.
To install the updated version of the VirtualCenter:
- Backup your VirtualCenter database (as recommended above).
- Download the
software installation file.
- Run the executable.
- Select "Yes" to upgrade an existing Installation.
- Step through the VirtualCenter Installation Wizard, selecting your existing VirtualCenter database instance, and entering the VirtualCenter database schema username and password as required.
- After upgrading the VirtualCenter Server, connect to the server from each of the existing VirtualCenter clients to obtain the updated client software.
For complete information about installing or upgrading VirtualCenter, see Installing
and Upgrading the VirtualCenter Product.
To enable SSL certificate client-side authentication, see the KB article 4646606, "Enabling Server-Certificate Verification for Virtual Infrastructure Clients."