Use this worksheet to prepare your configuration options before you create the global entitlement in Horizon Console.
You can print this worksheet and write down the values to specify when you add a global entitlement.
Worksheet: Options for Configuring a Global Entitlement
| Option | Description | Fill In Your Value Here |
|---|---|---|
| Name | Unique name that identifies the global entitlement in Horizon Console. The name can contain between 1 and 64 characters. | |
| Display Name | (Optional) Display name of the global entitlement. The display name appears to users in the list of available desktops and applications in Horizon Client. The display name does not need to be unique. Multiple global entitlements can have the same display name. If you do not specify a display name, the unique name appears to users in Horizon Client. The display name can contain between 1 and 64 characters. | |
| Federation Access Group | Associates the global entitlement and its sessions with a federation access group. Federation access groups enable you to delegate the administration of specific global entitlements and global sessions to different administrators. The default setting is the root federation access group. For more information, see Setting Up Federation Access Groups in Horizon Console. | |
| Description | (Optional) Description of the global entitlement. The description can contain between 1 and 1024 characters. | |
| Connection Server Restrictions | (Optional) Associates Connection Server tags with the global entitlement to restrict access to the global entitlement from specific Connection Server instances. Note: You can select only tags that are assigned to Connection Server instances in the local pod. To select tags assigned to Connection Server instances in another pod, you must log in to a Connection Server instance in the other pod and modify the global entitlement. For more information, see How to Specify Connection Server Restrictions for Global Entitlements in Horizon 8. | |
| Category Folder | (Optional) Creates a shortcut for the global entitlement. You can select an existing category folder, or create a category folder. You can configure up to four subfolders. You can configure a Windows Start menu shortcut, a desktop shortcut, or both.
A folder name can be up to 64 characters long. To specify a subfolder, enter a backslash (\) character, for example, dir1\dir2\dir3\dir4. You can enter up to four folder levels. You cannot begin or end a folder name with a backslash, and you cannot combine two or more backslashes. For example, \dir1, dir1\dir2\, dir1\\dir2, and dir1\\\dir2 are invalid. You cannot enter Windows reserved keywords.
For more information, see Configuring Shortcuts for Global Entitlements in Horizon 8. | |
| Backup Global Entitlement | (Only available when you edit a global entitlement) A backup global entitlement delivers remote desktops or published applications when the primary global entitlement cannot start a session. For requirements and restrictions, see Implementing Backup Global Entitlements in Horizon 8. | |
| User Assignment | (Global desktop entitlement only) Specifies the type of desktop pool that the global entitlement can contain. You can configure one of the following user assignment policies:
| |
| Scope | Specifies where to look for desktops or applications to satisfy a request from the global entitlement. You can configure one of the following scope policies:
| |
| Use Home Site and Entitled user must have Home Site | (Optional) If users have home sites, configures a home site policy for the global entitlement. You can configure the following home site policies:
| |
| Automatically Clean Up Redundant Sessions | (Optional) Specifies whether to clean up redundant sessions. Multiple sessions can occur when a pod that contains a session goes offline, the user logs in again and starts another session, and the problem pod comes back online with the original session. When multiple sessions occur, Horizon Client prompts the user to select a session. This option determines what happens to sessions that the user does not select. If you do not select this option, users must manually end their own extra sessions, either by logging off in Horizon Client or by launching the sessions and logging them off. | |
| Default Display Protocol | Specifies the default display protocol for desktops or applications in the global entitlement. Choices are PCoIP and Horizon Blast. | |
| Allow Users to Choose Protocol | When you enable this policy, users can override the default display protocol. | |
| Session Distribution Policy (version 2306) | Select Session Count to distribute new sessions evenly across available resources within the global application entitlement or global desktop entitlement based on their current utilization. The default is None. | |
| Use Preferred Sites (version 2606 and later) | (Optional) When you enable this policy, Horizon 8 searches the connecting site's configured preferred sites, in the order you ranked them, before falling back to the remaining sites in the pod federation. Applies only when Scope is set to All Sites. Preferred sites are not used unless this option is selected. You define the ordered list of preferred sites per site. See Create and Configure a Site in Horizon Console. For more information, see Preferred Sites and Cloud Pod Architecture in Horizon 8. | |
| Ignore Preferred Sites with High Load (version 2606 and later) | (Optional) Available only when Use Preferred Sites is selected. Specify a load threshold from 0 to 100. If a preferred site's current load exceeds the threshold, Horizon 8 skips that site and continues to the next preferred site. The default threshold is 98. Note: This option requires a Session Load Distribution policy (Load Index or Session Count) to be configured on the global entitlement, as Horizon uses it to determine each site's current load. See Understanding Session Load Distribution Policy. | |
| Session Load Distribution (version 2309 and later) | Specifies the type of session distribution policy to be used for evenly distributing CPA sessions across pods/sites based on the global desktop entitlement or global application entitlement scope. See Understanding Session Load Distribution Policy for details on the policy options and resulting behavior. | |
| Preferred Sites (version 2606 and later) | Select to configure an ordered list of CPA sites that Horizon 8 searches, in priority order, when a user’s initial site cannot satisfy a desktop or application request. See Preferred Sites and Cloud Pod Architecture in Horizon 8 for details. | |
| Allow Users to Restart Machines | (Global entitlement only) When you enable this policy, users can reset and restart desktops in the global desktop entitlement. | |
| Pre-launch | (Global application entitlement only) When you enable this policy, users can start the global application entitlement more quickly. Note: If you enable this policy, all the application pools in the global application entitlement must also support the session pre-launch feature, and the pre-launch session timeout must be the same for all farms. | |
| Enable application launch limit | You can limit the number of application instances a user can launch from an application pool to just one instance. An attempt to re-launch the application will bring the first instance to focus. If you enable this setting, multi-session mode is not available. | |
| Allow Session Collaboration | When you enable this policy, users can invite other users to join their remote desktop sessions. Note: If you enable this policy, all the desktop pools in the global desktop entitlement must also support the Session Collaboration feature. For RDS desktop pools, the Session Collaboration feature is activated at the farm level. For more information, see Enabling Session Collaboration for Global Desktop Entitlements in Horizon 8. | |
| Allow PCoIP Ultra | (Global application entitlement only) Select Allow PCoIP Ultra to enable PCoIP Ultra. | |
| Allow user to initiate separate sessions from different client devices | (Global desktop entitlement only) When you enable this policy, users that connect to the global entitlement from different client devices receive different desktop sessions. To reconnect to an existing desktop session, users must use the same device from which that session was initiated. If you do not enable this policy, users are always reconnected to their existing desktop sessions, regardless of the client device that they use. You can enable this policy only for floating desktop entitlements. Note: If you enable this policy, all the desktop pools in the global entitlement must also support multiple sessions per user. For more information, see Understanding the Multiple Sessions Per User Policy for Global Desktop Entitlements. | |
| Client Restrictions | When you enable this policy, access to the global entitlement is restricted to specific client computers. You can enable this policy only for floating desktop entitlements and global application entitlements. You must add the names of the computers that are allowed to access the global entitlement in an Active Directory security group. You can select this security group when you add users or groups to the global entitlement. For more information, see Implementing Client Restrictions for Global Entitlements in Horizon 8. | |
| Multi-Session Mode | (Global application entitlement only) Use this policy to configure the multi-session mode feature for a global application entitlement. Valid values are as follows.
| |
| Show Assigned Machine Name | (Global entitlement only) Displays the host name of the assigned machine instead of the global entitlement name in Horizon Client. If no machine is assigned to the user, "Entitlement name (No Machine Assigned)" appears for the global entitlement in Horizon Client. Note: If the pod that contains the machine is unavailable or does not reply in time, Connection Server cannot get the assigned machine name. In such cases, "Entitlement name (Unable to get machine name)" appears instead of the global entitlement name in Horizon Client. This option is available only if you select Dedicated in User assignment. | |
| Show Machine Alias Name | (Global desktop entitlement only) Displays the alias name of the assigned machine instead of the global entitlement name in Horizon Client. If no machine alias name is set, the host name of the assigned machine appears in Horizon Client. This option is available only if you select Dedicated in User assignment. | |
| Allow Machine Name Selection | Enabling this option will allow a command line launch of Horizon Client to specify a machine name to connect to, for example for test or troubleshooting purposes. Applies only to floating desktop pools, published RDS Desktops and Published Applications. All underlying Desktop or Application Pools must also have this setting enabled. | |
| Isolated Session Mode | You can configure an application pool so that every launch of the application starts in a new, separate RDSH session rather than joining an existing session for that user. This applies whether it's an additional launch of the same application, or a launch of a different application from the same farm. Each application launch starts in a new, independent session rather than reusing one, allowing users to run multiple concurrent instances of the same application in fully isolated sessions, which supports workflows where per-instance session isolation is required. The new session can be created on the same RDS host or a different RDS host within the farm.
This setting is disabled by default and must be explicitly enabled when you create or edit the application pool. It can also be enabled at the Global Application Entitlement level. Before enabling this setting, ensure the farm has sufficient capacity for the expected number of concurrent application sessions per user, since each launch consumes a separate session rather than sharing one. When enabled, the administrator should set a Max Isolated Sessions value which sets an upper limit on the number of instances of the app each user can launch. The default is 10. Client support for this feature:
Note: Isolated Application Launch cannot be enabled together with Enable single application launch limit. |
Was this page helpful?