Desktop edit fails with 'Couldn't find the current boot disk in the list of disk' or 'A configuration error exists'.  Note, "A configuration error exists" could also apply to an inconsistent snapshot configuration on the VM, so see this KB article as well.

This error means that the boot disk for this Unidesk desktop virtual machine has been disconnected from the VM and needs to be reattached manually.

When Unidesk updates a desktop VM or an Install Machine, it attaches the boot VMDK from the VM to the host CachePoint, rewrites the filesystem on the CachePoint, and reattaches it to the VM. Specifically, Unidesk does the following:

1. Unidesk detaches boot VMDK from the desktop.
2. Unidesk attaches the desktop VMDK to the CachePoint.
3. The CachePoint makes any necessary modifications to the boot disk.
4. Unidesk detaches the desktop VMDK from the CachePoint.
5. Unidesk reattaches the VMDK to the desktop VM.

If the task for this process fails before step 5, it's possible for the boot disk to not be reattached to the original VM. Any subsequent task issued to the desktop fails with this message:

The virtual infrastructure failed to reconfigure a virtual machine. Error is: Internal client error: 'Couldn't find the current boot disk in the list of disk'

To fix this error, manually edit the configuration of the VM to reattach the boot disk to the VM. The boot VMDK still exists in your VMware VMFS datastore.

To resolve the issue perform the following steps:

Reattach the desktop's VMDK to the desktop VM

1. In vSphere, select the affected desktop and note what datastore it is on. The Summary tab will show both the Boot Tier and the Layers Tier for this desktop, so you may need to check the CachePoint in the UDMC to know which is the Boot Tier.
2. Click Edit Settings, and check whether there is a Hard Disk device associated with the VM which is on the Boot Tier. The layer disks may still be attached. Verify whether there is a disk in the Boot Tier datastore attached at SCSI0:0 or IDE0:0.
3. If there is no boot disk connected, click Add..., Hard Disk, "Use an existing virtual disk", and find the boot VMDK for your VM in the datastore from step 1.
4. Use defaults for the rest of the wizard.

Once you have reconnected the disk to the desktop VM, restart it from the Unidesk management console. This will complete whatever task previously failed, reattach the layer disks, and boot the machine.

You may want to determine why the hard disk was not automatically reattached. First, attempt to find the original task for this desktop which failed and orphaned the VMDK, and look at the final status. It might tell you something about why the task failed in the first place.