VMware

VMware vCenter Converter Release Notes


VMware vCenter Converter for vCenter Server 4.0 | 21 May 2009 | Build 161418

Last Document Update: 21 May 2009

Check periodically for additions and updates to these release notes.

These release notes cover the following topics:

These release notes provide information about the VMware vCenter Converter module for VMware vCenter Server 4.0. For information about new vCenter Server features, requirements, and installation, see the VMware vSphere 4.0 Release Notes.

Introduction to VMware vCenter Converter

VMware vCenter Converter is an add-on plug-in for vCenter Server 4.0, and provides an integrated solution for migrating both physical and virtual machines to VMware vSphere. You can use vCenter Converter to create, edit, and monitor physical-to-virtual and virtual-to-virtual migration tasks through the vCenter Server user interface. In addition, you can use vCenter Converter to directly import supported third-party images to virtual machines that vCenter Server manages.

For physical-to-virtual migrations, you can use vCenter Converter to perform live migrations by using hot cloning, which causes no disruption or downtime on the source physical machines. The hot cloning process installs an agent on the physical source being converted to leverage volume shadow copy service (VSS) snapshots prior to conversion. To avoid installing an agent in the physical operating environment, you can use the traditional cold cloning approach for physical-to-virtual conversions. This involves shutting down the physical machine and using the vCenter Converter Boot CD to perform an offline conversion.

vCenter Converter also provides the ability to export virtual machines managed by vCenter Server to hosted VMware platforms such as VMware Workstation, VMware Server, VMware ACE, and VMware Fusion.

What's New

VMware vCenter Converter is a new release for vCenter Server 4.0 and includes the following enhancements:

  • Support for importing physical, virtual, and third-party sources to supported platforms on ESX/ESXi 4.0 hosts that vCenter Server manages
  • Support for Windows Server 2008, both as a conversion source and an installable platform
  • Support for conversion of Microsoft Hyper-V virtual machines to VMware virtual machines by treating Hyper-V machines as physical source machines
This release contains known issues described in Known Issues.

Prior Releases of vCenter Converter

Features from earlier releases of vCenter Converter are described in the release notes for each release. To view release notes for earlier releases of vCenter Converter, click one of the following links:

Installation Notes

Installation of VMware vCenter Converter 4.1.0 requires a connection to vCenter Server 4.0. Each installation of vCenter Converter must be associated with only one vCenter Server instance.

VMware vCenter Converter consists of the following components:

  • A server component, which you can install on the same system as vCenter Server or on a different system. The server component of vCenter Converter can coexist with installations of vCenter Converter Standalone 4.x and 3.x.
  • A client component that is a plug-in interface to a VMware vSphere Client 4.0 instance.
The following installation conditions and restrictions exist:
  • You can install the vCenter Converter client plug-in for vCenter Server 4.0 on vSphere Client 4.0 only. If both vSphere Client 4.0 and VI Client 2.5 are installed on the same machine, different versions of the vCenter Converter client plug-in can coexist on that machine.
  • If you have an existing system with Converter Enterprise for Virtual Infrastructure 2.5, and you install vCenter Converter for vCenter Server 4.0 on that system, the vCenter Converter server is upgraded.
  • Each vCenter Converter client plug-in is compatible only with the same version of vCenter Converter server.
  • If the vSphere client does not find a vCenter Converter client plug-in compatible with vCenter Converter server, a download and install option appears in the Available Plug-ins list of the Plug-in Manager so that you can install the client.
  • During installation, you cannot use non-ASCII characters for the name and password of the computer on which you install vCenter Converter or for installation path names. The installer does not support the use of non-ASCII characters in these cases.

Upgrade Notes

When you upgrade to vCenter Converter for vCenter Server 4.0, any previously scheduled tasks from earlier releases, such as Converter Enterprise for VirtualCenter 2.5 (including Update 1, Update 2, Update 3, Update 4, and so on) are removed. You must document the settings for any scheduled tasks you want to keep so that you can re-create them after the upgrade.

