VMware converter "Unable to obtain hardware information for the selected machine" (4047627)

After completing a successful "Virtual Machine Files Only Restore", using the "Restore Files from Backup" option, the vCenter Converter fails to convert  the restored files to create a virtual machine, showing the following error:

"Unable to obtain hardware information for the selected machine" or "Can't determine guest OS"

Navigate to the target directory where the virtual machine files were restored and note the filename(s) of the virtual disks.

Here is an example of the files generated from a "Virtual Machine Files Only Restore" of a VADP backup of a VM that did not have any existing snapshots:

MyVirtualMachine.vmx
scsi0-0-MyVirtualMachine.vmdk
scsi0-0-MyVirtualMachine-s001.vmdk
VirtualMachineConfigInfo

- Open the .vmx file.

- Modify the relevant entries for the virtual disk(s).
For example, modify the following entry
scsi0:0.fileName = "MyVirtualMachine-000001.vmdk"
so that it matches the smallest lead .vmdk file generated during the restore
scsi0:0.fileName = "scsi0-0-MyVirtualMachine.vmdk"

Note that you may end up with several files restored on this location, so the .vmx file needs to point to the smallest .vmdk file which in turns points to the rest of the files.

- After modifying the .vmx file, launch the VMware vCenter Converter Standalone
Client Wizard to create the virtual machine.

- Follow the wizard as it takes you through the various steps. When the "Select source type:" prompt appears, select "VMware Workstation or other VMware virtual machine".

- For the "Virtual machine file" parameter, select the restored .vmx file.
Note: In the scenario described in the article http://kb.vmware.com/kb/1019286, the .vmx file will not be backed up. The .vmdk files will still be available.


Important Note:

It should also be recognised that Netvault does not backup 'independent-persistent' disks with the image backup option. However, NetVault backs up the unmodified vmx file which contains entries for these disks. So the same error will be seen when restoring from files if the system backed up contained 'independent-persistent' disks. The entry in the VMX file will look similar to the below example. This needs to be removed.


scsi0:2.fileName = "scsi0-2-MyVirtualMachine.vmdk"
scsi0:2.mode = "independent-persistent"
scsi0:2.ctkEnabled = "FALSE"
scsi0:2.deviceType = "scsi-hardDisk"
scsi0:2.present = "TRUE"
scsi0:2.redo = ""