Return to site

Converter unable to obtain hardware information

broken image
broken image
broken image

Add both of them in etc/hosts file on both source and converter machine. Look at vcenter and ESXi host to determine FQDN even if admins connect to it using IP. Use proxy mode in case source and Vcenter cant talk directly. Basically the VM should be able to resolve PSC and vCenter using FQDN. The machine where converter is installed should use same DNS (may be same AD server) as used by VMWare infrastructure.Disable firewall on VM where converter is installed.After this restart 'VMware vCenter Converter Standalone Worker' service.In most cases it improves conversion speed This could be in 'Program Files (x86)' or in 'C:\Users\All Users\VMware\VMware vCenter Converter Standalone' etc. Fine 'converter-worker.xml' in VMWare installation.This can be a different machine or VM from the machine being converted Install the converter on a Windows machine or VM.You will need a 'My VMWare' account for the download. Download correct VMWare standalone converter based on vCenter version from using 'Download now' button.VMWare standalone converter can be used for converting physical or virtual machines from different types of physical hardware or hypervisors to VMWare vCenter based VMs. Home > VMWare platform > VMWare vCenter > Migrate machines to VMWare vCenter VMs using standalone converter Migrate machines to VMWare vCenter VMs using standalone converter