[an error occurred while processing this directive]


VMware VirtualCenter 1.3.x Release Notes

Check back frequently for additions and updates to these release notes.

Version 1.3.1 patch 1 | 3/23/06 | Build 22214
Version 1.3.1 | 12/22/2005 | Build 18881

Last update to Release Notes: May 2, 2006

Version 1.3.x

View all the Knowledge Base articles related to the VirtualCenter 1.3 and 1.3.1 releases.

What's New in This Release

VirtualCenter 1.3.1 patch 1 is a patch release to correct a very rare but potentially serious situation:

  • Data loss might occur from a cold-migration, if a network failure occurs at the same time as the migration and the migration keeps the disk files on the same shared VMFS SAN volume. Refer to KB article 2070 for additional information.

    Note:Review the updated Installation and Upgrade Instructions.

VirtualCenter 1.3.1 is a maintenance bug fix release to improve upon VirtualCenter 1.3.

VirtualCenter 1.3 is a minor release to improve upon VirtualCenter 1.2 and includes the following features:

  • Dual core processor support - Newer processors have two CPU cores in each processor package. Systems with dual-core processors must use ESX Server 2.5.2 or later or GSX Server 3.2 or later.

  • vmware-serverd process runs on an ESX Server host, even when managed by VirtualCenter, rather than the expected vmware-ccagent.
    This does not impact performance or operations of VirtualCenter, ESX Server, GSX Server, or virtual machines.
    If you are using ESX Server 2.5.2 and VirtualCenter 1.3 to manage the host, you will not see the vmware-ccagent running, as you did in previous releases. You will see the vmware-serverd running. Also, if you are using VirtualCenter 1.3 to manage an ESX Server 2.5 or 2.5.1 version, you will see vmware-ccagent running on the host.

Version Compatibility for This Release

This release version requires or functions with the listed version of the following:

 VirtualCenter version
 ESX Server version
 GSX Server version
1.3, 1.3.1 2.0.1, 2.1, 2.1.1, 2.1.2, 2.1.3, 2.5.x 3.1, 3.2
1.2 2.0.1, 2.1, 2.1.1, 2.1.2, 2.5.0, 2.5.1 3.1, 3.2
1.1 2.0.1, 2.1, 2.1.1 3.1
1.0.1 2.0.1, 2.1  
1.0 2.0.1  

NEW 5/2/06 Added ESX Server version 2.1.3 to compatibility table.

Revision History of This Release Note

1.3.1 December 22, 2005 Maintenance release
1.3 September 22, 2005 Minor release

Installing and Upgrading to Version 1.3.1 Patch 1

Patch 1 requires updating the VirtualCenter Management Server using the updated VirtualCenter 1.3.1 Patch 1 installer. Upgrades to the VirtualCenter clients may be required as well:

  • VirtualCenter clients from either version 1.3.0 (build 16701) or version 1.3.1 (build 18881) work with a patched VirtualCenter management server, though they continue to display their original build number.
  • VirtualCenter clients from version 1.2.0 (build 12684) and older will not be able to connect to a patched VirtualCenter management server, and will need to be updated.

The updated VirtualCenter 1.3.1 Patch 1 binaries are posted at the following location:

NOTE: The VirtualCenter 1.3.1 patch 1 binaries available for download are a full installer that can be used to upgrade from any previous version of VirtualCenter.

Please follow these instructions to apply the update:

  1. Backup your VirtualCenter database (standard recommendation prior to any VirtualCenter upgrade).
  2. Download the updated installer binaries from the VMware web site.
  3. Run the "VMware-vpx-1.3.1-22214.exe" executable.
  4. Select "Yes" to upgrade an existing Installation.
  5. Step through the VirtualCenter Installation Wizard, selecting the same type of database previously used, and the same username/password pair previously given to the VirtualCenter web services interface.

Installing and Upgrading to Version 1.3 and 1.3.1

The process for installing VirtualCenter for the first time and upgrading an existing installation of VirtualCenter is essentially the same. The installer determines whether a VirtualCenter component is installed on the local machine and then displays the appropriate opening screen. The difference is:

  • For an upgrade, the installation wizard opening screen asks if you wish to perform an upgrade.
  • For a first-time install, the installation wizard opening screen asks for your user name and company information.

Refer to Installing and Upgrading the VirtualCenter Product for complete information on performing an installation or upgrade of your VirtualCenter product.

In VirtualCenter 1.3.x, the installation or upgrade process also includes an option to install the VirtualCenter Web service component. The Web service component is installed on a machine that has the VirtualCenter server. If the VirtualCenter server is not already installed on the local machine, it will be installed when you select to install the Web service. For information on the VirtualCenter Web service refer to the VirtualCenter Web service web service.


  • Because changes have been made to both the VirtualCenter server and the VirtualCenter client, you must upgrade all machines with either component. VirtualCenter 1.1.x or 1.2.x client cannot connect to a VirtualCenter 1.3.x server, and VirtualCenter 1.3.x client cannot connect to a VirtualCenter 1.1.x or 1.2.x server.

  • Microsoft Windows 98SE is no longer a supported operating system for installing the VirtualCenter client.

  • If you are unable to connect to the VirtualCenter remote database during the installation, please make sure that the Workstation service (lanmanworkstation) is up and running. Also, verify that the VirtualCenter database server is up and running and that it is connected to the network.

If you are upgrading VirtualCenter, perform the following as needed:

Always backup your database before you proceed with an upgrade process.

  • If you are using an Oracle database: Prior to upgrading, make sure that shared_pool_size parameter is set to no less than 100 MB. This ensures that the upgrade performs reasonably. The shared_pool_size parameter is in the init.ora file. Have your Oracle database administrator check and set this.

  • If you are upgrading a large database: This may take a significant amount of time from several minutes to more than an hour, depending upon the size of your database.
  • Errata to the VirtualCenter User's Manual: When upgrading your VirtualCenter server be sure to answer No to the prompt An existing [name] database already exists. Do you want to overwrite the data?