Los costos de envío se calcularán en base a esta dirección en todo el sitio.
Selecciona tu país
As with previous versions, this tool is available without a separate license. 2. Key Features and Improvements in Version 6.2
This release patches multiple CVEs (Common Vulnerabilities and Exposures). Users on version 6.1 or 6.0 are strongly advised to upgrade to 6.2 due to these fixes.
The converted virtual machines can be deployed directly to the following VMware platforms: VMware vSphere 6.5 (ESXi 6.5 and vCenter Server 6.5) VMware vSphere 6.0 VMware vSphere 5.5 VMware Workstation 12.x and 14.x VMware Fusion 8.x and 10.x System Requirements and Installation vmware vcenter converter standalone 6.2 release notes
: A new configuration option in the converter-worker.xml file allows you to specify a custom path for temporary vmware-sysinfo files. This is particularly useful for environments where the /tmp directory has restricted execution policies.
The following features were introduced to expand compatibility and control: As with previous versions, this tool is available
: Confirmed support for converting offline virtual machines from Hyper-V running Windows Server 2016 and Windows 10.
Version 6.2 supports V2V migrations, allowing users to convert offline virtual machines directly from Microsoft Hyper-V servers. Supported systems for offline ingestion include Windows 10 and Windows Server 2008 R2 through 2016 (64-bit). Users on version 6
The resolved issues section of the release notes is particularly valuable. One critical fix addressed a problem where conversion jobs would hang indefinitely when processing disks with certain partition table errors. Another resolved issue involved network authentication failures when the source machine was part of a workgroup rather than a domain. The release notes also noted the correction of a memory leak in the worker service, which previously caused converter stability problems during prolonged or batch conversions.
Added support for Ubuntu 16.04 LTS configurations.
Full compatibility with Windows Server 2016 and updated builds of Windows 10.
The tool is not supported by Broadcom, contains known critical security vulnerabilities, suffers from a major service start bug, and is incompatible with modern vSphere and ESXi platforms (versions 7.x and 8.x). Its inability to work with newer hardware virtual machine versions (above 11) makes it unsuitable for most current infrastructure.
