Using vSphere 4 hosts (in this case a legacy un-patched host that was being migrated off and decommissioned), we came across an interesting and ambiguois error – ‘Invalid configuration for device ’0′, plus a note of time, the target object and the vCenter Server.
In this case, I was trying to migrate a powered-off VM to different storage – resulting in the error. I also found that the issue was related to the second disk attached to the VM. Editing the VM showed the size as 0MB, but removing this disk also threw the error in vCenter.
The solution was to follow these steps:
- Remove the VM from the vCenter inventory.
- Update the VM VMX file. There are 2 ways to do this – SSH to the host / datastore using a tool like Putty, or use the datastore browser to download the VMX file, then edit the it in Notepad.
- Inside the VMX file. look for the following entries:
scsi0:1.present = “true”
scsi0:1.fileName = “vmname.vmdk”
Update these entries to the following:
scsi0:1.present = “false”
scsi0:1.fileName = “vmname.vmdk”
- Re-add the VM to the vCenter inventory, either through the GUI or using ‘vmware-cmd -s register \path\to\your\vm.vmdk’.
- Check the VM properties, you should now show the offending drive as missing and it can be re-added from the datastore.


If you don’t know what VMTN is, you might be new to VMware virtualisation or the IT industry. Either way, I have an 