VMware VirtualCenter 1.4.x Support Documentation
Knowledge Base |
VMware VirtualCenter 1.4.x Release Notes
Check back frequently for additions and updates to these release notes.
VirtualCenter Version 1.4.1 | 9/28/06 | Build 30780
VirtualCenter Version 1.4 | 7/6/06 | Build 28235
Last update to release notes: October 5, 2006.
These release notes contain the following:
Refer to the VMware Virtual Center 1.x Documentation for additional information.
What's New in This Release
VirtualCenter 1.4.1 is a maintenance bug fix release to improve upon VirtualCenter 1.4.
VirtualCenter 1.4 is a minor release to
improve upon VirtualCenter 1.3.x and includes the following
- VMware Server support - A VMware Server can now be managed by VirtualCenter as a host,
along with ESX Server 2.x and GSX Server 3.x hosts in a heterogeneous environment.
- VMware Server 64-bit support - Create and use 64-bit virtual machines and templates on VMware Server.
- VMware Server SMP support - Create and use SMP virtual machines and templates on VMware Server.
- VMware Server virtual hardware support - Create or edit virtual machines to use the additional
virtual hardware options on VMware Server. This includes the E1000 NIC and new autodetect options. Virtual machines not using the new hardware continue to be supported on ESX Server 2.x and GSX Server 3.1 or later hosts.
- VMware Server migration support - Virtual machines on ESX Server or GSX Server hosts can be migrated or imported onto VMware Server hosts. Once migrated to a VMware Server, they can be migrated back to an ESX Server or
GSX Server, provided their virtual hardware has not been upgraded through the VMware Server Console.
- Resolution of issues in previous releases. Refer to the Resolved Issues for a partial list of resolved items.
Version Compatibility for This Release
This release version requires or functions with the listed
version of the following:
ESX Server version
GSX Server version
VMware Server version
||2.0.1, 2.0.2, 2.1.x, 2.5.1, 2.5.2
||2.0.1, 2.1, 2.1.1, 2.1.2, 2.1.3, 2.5.1, 2.5.2
||2.0.1, 2.1, 2.1.1, 2.1.2, 2.5.0, 2.5.1
||2.0.1, 2.1, 2.1.1
Revision History of This Release Note
||September 28, 2006
||July 6, 2006
||Minor Release. Added VMware Server support.
Installing and Upgrading to Version 1.4.x
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 VirtualCenter 1.4 Users Guide for complete information on performing an installation or upgrade of your VirtualCenter product.
In VirtualCenter 1.4.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:
- Because changes have been made to both the VirtualCenter
server and the VirtualCenter client, you must upgrade all machines
with either component. For example, VirtualCenter 1.3.x or lower version clients
cannot connect to VirtualCenter 1.4.x servers and VirtualCenter 1.4.x clients cannot
connect to VirtualCenter 1.3.x or lower version servers.
- 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.