Installation and Use of Converter Standalone 5.5

[TheKid7]

vSphere 5.1, VMware 5.1, Windows Server 2012 R2 64 bit VM's

I am new to VM's and VMware.  I did not know until today that if you allocate a certain amount of Disk Space to a VM and later decide to reduce the Disk Space allocation, you need to 'Convert' the VM with a reduced amount of space during the conversion.  I allocated 300 GB to a VM and I now want the allocation to be 100 GB.  The actual Windows Server 2012 R2 64 bit partition size is currently 40 GB.

What I want to do is to install Converter 5.5 on the same Physical Server (Windows Storage Server 2012 64 bit) where I currently have vSphere 5.1 installed.  I would like to use Converter 5.5 to convert the VM which has the excessive Disk Space allocation from this Physical Server.

1.  What options do I use during the Converter 5.5 installation (Converter Standalone Server?, Converter Standalone Agent?, Converter Standalone Client?, etc.)

2.  Are there any special Tips/Guidance for the conversion to a VM with less Disk Space allocation?

Thanks in Advance.

[TheKid7]

I figured out how to install the Converter Standalone 5.5.  It is now properly installed.

VM Conversion:  I got stuck on the step under Select a Managed Destination:  "Name the Destination Virtual Machine and Select a Folder"

Do I need to create an 'empty' VM first?  All I see showing up are my existing VM's, with no option to name a new VM.

Thanks in Advance.

[rcporto · Accepted solution]

Do I need to create an 'empty' VM first?  All I see showing up are my existing VM's, with no option to name a new VM.

No, you don't need create a "empty" VM, just type the name for the new VM and try use a different name than the VMs listed on the right panel.

[TheKid7]

Thank you.

I understand now.  I see that, by default, the name of the VM being converted was added to the place where you type in the new VM name.  The only issue that I had with conversion was that I only changed the disk allocation size to what I wanted.  I have been using a different that typical Ethernet Adapter due to an issue with the version of VMware (Dell ESXi 5.1.X) that I am using.  I successfully did the conversion again with the correct Ethernet adapter.