Vmware Vcenter Converter Standalone 6.2 Release Notes Now
VMware vCenter Converter Standalone 6.2 facilitates data center modernization by expanding support for modern operating systems, including Windows 10, Server 2016, and updated Ubuntu LTS versions. The release enhances P2V migration reliability through improved handling of GPT and UEFI configurations, streamlining the transition of legacy physical infrastructure into virtualized environments. Read the full release notes on the VMware documentation site.
VMware vCenter Converter Standalone 6.2 was officially released on December 14, 2017. It is primarily a free tool used to automate the conversion of physical machines (P2V) and other virtual machine formats (V2V) into VMware virtual machines. Key New Features in Version 6.2
The following features were introduced to expand compatibility and control:
vSphere Support: Added interoperability with vSphere 6.5 Update 1. vmware vcenter converter standalone 6.2 release notes
Expanded Guest OS Support: Added support for Windows Server 2016 and Ubuntu 16.04.
Destination Disk Provisioning: Introduced the ability to change the default destination provisioning disk type from thick to thin. This requires modifying the converter-worker.xml file and setting the useNonAllocatingThinDiskType tag to true.
Linux Migration Improvements: Added a new configuration option in converter-worker.xml to specify a custom path for temporary vmware-sysinfo files. This is useful for Linux systems where the /tmp directory is restricted from running code. Build and Version History VMware vCenter Converter Standalone 6
A minor follow-up update, Version 6.2.0.1 (Build 8466193), was released on May 22, 2018.
Resolved Issues: Fixed failures when converting powered-on Windows machines to SMB shares.
Hyper-V Support: Confirmed support for converting offline virtual machines from Hyper-V running Windows Server 2016 and Windows 10. What Is VMware vCenter Converter Standalone 6
Interoperability: Noted that interoperability with VMware Workstation 14.x was initially problematic. Current Status and Availability
As of April 2026, Version 6.2 is considered a legacy release.
What Is VMware vCenter Converter Standalone 6.2?
Before diving into the release notes, it is essential to understand the product’s scope. Converter Standalone 6.2 is an agent-based migration tool that allows administrators to:
- Convert a running physical machine (Windows or Linux) into a virtual machine (VM).
- Convert third-party virtual machines (Microsoft Hyper-V, Citrix XenServer, KVM) to VMware VMDK format.
- Reconfigure and re-host existing VMware VMs across vCenter servers or ESXi hosts.
- Perform "hot cloning" (without reboot) for Windows sources and "cold cloning" (boot from ISO) for Linux sources.
Unlike the plugin version integrated with vCenter Server, the standalone client operates independently, making it ideal for disconnected environments, remote sites, or migrations where vCenter itself may not yet exist.
3.1 Source Operating Systems (Physical Machines)
- Windows: Windows XP SP3 (32-bit only), Windows 7 SP1, Windows 8, 8.1, Windows 10 (1511+), Windows Server 2008 R2 SP1, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016 TP5.
- Linux: RHEL 5/6/7, CentOS 5/6/7, Ubuntu 12.04, 14.04, 16.04 LTS, SUSE Linux Enterprise Server 11 SP3/SP4.
Background and Context
Prior to version 6.2, Converter Standalone 6.1.x offered basic P2V (physical-to-virtual) and V2V (virtual-to-virtual) capabilities but faced challenges with modern operating systems, secure boot configurations, and large-scale conversions. Version 6.2 was released to bridge compatibility gaps with vSphere 6.5 and Windows Server 2016, while also addressing several long-standing bugs. The release notes thus serve not only as a technical changelog but as a guide for safe migration planning.
Troubleshooting pointers
- Collect Converter logs from the Converter server and client agents when conversions fail.
- Check for problematic drivers, dynamic disks, or unusual storage layouts first.
- For network-related failures, repeat conversions over a reliable network or perform an offline conversion using local storage staging.
- If you encounter a known issue not fixed in 6.2, consult VMware KB articles for workarounds and patches.