There are a number of different issues that can arise during the deployment of desktop pools. While it is impossible to try and list them all, the following represent some of the more common issues that can occur:

• Undersized or misconfigured DHCP address pool: This is more common with linked clones, which change MAC addresses when redeployed; this can exhaust a DHCP pool. Linked clone environments typically work best when the DHCP lease time is very short. Desktops cannot complete the provisioning process without access to the network.
• Issues with Windows operating system activation: If Windows KMS services are not functioning within the domain, the provisioning process will fail.
• Insufficient permissions within vCenter: If the accounts used by Horizon and Horizon Composer do not have the required permissions within vCenter, the provisioning process will fail.
• DNS not functioning properly: DNS is integral to desktop provisioning. If the desktops cannot resolve the IP addresses or infrastructure services, including Active Directory and Horizon components, the provisioning process will fail.

The Horizon event log, located in the Monitoring - Events window of the Horizon Administrator console, contains detailed information that can be used to troubleshoot the provisioning process.