Finding and Allocating Desktops and Applications in the Pod Federation

<

Connection Server instances in a Cloud Pod Architecture environment use shared global entitlement and topology configuration information from the Global Data Layer to determine where to search for and how to allocate desktops and applications across the pod federation.

When a user requests a desktop or application from a global entitlement, Horizon searches for an available desktop or application in the pools that are associated with that global entitlement. By default, Horizon gives preference to the local pod, the local site, and pods in other sites, in that order.

For global desktop entitlements that contain dedicated desktop pools, Horizon uses the default search behavior only the first time a user requests a desktop. After Horizon allocates a dedicated desktop, it returns the user directly to the same desktop.

You can modify the search and allocation behavior for individual global entitlements by setting the scope policy and configuring home sites.

When you create a global desktop entitlement or global application entitlement, you must specify its scope policy. The scope policy determines the scope of the search when Horizon looks for desktops or applications to satisfy a request from the global entitlement.

When you create a global desktop entitlement, you can specify whether users can initiate separate desktop sessions from different client devices. The multiple sessions per user policy applies only to global desktop entitlements that contain floating desktop pools.

A home site is a relationship between a user or group and a Cloud Pod Architecture site. With home sites, Horizon begins searching for desktops and applications from a specific site rather than searching for desktops and applications based on the user's current location.