VMware VirtualCenter 1.4.1 Patch 2
This document contains the following information:
As detailed in Resolved Issues, this update includes improvements in certificate handling for SDK developers (users of the 1.x Web service), and for VirtualCenter administrators who use templates to create ESX Server, GSX Server, or VMware Server system clones. This patch also includes improvements to license-information-handling for quad-core-based ESX Server systems.
If you do not use the SDK or templates on your VirtualCenter, or if you do not need to manage quad-core-based server systems from VirtualCenter, you do not need to install this upgrade.
This update includes changes to VirtualCenter 1.4.1 Server and to VirtualCenter 1.4.1 Client software: If you upgrade a VirtualCenter Server host using this update, you must also upgrade all VMware VirtualCenter Client hosts. You can upgrade the Windows client hosts by downloading the software from an upgraded VirtualCenter Server host, or by selecting VirtualCenter Client from the VirtualCenter installation program.
VirtualCenter 1.4.1 Patch 2 (Build 36208) resolves several issues, resulting in these improvements:
Templates with Server-Certificate-Verification Enabled No Longer Limited to IP Addresses: A defect in how certificates were being handled by VirtualCenter templates has been resolved, so the workaround described in the VirtualCenter 1.4.1 Patch 1 patchnote is no longer required: you can install VirtualCenter 1.4.1 Patch 2, enable server-certificate verification, and use fully-qualified domain names (FQDN) to create templates (in VirtualCenter Server repository) for ESX Server, GSX Server, or VMware Server hosts.
Quad-Core Server Support: A restriction on the number of licensed physical CPUs supported has been removed, enabling quad-core-CPU-based ESX Server systems to be managed by VirtualCenter using one license per CPU. Previously, quad-core CPUs consumed two licenses each. Note that the restriction still applies to the VMware Server 1.x.x systems being managed by VirtualCenter: See the
Valid Certificate Provided for Web Service: The default self-signed X.509 certificate generated during the installation process for the VirtualCenter Web Service (used by the 1.x SDK) now has a 7-year life. The certificate provided in previous releases had an expiration date of 13-November-2006.
Note this limitation of this update:
- VMware Server Systems Running on Quad-Core, Dual-CPU Systems Consume 8 (instead of 2) CPU licenses. Attempting to manage VMware Server 1.x.x systems (running on quad-core dual-CPU systems) using this release is not recommended due to an issue with the VMware Server that reports CPUs on a per-core (rather than a per-socket) basis.
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 the Patch
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.
- 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.