Supported Platforms

For information about supported platforms for this release, see the vCenter Converter Administration Guide.

Interoperability and Supported Guest Operating Systems

For information about interoperability and supported guest operating systems for this release, see the vCenter Converter Administration Guide.

VMware vCenter Converter can clone source images containing certain operating systems, but the destination virtual machine may or may not work without additional configuration after import. Support for the following guest operating systems is experimental. In particular, if the source image contains unsupported hardware, you might need to modify the configuration of the destination virtual machine before using it:

  • Linux
  • Windows NT 3.x (cold cloning only)
  • Windows ME
  • Windows 98
  • Windows 95
  • MS-DOS

Top of Page

Known Issues

This VMware vCenter Converter release contains the following known issues:

vCenter Converter drops NICs on ESX/ESXi 4.0 hosts that have distributed switches without a virtual machine port group
When you import or export a machine to an ESX/ESXi 4.0 destination, if you specify a vNetwork Distributed Switch (on the wizard Network Information page) that does not have a virtual machine port group, the NIC configured for the distributed switch is dropped on the target virtual machine during conversion.
Workaround: To avoid this problem, select a non-vNetwork Distributed Switch network. After the conversion completes, add the NIC and configure it to use a vNetwork Distributed Switch network in the target virtual machine.

vCenter Converter service terminates abnormally when exporting or importing an ESX/ESXi 4.0 managed virtual machine configured with a vNetwork Distributed Switch
When you use the converter-tool Command-Line Interface (CLI) to import or export a managed virtual machine running on an ESX/ESXi 4.0 host whose network settings are configured with a vNetwork Distributed Switch, the vCenter Converter service terminates abnormally and the job fails. This problem happens when the input XML file to converter-tool sets the <nicMappings> keepNics attribute to true.
The following workarounds are available:

  • Use the vCenter Converter plug-in module for the vSphere Client to import or export the source machine instead of using the converter-tool CLI.
  • If you use converter-tool, set the following attribute: <nicMappings> keepNics="false" </nicMappings>.

Import and export tasks fail when a vNetwork Distributed Switch is selected as the network for the target virtual machine
When you create an import or export task and select a vNetwork Distributed Switch from the network selection for the target virtual machine, the task begins but fails immediately with the following error message: Unknown error returned by vCenter Converter agent. This problem is seen when you use the Import or Export wizards or the converter-tool Command-Line Interface (CLI) to create the task.
Workaround: Select a network for the target virtual machine that is not a vNetwork Distributed Switch.

Volume-based clone of source with IDE disk to ESX/ESXi 4.0 destination fails with disk error when powered on
When a source machine containing IDE disks is converted to an ESX/ESXi 4.0 virtual machine using volume-based cloning, the cloning succeeds, but the target virtual machine fails to boot up and issues a disk error when powered on. This can happen when importing an ESX/ESXi 4.0 virtual machine, a Workstation virtual machine, or when you perform a physical to virtual clone of a source machine containing IDE disks.
Workaround:

  • Use disk-based cloning to clone the source with IDE disks to the ESX/ESXi 4.0 destination.
  • When attempting a physical to virtual conversion, power off the virtual machine and use the vCenter Converter Boot CD to perform disk-based cold cloning.

Distributed Power Management can power off ESX/ESXi hosts that vCenter Converter uses
When you use a VMware DRS cluster as a vCenter Converter source or destination, VMware DRS Power Management (DPM) might power off the hosts, which breaks active connections and causes operations to fail.
Workaround: Set VMware DRS Power Management (DPM) to Manual. At the end of the conversion process, restore DPM to its original setting.

vCenter Converter service does not remove temporary files in the C:\Windows\Temp\vmware-converter folder
When the vCenter Converter service terminates abnormally, it does not completely remove files created in the Temp folder. These files accumulate and consume considerable disk space.
Workaround: To recover the disk space, you must manually remove the files.

  • Delete any files from the C:\Windows\Temp\vmware-converter folder with the following name types: vmw*.tmp and vmware-_VMware_Converter_-*.
  • Delete any files from the TEMP directory with a ufa*.tmp name type.
    1. Open the Registry Editor and select Start > Run, type regedit and click OK.
    2. In the left panel, select HKEY_LOCAL_MACHINE > ufa*.tmp, then select File > Unload Hive.
    3. Remove the ufa*.tmp and ufa*.tmp.LOG files from the system's TEMP directory.

