In this post we will continue covering the objective from the blueprint and now its time for the Consolidate Physical Workloads using VMware Converter
The following are the blueprint objective:
- Install vCenter Converter standalone instance
- Convert physical workloads using vCenter Converter
- Modify server resources during conversion
- Resize partitions during the conversion process
- Interpret and correct errors during conversion
- Collect diagnostic information during conversion operation
Install vCenter Converter standalone instance:
Use case for converter:
- Import running remote physical and VM’s
- Import Hyper-V
- Import VMware workstation VM’s
- Export VM’s to other VMware format
The installation process is very simple , the only thing that is different is that you can install this as client -server i choose to install it as local installation.
Convert physical workloads using vCenter Converter:
I dont have a physical machine in my lab but for this task i used one of my VM as a “physical” machine
to convert machine start the application and click on convert machine
Provide the machine credentials , in windows 10 you will have to enable local administrator account , click on view source details and you can choose to remove the agent that is installed on the machine automatically.
Choose the destination type which can be also VMware workstation but i choose the VMware infrastructure VM
also type the credentials for vCenter
Next you can change the name of the VM and choose the datacenter
Choose the host,datastore and the VM version (i shirked the lab for one host)
Next you need to configure the option for that VM, more on the option in the next subject down below
when all done with the wizard you will see the conversion progress for that VM.
Modify server resources during conversion:
During the conversion you can choose to modify the resources in the options screen there is a lot of option and i am going to highlight some of the major ones.
If your physical machine is active and data keep changing you can enable synchronization and apply the time for the sync.
If the machine is very active and you dont want to impact performance you can throttle the CPU and the network bandwidth.
Resize partitions during the conversion process:
In “data to copy” under the advanced settings you can change the following:
- Make the disk thin/think
- Change the destination datastore
- change the size of the vol , you can also manually type the size in GB/MB
Collect diagnostic information during conversion operation:
The subject said to collect diagnostic information during conversion operation , you can also take diagnostics after the process is done
Interpret and correct errors during conversion:
the only actual issue with the conversion that i faced was connecting to the “physical” machine, since i used Windows 10 i didnt have an active administrator account and my domain admin wasn’t able to access the $ADMIN directory , so i had to enable the administrator account
also when i practice this task several times i noticed that i needed to reboot the |physical” machine between each conversions.
Thanks for reading