Virtual Machines Managed by VirtualCenter Renamed When Management Server Restarts or ESX Server Reconnects (1578)
The virtual machines residing on the ESX Server 2.5 host continue to run and remain unmodified if viewed through the ESX Server Management Interface; however, the same virtual machines may be assigned incorrectly in the VirtualCenter inventory and exhibit the following symptoms when viewed through the VirtualCenter client:
- The name of a virtual machine may change.
- The remote console may connect to a different virtual machine.
- The virtual machine groups may appear to be shuffled.
Instances of ESX Server 2.5 being managed by VirtualCenter 1.2 are the only ones that might be affected by this issue. Versions of ESX Server prior to 2.5 and instances of VirtualCenter 1.2 that are not being used to manage an ESX Server 2.5 host do not encounter this issue.
Note: This problem has been fixed in VirtualCenter 1.2 Patch 1 (build 12684).
To download the installer for this build, go to www.vmware.com/download/vc/ and click the VMware VirtualCenter 1.2 download link.
Caution: Be careful not to delete your existing VirtualCenter database. If you are upgrading from a previous VirtualCenter release, you are prompted during the installation:
An existing database already exists. Do you want to overwrite the data?
You should answer No to this question to keep your existing VirtualCenter database.
The release notes are located at www.vmware.com/support/vc12/doc/releasenotes_vc.html.