Exporting a virtual machine to a hosted destination fails with a vCenter Converter agent system error
When you export a virtual machine to a hosted destination, if the source virtual machine's Annotations field contains carriage returns (Enter), the job fails at two percent with a vCenter Converter Agent system error.
Workaround: Edit the virtual machine properties and ensure that the Annotations field does not contain any carriage returns. If returns are present, remove them from the annotations by editing the virtual machine in the Summary view of the vSphere Client or by editing the .vmx file on the ESX/ESXi host.

Cloning a Windows Vista virtual machine to an ESX destination with the VMware Tools option selected might result in a blue screen
When you select the Install VMware Tools option on the Customization page during a Windows Vista virtual machine clone to an ESX/ESXi 4.0 host and VMware Tools is not installed on the Vista virtual machine, the VMware Tools installation might fail. The target virtual machine boots, but when the machine reboots during the VMware Tools installation, a blue screen might appear.
This issue is caused by a conflict between the Windows Vista driver installation and the VMware Tools driver installation when the devices are configured on first boot up.
The same behavior is observed when cloning a Windows Vista VPC image to an ESXi 3 destination.
Workaround:

  1. Repeat the cloning process to the ESX/ESXi host destination and on the Customization page, deselect Install VMware Tools.
  2. When cloning is complete, power on the virtual machine and install VMware Tools using the vSphere Client interface.

Reinstallation of vCenter Converter fails on Windows Server 2008 64-bit machine
If vCenter Converter is reinstalled on a Windows Server 2008 64-bit machine that also runs vCenter Server, the installation fails with the following error message: Could not start service Vstor2 Converter Virtual Storage Driver.
The following workarounds are available:

  • Reboot the machine and run the installer again to reinstall vCenter Converter.
  • Install vCenter Converter on a different machine than the one running vCenter Server.

Login failure error message received when specifying valid credentials for a remote Windows physical machine
While selecting a remote Windows physical machine for hot clone, you might receive a Login failure, unknown user name or bad password error message. This error might be caused by incompatibilities in the network authentication protocols between the Windows operating system on the remote system and the system on which vCenter Converter server is running. This situation usually occurs in cases where a newer version of Windows is communicating with an older version, such as when vCenter Converter server is running on Windows 2008 and trying to clone a Windows XP source.
For additional information, refer to the Microsoft KB article 823659 for LAN Manager authentication levels.

Customization is not applied when the active system partition is on the D: drive instead of the C: drive
After customizing a virtual machine on any host machine, customization fails if the C: drive is not the primary partition in your configuration. This happens because the Microsoft Sysprep utility does not preserve the original drive letter assignment during setup.
Workaround: Ensure that the C: drive is the primary partition for the virtual machine being customized.

Import wizard stops responding when importing a Windows NT SP6 image
When vCenter Converter server is installed on a Windows Vista or Windows Server 2008 machine and you try to import a Windows NT SP6 image, the Import wizard stops responding and the CPU utilization goes up to 100 percent. This happens because of a deadlock in the NTFS driver of the host operating system while accessing the volumes on the Windows NT source.
Workaround: Install the vCenter Converter server on an operating system other than Windows Vista or Windows Server 2008 and then import the Windows NT image.

Image customization prompts a dialog box for Sysprep file information
When you customize a virtual machine (during import, export, or reconfiguration of an existing machine), while vCenter Converter is setting the customization parameters, the machine automatically reboots and a Sysprep dialog box might prompt you for additional files.
Workaround: Note the list of missing files that the Windows Mini-Setup wizard cannot find. Copy the required files (for example, Thawbrkr.dll) on the source machine to the Sysprep install files folder, C:\sysprep\i386, then perform the conversion (import, export, or reconfiguration) and customization steps. The files that Sysprep prompts for are usually in the following location on the source machine: C:\Windows\system32
Note that the Sysprep directory is removed after the virtual machine is started and the customization is completed.

