When you create a global desktop entitlement or global application entitlement, you can specify its Session Load Distribution policy. The Session Load Distribution policy determines which of the underlying Desktop or Application Pool resources are used for new connections, depending on the scope of the global entitlement.

When Session Count is selected as the Session Load Distribution policy, Horizon will attempt to balance the sessions across the resources evenly, in proportion to their capacity. Their capacity is determined based on the Max sessions per RDS Host Farm setting for Automated Instant-Clone farms (150 sessions is used as the default capacity for session load distribution if unlimited is selected), or the Number of connections setting for manual RDSH Farms.

Table 1. Session Load Distribution Behavior
Global Entitlement Scope Session Load Distribution Behavior
All Sites Distribute the connecting user’s session across all resources within the site they connect to or to the home site (if set). For the selected site, connection is attempted to the least loaded pool/farm within the least loaded Pod.
Note: If a resource is not found, the search continues for a resource in the remaining sites, starting with the least-loaded site, until a resource is found or all sites are exhausted.
Within Site Distribute the connecting user’s session across all resources within the site they connect to. Connection is attempted to the least loaded pool/farm within the least loaded Pod.
Note: The resource search is limited to finding the least loaded resource only in the home site (if set) or in the connecting site.
Within Pod Distribute the connecting user’s session across all resources within the Pod they connect to. Connection is attempted to the least loaded pool/farm.

By default, None is selected for session load distribution policy, which means that Horizon will not attempt to distribute new sessions evenly across the underlying resources.