You can use several procedures for diagnosing and fixing problems with the provisioning or recreation of desktop pools. Instant-Clone Provisioning or Push Image FailureThe pending image of an instant-clone desktop pool is in a failed state. Instant Clone Image Publish FailureHorizon Administrator shows that an image publish failed. Endless Error Recovery During Instant-Clone ProvisioningError recovery falls into an endless loop during the provisioning of an instant-clone desktop pool Cannot Delete Orphaned Instant ClonesOn rare occasions, during provisioning, an instant clone gets into an error state and you cannot delete the desktop pool from Horizon Administrator. Pool Creation Fails if Customization Specifications Cannot Be FoundIf you try to create a desktop pool, the operation fails if the customization specifications cannot be found. Pool Creation Fails Because of a Permissions ProblemYou cannot create a desktop pool if there is a permissions problem with an ESX/ESXi host, ESX/ESXi cluster, or datacenter. Pool Provisioning Fails Due to a Configuration ProblemIf a template is not available or a virtual machine image has been moved or deleted, provisioning of a desktop pool can fail. Pool Provisioning Fails Due to a View Connection Server Instance Being Unable to Connect to vCenterIf a Connection Server is not able to connect to vCenter, provisioning of a desktop pool can fail. Pool Provisioning Fails Due to Datastore ProblemsIf a datastore is out of disk space, or you do not have permission to access the datastore, provisioning of a desktop pool can fail. Pool Provisioning Fails Due to vCenter Server Being OverloadedIf vCenter Server is overloaded with requests, provisioning of a desktop pool can fail. Virtual Machines Are Stuck in the Provisioning StateAfter being cloned, virtual machines are stuck in the Provisioning state. Virtual Machines Are Stuck in the Customizing StateAfter being cloned, virtual machines are stuck in the Customizing state. Removing Orphaned or Deleted Linked ClonesUnder certain conditions, linked-clone data in View, View Composer, and vCenter Server might get out of synchronization, and you might be unable to provision or delete linked-clone machines. Troubleshooting Machines That Are Repeatedly Deleted and RecreatedView can repeatedly delete and recreate linked-clone and full-clone machines that are in an Error state. Troubleshooting QuickPrep Customization ProblemsA View Composer QuickPrep customization script can fail for a variety of reasons. Finding and Unprotecting Unused View Composer ReplicasUnder certain conditions, View Composer replicas might remain in vCenter Server when they no longer have any linked clones associated with them. View Composer Provisioning ErrorsIf an error occurs when View Composer provisions or recomposes linked-clone machines, an error code indicates the cause of the failure. The error code appears in the machine-status column in View Administrator. Parent topic: Troubleshooting Machines and Desktop Pools