Conversion of a source machine to vCenter Server or ESX/ESXi destination fails with NFC errors
The cloning process to a vCenter Server or ESX/ESXi destination can fail with NFC errors when you select source volumes that reside on different source disks for conversion. This issue can be caused by certain network environments that are used by vCenter Converter server and vCenter Server or ESX/ESXi for communication. For details, see Investigating network devices and device settings as a cause of VMware Converter failures (KB article 1004615).

Microsoft Visual C++ Runtime Library error message is displayed during import or export of a machine
If a user environment has versions of VI Client 2.5 Update 1, Update 2, Update 3, or Update 4 that coexist with vSphere Client 4.0, and you install the vCenter Converter 4.1.0 client plug-in, when you start the vCenter Converter Import or Export wizard, the vSphere Client session is terminated abruptly. An OpenSSL DLL conflict between the VI Client versions and the vCenter Converter 4.1.0 client plug-in causes this problem.
Workaround: Go to the Launcher folder in the VI Client install directory, for example, C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\Launcher, and delete the following DLL files from that location:

  • libeay32.dll
  • ssleay32.dll
For this workaround to function correctly, you also need to ensure that no additional copies of OpenSSL DLL files with different versions exist in the system path.

When you import a virtual machine to a cluster destination, the Import wizard displays datastores that are available to the cluster, but not to the selected host
vCenter Converter enumerates all datastores for the selected cluster. It does not filter datastores based on the host. Therefore, during import of a virtual machine, when vCenter Converter tries to connect to a datastore in the cluster that does not have SAN connectivity, it issues an error message stating that you do not have access to the datastore.
The following workarounds are available:

  • Select a datastore that has SAN connectivity for the selected host and continue the import process.
  • To import a virtual machine to the host datastore that is not on SAN, select a host destination rather than a cluster destination.

