Message: A general system error occurred: The system returned an error. Communication with the virtual machine might have been interrupted.
If you look in vSphere at the same time, you will see a task that also fails with the same information. This doesn’t tell us exactly how the VM is broken, but it tells us pretty clearly that the VM is broken in vSphere. Unidesk can’t fix it. In fact, we probably can’t even delete it, which means we can’t do a repair to a new CP. Crtainly, any plain rebuild (including a Repair operation) will fail because vSphere itself won’t reconfigure the machine.
o You may be able to migrate this VM to a new host (do not change the datastore) to rehabilitate it.
o You may be able to remove it from the vSphere inventory, add it back, and then in Unidesk, System -> Synchronize Infrastructure to get us to use the new VM ID. Adding a machine to inventory doe a lot of sanity checking on the VMX file.
o You may, if you have a Unidesk backup, be able to remove it from the vSphere inventory, delete the boot image from the datastore, and use the Unidesk Repair function to recreate the VM.
o You may just have to open a case with VMware and get them to either fix to destroy that VM.