When you delete a physical machine, the platform will put all VMs in the “Not allocated” state, without changing the VMs on the hypervisor. (Note that you cannot deploy the captured VMs again unless you recreate them from an instance template).
If you later add the physical machine again or upgrade to cluster as physical machine, the platform will automatically update all VMs from the hypervisor, returning captured VMs running on the hypervisor to a deployed state. In the API these resynchronized VMs will have the same ID and URL as before.
Screenshot: a vCenter with captured VMs.
Screenshot: On deleting the physical machine, the VMs are put in a Not allocated state
Screenshot: After adding the physical machine (or upgrading to use clusters as physical machines), the VMs are automatically recovered as captured VMs. Here the list of VMs is sorted by virtual datacenter name.
Screenshot: The VMs in the virtual appliance are deployed in the ON or OFF state