vCenter Converter installer issues inappropriate error message if user does not have administrator login credentials
If you are logged in to a Windows system as a user with no administrator privileges and try to install vCenter Converter server, the following error message is displayed: Unable to save file:C:\WINDOWS\Installer\{11D05092-A113-4FC5-g/vCenter Converter.msi The system cannot find the path specified.

Workaround: To install and set up vCenter Converter server on Windows systems, log into the system as an administrator.

Installing two or more vCenter Converter plug-ins on the same machine causes unpredicted behavior
If two or more instances of the vCenter Converter client plug-in appear in the Virtual Infrastructure Client 2.5 GA or Update 1 Plug-in Manager when you connect to a VirtualCenter 2.5 server, you must enable only the vCenter Converter client plug-in for VirtualCenter 2.5. Multiple plug-ins can appear if you install VI Client 2.5 (either GA or Update 1) and vSphere Client 4.0 on the same machine and install the vCenter Converter client plug-in for both versions.
Workaround: Enable the vCenter Converter client plug-in for VirtualCenter 2.5 only. This issue is fixed in VI Client Update 2 and later releases. Only one vCenter Converter plug-in client appears in the Plug-in Manager.

Cloning of Windows operating system fails if the size of the FAT32 volume is set to greater than 32GB
On some Windows operating systems, if you resize a file allocation table (FAT32) volume to larger than 32GB during hot or cold cloning, the conversion fails when the new volume is formatted. This is a known limitation of the FAT32 file system.
The following workarounds are available:

  • Limit the FAT32 volume to a maximum of 32GB.
  • Perform a disk-based cold clone.
  • Deselect the FAT32 volume if the minimum size is larger than 32GBs.
For additional information, search the Microsoft Help and Support Web site.

Timeout on SSL handshake when converting over a WAN link
vCenter Converter does not support conversion over a WAN. When trying to perform a conversion over a WAN link, you might experience an SSL timeout because the timeout for SSL handshakes is two minutes.
Workaround: To avoid the timeout, perform a conversion to a hosted target machine (for example, a Workstation virtual machine), that is in the same LAN as the host, then copy the temporary virtual machine and transfer it over the WAN to the remote site. If the intended target is a Workstation virtual machine, this completes the process. If the intended target is ESX/ESXi, import the Workstation virtual machine to the ESX/ESXi host.

When you convert a Windows Vista source machine to a virtual machine manually and customize the settings, user accounts for the converted machine do not behave as expected
A user account with administrative privileges is disabled because the customization process disables the administrator account, even though the account was initially enabled. If no other user account is enabled, the newly created virtual machine is not usable because you can't log in to it.
Workaround: Create another user with administrative privileges on the source machine before the conversion and customization.

Default administrator password is not preserved for Windows Server 2008 after customization
During customization, the Windows Sysprep utility deletes and re-creates the administrator account on Windows Server 2008. You must reset the administrator password when the virtual machine starts up the first time after customization.

Task parameter error message issued when scheduling a task
You might receive an Invalid task parameter error message when you click Finish after scheduling a task. This might happen if the task name you entered is too long.
Workaround: Provide a shorter task name.

Converting Windows Server 2008 images with more than one disk results in all disks being offline except the disk on which the operating system exists
If you are converting a Windows Server 2008 Enterprise Edition or Datacenter Edition virtual machine with multiple disks, some of the disks might remain offline. This is because Windows Server 2008 has a new SAN policy that determines whether a newly discovered disk is brought online or remains offline.
For additional information about the new SAN policy, search the Microsoft Web site.
Workaround: Use the Windows Disk Management snap-in tool to bring the disks online.

vCenter Converter cannot communicate with vCenter Server in the Internet Protocol version 6 (IPv6) environment
vCenter Converter server does not support IPv6 communication. You cannot connect to or register with vCenter Server by using an IPv6 address.
Workaround: To communicate with vCenter Server, you must enter an IPv4 address or a host name that resolves to an IPv4 address.

vCenter Converter does not support VMware vApp objects as destinations for virtual machines
When a vApp object is created on an ESX/ESXi 4.0 host that vCenter Server manages, vCenter Converter treats the host as a resource pool. When vCenter Converter clones a new target virtual machine, if the vApp object is selected as the destination for the virtual machine instead of a resource pool, creation of the virtual machine fail on the target. This is the expected behavior.
Workaround: To successfully clone a vApp object, import the host machine to a folder and move the folder to the vApp instead of trying to import the machine directly to the vApp pool.

Thin-provisioned disks are not converted as thin-provisioned target disks on ESX/ESXi 4.0 hosts
ESX/ESXi 4.0 supports virtual machines with thin-provisioned disks (where the actual space usage on the datastore for the disk grows as it is needed). This feature is currently not supported by vCenter Converter and results in thin-provisioned disks in source virtual machines being created at the target as fully-allocated flat disks.

No warning message appears when you remove a vCenter Converter server
If you use the installer or the Windows Add and Remove program utility to uninstall a vCenter Converter server that is installed on a guest operating system, the server is deleted without issuing a File in use message (or any other information message) prior to the deletion. This is true even if the vCenter Converter service is still running. A workaround is not available for this issue.

Cloning a virtual machine running Microsoft Windows fails if you modify the MULTI syntax in the boot.ini file
If you modify the MULTI syntax, in the boot.ini file, hot or cold cloning a machine running Microsoft Windows fails. Converter does not support systems with a boot.ini file that has lines different from the following form: [multi(xxx)disk(xxx)rdisk(xxx)partition(xxx)\%systemroot%].
Workaround: Use the standard syntax.

On a Windows Vista virtual machine that has more than one virtual NIC, some virtual NICs don't capture the static IP address set during customization
If you try to configure static IP settings for more than one virtual NIC on a Windows Vista guest operating system, the settings might not be applied correctly to all virtual NICs. The workaround is to manually configure the static IP settings.

vCenter Converter issues an error message when customizing an imported virtual machine
When you customize an imported virtual machine and the import task reaches 100 percent, an UNKNOWN_METHOD_FAULT.summary error message appears.
Workaround: If you experience this problem with a vCenter Converter server running Microsoft Windows 2000, upgrade the operating system to SP3 or higher. If you experience this problem with Microsoft Windows XP, upgrade to SP1 or higher.

When importing a virtual machine, the task is not completed if the machine name exceeds the character limit
When you import a virtual machine and give the destination virtual machine a name that exceeds 60 characters, the task is not completed. The destination virtual machine name field allows for up to 80 characters, but a timestamp is appended to the name you select. If the combination of characters in the name and timestamp exceeds this limit, the problem occurs.
Workaround: Use 60 characters or less for the destination machine name.

Microsoft Windows NT does not preserve the drive letters in a cloned virtual machine
If you clone a Windows NT4 machine and select the Create a separate disk for each volume option, the volume drive letters in the target virtual machine are modified, with the exception of active and system volumes.
Workaround: Manually reset the volume drive letters by launching the Disk Administrator in the target virtual machine. In the Disk Administrator, right-click the volume and select Assign Drive Letter.

Restarting vCenter Server when vCenter Converter is importing a virtual machine causes out-of-sync inventory
If you restart vCenter Server during an import, the Recent Tasks pane does not show the running vCenter Converter tasks. When the vCenter Server is stopped while the import task is running, the target virtual machine is unusable. You must remove the target virtual machine and reimport it.

vCenter Converter allows import of powered-on hosted sources
vCenter Converter allows import of powered on or suspended hosted sources, but this action is not supported.
Workaround: Shut down and power-off the virtual machine before importing it.

Manual uninstall of vCenter Converter agent from remote source physical machine might be required
In some cases, you might need to manually remove the vCenter Converter agent. You can uninstall the agent by using Add/Remove Programs on the source physical machine.

Source machine with mixed IDE and SCSI disks might not produce a bootable virtual machine
On a source machine with both SCSI and IDE disks, the IDE disks are placed at the end of the disk list in BIOS. If the source machine boots from an IDE disk, the target virtual machine created by vCenter Converter boots from the wrong disk because a VMware virtual machine looks for the first disk in the disk list.
Workaround:

  1. Boot the imported virtual machine and press F2 to enter the BIOS.
  2. Go to the Boot menu.
  3. Highlight the Hard Drive row and press Enter.
  4. Change the boot order of the disks so that the system disk is first.
  5. Reboot the virtual machine.

Sysprep deletes drive letter mappings if your task includes customization
If you choose customization options and the destination virtual machine stops responding at a Please Wait screen after the second sysprep reboot, you must rerun the import without customization. This issue occurs because the Microsoft Sysprep utility deletes the drive letter mappings, which prevents access to necessary files.

Customization is not applied if virtual machine is manually restarted after reconfiguration
The process for customization occurs in the following order:

  1. The user customizes the virtual machine image with vCenter Converter and waits for 100% Complete.
  2. The user powers on the virtual machine.
  3. The user waits for the machine to reboot automatically.
  4. Sysprep processes the customizations.
  5. Sysprep reboots the virtual machine.
  6. The Windows operating system loads, and the network configurations occur.
If you manually reboot the virtual machine after step 2 without waiting for the virtual machine to automatically reboot, the customization process does not work.
Workaround: Turn off Autologon in the source machine. Wait for the machine to automatically reboot during the first boot up. After the first boot, the machine reboots twice before you can safely log in.

vCenter Converter does not distinguish between physical serial ports and virtual serial ports on the source machine
Virtual serial ports are treated as physical serial ports during the migration. For example, if a source machine has two physical serial ports and two virtual serial ports, the import process creates four serial ports on the destination machine.

Importing a Windows 2000 virtual machine fails when an OEM-type partition is selected
When selecting individual volumes for a clone, with or without resizing the volumes, do not select any OEM or diagnostic partitions on the disk. The only volumes needed are the active, system, and any data partitions.

Cloning a large disk with lots of free space to an ESX/ESXi destination fails
Selecting Import all disks and maintain size on the vCenter Converter Import wizard Source Data page when converting a large disk with a lot of free space to an ESX/ESXi destination might cause the import to fail. Check the log files, and if error messages with NFC failures appear, use the import volumes method with or without resizing.

Reimporting a failed or canceled vCenter Converter import task might fail with source in use error message
If you try to rerun a failed or canceled import task immediately after cancellation or failure, vCenter Converter might fail and report that the source machine is in use. When an import task fails or is canceled, vSphere Client 4.0 immediately indicates this, but it takes a few minutes for vCenter Converter to remove the target virtual machine. Before trying to reimport the source machine, wait for the target virtual machine to be removed. This is indicated by the successful completion of the Destroy Virtual Machine task (generated by vCenter Converter server) in the task pane of the vSphere Client.

vCenter Converter operations to vCenter Server fail when the source machine disk size is greater than 1023GB
When vCenter Converter tries to import a source machine containing a disk size greater than 1023GB, virtual machine creation fails. This is a Virtual Machine File System (VMFS) limitation. By default, when you create a datastore, the VMFS block size limit is 1MB which supports a 256GB disk size. To increase the file size, create a VMFS3 datastore with a larger block size. vCenter Converter supports a disk size up to 1023GB when the VMFS block size is 4MB.

The block size limits for VMFS versions are:

  • VMFS2: 1, 2, 4, 8, 16, 32, or 64MB
  • VMFS3: 1, 2, 4, or 8MB

vCenter Converter server remote agent deployment fails on Windows Vista Enterprise 64-bit systems
vCenter Converter agent can remotely hot clone the remote source to a destination managed by VirtualCenter Server 2.5. However, in the case of Windows Vista Enterprise 64-bit, the remote agent is deployed but fails to run. These systems cannot be remotely hot cloned.
Workaround: Power off the remote source. Use the VMware vCenter Converter Boot CD to import the system by cold cloning.
You can also turn off Windows Vista User Account Control (UAC) before beginning the remote hot clone. For more information, search on the Microsoft Web site for the "Windows User Account Control Step-by-Step Guide."

VMware vCenter Converter cannot read short host names
If you log in to vSphere Client 4 by using a short machine name for vCenter Server that is resolvable by the client machine but not by the vCenter Converter agent, the agent fails to connect to vCenter Server. When the vCenter Converter server tries to contact the vCenter Server during the remote hot clone setup, the following error message appears: Unable to find the server. Verify that the server name is correct and then try again.
Workaround: Log in by using a fully qualified host name or IP address in vSphere 4 Client. Alternatively, you can ensure that the short host name of the vCenter Server is resolvable from the remote source.

Importing an Acronis image of a system with dynamic disks fails
In some circumstances, importing an Acronis image of a system with dynamic disk fails with the following error message: Guest OS not found. vCenter Converter does not support importing system images with dynamic disks.

The creation of separate disks for each volume is not recommended for multi-boot systems
The Create a separate disk for each volume option on the Source Data page of the Conversion wizard does not support multi-boot systems. If you clone a physical or virtual machine that has a multi-boot configuration, every system volume except for the recognized system volume is placed on a new disk. This prevents the target virtual machine from booting into any of the additional system volumes.
Workaround: Deselect additional system volumes so they are not cloned in the target virtual machine.

Importing a Windows Vista source with a USB device on some versions of ESX/ESXi causes a critical system error
If a Windows Vista source with a USB port is imported to an ESX/ESXi 3.0, 3.0.1, or 3.0.2 destination, the virtual machine displays a blue screen on first startup because the destination machine does not support USB devices.
Workaround: Remove usb.present = "TRUE" from the converted .vmx file and power on the target virtual machine.

Import of Microsoft Virtual PC image fails with a Could not parse the VMC configuration file error message
The Microsoft Windows system on which vCenter Converter is installed must have Microsoft XML Parser (MSXML) 2.6, 3.0, or 4.0 installed to successfully import Virtual PC images.

The CD-ROM device does not work after importing Windows Vista to virtual machines
The CD-ROM device does not work after importing Windows Vista to ESX 3.x/ESXi 3.x or to a Workstation version earlier than VMware Workstation 6. The CD-ROM driver that comes with Windows Vista does not work with the emulated CD-ROM devices in ESX /ESXi 3.x and Workstation versions earlier than 6. Workstation 4.x and ESX 2.x do not support Vista. Support for Windows Vista as a guest operating system is experimental for ESX 3.0.x and Workstation 5.x. Vista is fully supported as a guest operating system on Workstation 6. For a list of VMware products that have experimental support for Windows Vista, see the Guest Operating System Installation Guide.

Remote hot clone of Windows NT4 from a Windows Vista host is not supported
If you install vCenter Converter server on a Windows Vista host and try to hot clone Windows NT4 remotely, the vCenter Converter agent deployment succeeds, but the vCenter Converter Service on the remote machine fails to start. This conversion scenario is not supported.

Top of Page

Internationalization

Locale forcing does not work with vCenter Converter plug-in wizards
When you use the VpxClient.exe -locale -en-US command to change the vSphere Client locale, this change does not affect the vCenter Converter plug-in wizards. The Import and Export wizards continue to display in the localized language. vCenter Converter does not support locale forcing.

ESX/ESXi destination host name is truncated in Import wizard name field
vCenter Converter does not support locale forcing. If you use locale forcing to run the English version of the vCenter Converter Import wizard on a Simplified Chinese operating system, when you enter a name for the destination host in the ESX/vCenter Server name field, the name is truncated to 33 characters.
Workaround: Use the IP address rather than the host name.

Misleading warning message appears when non-ASCII characters are entered in the Computer Name field
If you enter non-ASCII characters in the Computer Name field on the Import or Export wizard Customization page, a warning message appears invalidating the input characters. However, the warning text is misleading. It does not state that non-ASCII characters are not allowed in the computer name field.
Workaround: In addition to the non-permissible characters displayed in the warning message, do not enter non-ASCII characters for the Computer Name.

Use of non-ASCII characters in the virtual machine name or folder path fields during export causes task failure
During export of a virtual machine, if you use non-ASCII characters in the folder path or for the target virtual machine name in the Export wizard, the task is not successful. This is a Unicode limitation and applies to all languages.
Workaround: Avoid using non-ASCII characters for the folder path and virtual machine name.

Virtual Machines with non-ASCII characters in their folder name and configuration file name cannot be powered on with Fusion
If you export a virtual machine that contains non-ASCII characters in either its folder name or configuration .vmx file name, you cannot power it on with VMware Fusion.

Remote agent installation is unsuccessful when specifying a computer or DNS name with non-ASCII characters in the Import wizard
If you use non-ASCII characters to populate the computer or DNS name field in the Import wizard when installing the vCenter Converter remote agent, the installation fails. Clicking on the Log Info button displays an erroneous log location message.
Workaround: Use the IP address instead.

Customization might fail if a non-ASCII word starting with an English character is used in some fields of the customization wizard
In the vCenter Converter customization wizard, non-ASCII characters are not permitted for the Computer Name, Domain Name, and Workgroup fields. The wizard disables entering non-ASCII characters for these fields. However, if a non-ASCII word that begins with an English character is entered, the user interface accepts the word instead of blocking it, but the customization might not happen as expected. A workaround is not available for this issue.

Configuration and display limitations:

  • Datastore names, virtual network names, and image files names (CD, DVD, and floppy drive) must contain only ASCII characters.

  • In conformance with general Internet practice and protocols, the following must contain ASCII characters only: host names, workgroup names, domain names, URLs, email addresses, SMTP server names, and SNMP community strings.

  • When using the vCenter Converter Import wizard, the date and time format might be inconsistent with the current location.

Top of Page