| Category | Detail | |----------|--------| | Product Name | VMware vCenter Converter Standalone | | Version | 6.2.0 | | Build Number | 2116140 | | Release Date | July 2019 (patch updates extended through 2020) | | Languages | English, Japanese, Simplified Chinese, French, German, Korean, Spanish |
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:
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.
The release notes for 6.2 highlight specific limitations that users must be aware of:
VMware vCenter Converter Standalone has long been an essential tool for IT administrators, enabling the conversion of physical machines, third-party virtual formats, and other virtual machine (VM) images into VMware virtual appliances. The release of version 6.2, though incremental, brought significant stability, security, and compatibility enhancements. This essay examines the key contents of the VMware vCenter Converter Standalone 6.2 release notes, focusing on its new features, resolved issues, known limitations, and overall impact on system migration workflows.
VMware vCenter Converter Standalone 6.2 is available for download from the VMware Customer Connect portal.
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
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.
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. | Category | Detail | |----------|--------| | Product
VMware vCenter Converter Standalone 6.2 Release Notes VMware vCenter Converter Standalone 6.2 is a major release designed to enhance physical-to-virtual (P2V) and virtual-to-virtual (V2V) migration capabilities for modern IT environments. Released in December 2017, this version specifically targeted compatibility with then-current technologies like vSphere 6.5 Update 1 and Windows Server 2016. Key Features and Enhancements
Interoperability with vSphere 6.5 Update 1: Seamlessly migrate machines to the latest vSphere environments available at the time.
New Guest OS Support: Added official support for Windows Server 2016 and Ubuntu 16.04.
Configurable Temporary Directory for Linux: Admins can now specify a custom path for temporary vmware-sysinfo files in the converter-worker.xml file. This is crucial for environments where the /tmp directory is restricted for privileged users.
Thick-to-Thin Provisioning: A new configuration option allows users to set "thin" as the default disk provisioning type for destination machines by modifying the converter-worker.xml.
Support for IPv6: Continues to provide authorized support for IPv6 environments with certain constraints. Release 6.2.0.1 (Maintenance Update)
Released on May 22, 2018, version 6.2.0.1 (Build 8466193) was a critical maintenance update that replaced the original 6.2 build. Additional Support in 6.2.0.1
vSphere 6.7 Update 1 Interoperability: Extended support to include newer vSphere 6.7 hosts. Unlike the plugin version integrated with vCenter Server,
Offline Hyper-V Conversion: Added the ability to convert offline Hyper-V virtual machines, including Windows 10 (64-bit) and Windows Server 2016 (64-bit). Resolved Issues in 6.2.0.1
SMB Share Failures: Fixed an issue where converting a powered-on Windows machine to an SMB share would fail.
Workstation 14 Interoperability: Resolved bugs preventing virtualization from within VMware Workstation 14.
Job Submission Errors: Corrected a specific "info.owner" parameter error that caused job submissions to fail. Known Issues and Workarounds VMware vCenter Converter Standalone - VA.gov
VMware has officially deprecated Converter Standalone as a standalone product. Version 6.2 was one of the last feature releases. No 6.2 patches exist for vSphere 7.0 or 8.0. For modern environments, VMware recommends:
However, Converter 6.2 remains downloadable from VMware’s legacy archive (MyVMware – Partner Connect) and is still used in air-gapped and legacy environments.
Despite its improvements, VMware vCenter Converter Standalone 6.2 retains several limitations that administrators must understand before planning migrations.
From an operational standpoint, the 6.2 release allowed system administrators to confidently migrate legacy physical servers running Windows Server 2016 into a modern vSphere 6.5 environment without third-party tools. The enhanced UEFI support meant that newer hardware could be virtualized with identical boot configurations, reducing post-conversion troubleshooting. Moreover, the security patch and stability fixes decreased the risk of conversion failures during critical migration windows, directly improving data center agility.