Knowledge Base

Search the Knowledge Base:
Products:
Search In:
 

Customization Breaks When Workstation, VMI, VCB, Converter, or P2V Are Installed on the Same Machine as VirtualCenter Server 2.x

Details

If I install Workstation, VMI, VMware Consolidated Backup (VCB), Converter, or P2V on the same machine as VirtualCenter Server 2.x, why does a VirtualCenter clone with customization break and cause an unexpected exception?

Solution

The disk-mounting frameworks used by VirtualCenter for guest customization and by these other products for disk copy are incompatible. When both frameworks are installed on the same machine, the version of the other product supercedes the VirtualCenter version and causes failures in VirtualCenter guest customization.

To work around this issue, uninstall Workstation, VMI, VMware Consolidated Backup (VCB), Converter, and P2V before you install VirtualCenter Server. If you install VirtualCenter Server with either of the other two applications, all applications must be removed before you reinstall VirtualCenter Server.
 
This issue will be fixed in a future version of VirtualCenter.

Keywords

2297; esx301; vc201; vielib

Feedback

Rating: 1 - Lowest 2 3 4 5 - Highest (0 Ratings)   

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (2000 or fewer characters)
Submit
Rating: 1 - Lowest 2 3 4 5 - Highest (0 Ratings)   
Actions
  • KB Article: 2297
  • Updated: Dec 31, 2007
  • Products:
    VMware Workstation
    VMware Consolidated Backup
    VMware ESX
    VMware P2V Assistant
    VMware VirtualCenter
    VMware Converter
  • Product Versions:
    VMware Workstation 5.5.x (Windows hosts)
    VMware Consolidated Backup 1.0.x
    VMware P2V Assistant 2.0.x
    VMware P2V Assistant 2.1.x
    VMware ESX 3.0.x
    VMware Workstation 6.0.x (Windows Hosts)
    VMware VirtualCenter 2.0.x
    VMware Converter 3.0.x