After a power Outage some machines were moved from one VMWare host to another. This caused a change in the UUID.BIOS parameter of the machines on the hyper-visor. However the HostedMachineID for the same machines on the XenDesktop was still the one that the machines had before the power outage. This leads to a mismatch of the UUIDs and hence the power states of the machines went unknown. This results in users receiving the 1030 error when attempting to launch the machines.

This is expected behavior in XenDesktop 7.x and requires a different method to resolve the HostedMachine ID mismatch. This articles describes an alternate method to change the HostedMachineID on the VMware .vmx file to match with the ID in XenDesktop.

1. Power off the "bad" VMs.

2. Enable SSH on the VMWare Host that is hosting the "bad" machine(s):
   

3. Initiate a putty session to the VMWare host on which the "bad" machine lies.

4. Navigate to the storage location for the VDMK for the bad machine.
   

5. Pull up the "bad" machine (run: cd examplevm) and take a backup of the .vmx file by using the following command:
   cp examplevm.vmx examplevm.vmx.bak

6. Once the backup is done, modify the original .vmx file to change the UUID.BIOS parameter by using the command:
   vi examplevm.vmx

7. To save the changes run:
   wq
   Alternatively wq! should overwrite read only permissions if using the root account.

8. Run  command below to verify the new UUID of the machine:
   cat examplevm.vmx|grep uuid

9. Now the new .vmx file needs to be reloaded. Run the following commands to reload the new .vmx file:
   vim-cmd vmsvc/getallvms
   This command gave an output of the serial number related to each vmx file.
   Find out the required number (ex. 32)  and run the following command to reload the vmx file:
   vim-cmd vmsvc/reload 32

10. Boot up the machine.
    Now the machine should have the new UUID. You should see the correct power state of the machines on the XenDesktop studio. Do the same procedure for all the machines.

Problem Cause