After creating a global entitlement, an administrator clicks on the name and navigates to Local Pools. The administrator clicks on Add but no local pools show up in the selection windows. What can be one explanation for this?

For a local pool to be added to a global entitlement in a Cloud Pod Architecture, its configuration must be compatible with the policies defined in the global entitlement. If there is a mismatch in key settings, the pool will not be available for selection. For example, if the global entitlement's "Allow users to choose protocol" setting is "No," but the local pool's setting is "Yes," that pool is considered incompatible and will not appear in the "Add Local Pools" dialog.

A. Global entitlements can only be configured with local Instant clone pools: Global entitlements support multiple pool types, including instant clone, full clone, and manual pools.
B. Global entitlements can only be configured with local manual pools: Global entitlements are not restricted to only manual pools; they support automated pools as well.
D. Global entitlements can only be configured with local RDSH pools: Global entitlements support both VDI desktop pools and RDSH application/desktop pools.

1. VMware Docs, Horizon 8 Administration, "Prerequisites for Creating Global Entitlements". States, "To add a desktop pool to a global desktop entitlement, the desktop pool must have certain characteristics... If a desktop pool does not meet these prerequisites, you cannot add it to the global desktop entitlement."

2. VMware Docs, Horizon 8 Administration, "Create a Global Desktop Entitlement". The table "Global Desktop Entitlement Policies" lists settings that must be compatible with the underlying local pools.