In this way, I can save time and space on destination datastore during conversion process. I have de-selected system partition because I just want to convert D: drive. We can see details about source virtual machine once agent installation has finished. I turned off windows firewall then started “vMware vCenter Converter Standalone Edition 6.2” to connect successfully. Windows firewall is turned on target virtual machines. “ vMware vCenter Converter Standalone Edition 6.2” installed on VMware vCenter Server 6.5 with “local install” option. We will retain same settings once we reduce size to 5GB. I have page file inside D: drive with user data as well as shown below. Please refer to “vMware vCenter Converter Standalone Edition 6.2” user guide for more detail. You may also need to firewall ports between “vMware vCenter Converter Standalone Edition 6.2” and source virtual machines as well. In production environment, we might need to disable AV/Security software so that it does not interfere with conversion process. Please note that it is carried out in plain vanilla environment where no AV software was installed inside the VM. Since virtual disk expansion is non-reversible process, it requires running vMware vCenter Converter Standalone Edition 6.2 to reduce the size of bloating VMDK file. Hard Disk 2 was expanded to 10GB instead of 5 GB. However, intent of the document is to outline process to achieve the same via an alternate way. It also helps in scenario where we do not want to run vMware vCenter Converter Standalone Edition 6.2 against all drives of virtual machines instead only selective volume and storage vMotion is not an option due to space availability issues in other datastore. We will only convert D: drive volume so that we can reduce its size to 5 GB from 10 GB. This scenario is applicable in a case where we just want to modify thick-disk lazy zeroed if it has been increased to large size and want to reclaim excessive disk assigned erroneously. We can selectively perform size reduction only via “vMware vCenter Converter Standalone Edition 6.2”. Since vMware vCenter Converter Standalone Edition 6.2 will create a brand new VM, we will attach reduced sized Thick-Disk Lazy Zeroed back to original VM which is ADLVM02. In this scenario, Thick-Disk Lazy Zeroed part of Hard Disk 2 will be reduced to 5GB because VMWare vCenter Server does not support size reduction once it is increased regardless of thin or thick disk. Target Virtual Machine :- Windows Server 2008 R1 x86 VCenter Server Version :- VMware vSphere vCenter 6.5 Build 5973321 VMware vCenter Converter Standalone Edition 6.2 is installed with “Local Installation” option during installation wizard.

Vmware converter standalone 6.5