VMware

VMware VirtualCenter 1.3.1 Patch 2


Released 7-Dec-2006



This document contains the following information:

Resolved Issues

VirtualCenter 1.3.1 Patch 2 (Build 35640) resolves several issues and provides these enhancements:

  • Windows-based VirtualCenter Client and VirtualCenter Server hosts can now perform proper SSL server-certificate verification when establishing SSL connections.  Note that installing the updated software does not, by default, enable server-certificate verification.  For information about how to enable this new optional capability, see Knowledge Base (KB) article 4646606, "Enabling Server-Certificate Verification for Virtual Infrastructure Clients."
  • Cold-migrating virtual machines (with Append Redo) now displays warning about potential data loss when appropriate.
  • VMotion migration between Dempsey- and Paxville-based servers is supported with this upgrade. (Intel’s dual-core Xeon "Dempsey" is the predecessor to the Intel dual-core Xeon "Paxville", for dual-processor servers.) With this software update, the work-around discussed in KB article 4893083 is no longer necessary.

Applicability

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 selecting Virtual Infrastructure Client from the VirtualCenter installation program.

Known Issues

  • The default ESX Server, GSX Server, and VMware Server host certificates are valid server certificates. However, they are self-signed, and so they are not contained in the trusted store of certificates on Windows clients, which means that if you want to enable server-certificate verification, you must do one of three things:
    • Pre-trust the default server certificates on the Windows host systems, including the VirtualCenter server Windows host system. See the Knowledge Base (KB) article 4646606, "Enabling Server-Certificate Verification for Virtual Infrastructure Clients" for more information.
    • Replace the default certificates with certificates signed by a commercial CA; or
    • Replace the default certificates with certificates signed by your local root CA. See the Technical Note, "Replacing VirtualCenter Server Certificates " for complete information. If you choose this option, you also will need to pre-trust the certificate of your local Root CA, if it’s not already in the local Windows store.
  • The default VirtualCenter server host certificates are defective, and must be replaced before enabling server-certificate verification:
    • If you replace the default VirtualCenter server certificates (or any other server certificates, such as ESX Server, GSX Server, or VMware Server hosts) with certificates obtained from a commercial Certificate Authority (CA), you can enable server-certificate immediately after upgrading. See the Knowledge Base (KB) article 4646606, "Enabling Server-Certificate Verification for Virtual Infrastructure Clients" for details.
  • This software update does not resolve the server-certificate verification issue for Remote Console clients (standalone GSX Server, ESX Server clients).

To replace the default VirtualCenter server certificates (or any other server certificates, such as ESX Server, GSX Server, or VMware Server hosts) with certificates signed by your own local Root CA, see the Technical Note, " Replacing VirtualCenter Server Certificates " for complete information.

Before Installing the Patch

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.

To install the updated version of the VirtualCenter:

  1. Backup your VirtualCenter database (as recommended above).
  2. Download the software installation file.
  3. Run the executable.
  4. Select "Yes" to upgrade an existing Installation.
  5. Step through the VirtualCenter Installation Wizard, selecting your existing VirtualCenter database instance, and entering the VirtualCenter database schema username and password as required.
  6. 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."

To replace the default VirtualCenter server certificates (or any other server certificates, such as ESX Server, GSX Server, or VMware Server hosts) with certificates signed by your own local Root CA, see the Technical Note, " Replacing VirtualCenter Server Certificates ."