This article provides details on how to troubleshoot broken desktop issues.

Instructions

Some possible reasons for why a desktop can become broken are:

• DNS server is down and is unable to resolve the addresses of the servers in your grid. Check if the DNS server is up by pinging it.

• There is no sufficient disk space on the data store to provision desktops. Validate if the hypervisor data store has sufficient disk space to provision desktops.

• The hypervisor password was changed from outside VDI-in-a-box and the changes were not registered in kMGR. The behavior can be resolved by clearing all the broken desktops and reconfiguring VDI-in-a-box with the new hypervisor password.

• The password of the domain account used to prepare the published image was changed from outside VDI-in-a-box and the changes are not updated in the prepared image. The behavior can be resolved by fixing the prepared image by taking it through the draft image cycle to sysprep the image with a new password.

• For ESX Users, deleting a desktop instance provisioned from a VDI-in-a-box template can result in deleting the base image along with it. Citric recommends you to avoid such operations from outside VDI-in-a-box. Unfortunately, this is an unrecoverable operation. The only workaround is to rebuild image.

• Taking snapshots of the draft or test images from outside VDI-in-a-box would render the published image to an unusable state. This might lead to desktops in a broken state.

Clicking on the broken link from the Desktop > Summary tab, provides information on the last known status of the desktop. The last known status helps narrow the possible reasons why a desktop could have gone broken.