You can use Horizon Administrator to modify the name, description, attributes, tags, scope, and other policies of a global entitlement.
About this task
You cannot modify the type of desktop pool that a global desktop entitlement can contain.
- Log in to the Horizon Administrator user interface for any Connection Server instance in the pod federation.
- In Horizon Administrator, select .
- Select the global entitlement and click Edit.
- To modify the name or description of the global entitlement, type a new name or description in the Name or Description text box in the General pane.
The name can contain between 1 and 64 characters. The description can contain between 1 and 1024 characters.
- To remove or modify the tags that are associated with the global entitlement, click the Connection Server restrictions Browse button.
You can select No restrictions to remove all of the existing tags, or you can select Restricted to these tags to associate the global entitlement with different tags. Only the Connection Server instances that have the selected tags can access the global entitlement.Note:
You can only select tags 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 Horizon Administrator for a Connection Server instance in the other pod and modify the global entitlement again.
- To add, remove, or modify a Windows Start menu shortcut for the global entitlement, click the Category Folder Browse button.
You can select Disabled to remove an existing shortcut, or select Select a category folder from the folder list to select a different category folder. To add a new category folder, type the folder name in the New Folder text box, click Add, and then select the new folder from the list.
- To modify a global entitlement policy, select or deselect the policy in the Policy pane.
Specifies where to look for desktops or applications that satisfy a desktop or application request from the global entitlement. You can select only one scope policy.
All sites - look for desktops or applications on any pod in the pod federation.
Within site - look for desktops or applications only on pods in the same site as the pod to which the user is connected.
Within pod - look for desktops or applications only in the pod to which the user is connected.
Use home site
Determines whether to begin searching for desktops or applications in the user's home site. If the user does not have a home site and the Entitled user must have home site option is not selected, the site to which the user is currently connected is assumed to be the home site.
Entitled user must have home site
Makes the global entitlement available only if the user has a home site. This option is available only when the Use home site option is selected.
Automatically clean up redundant sessions
Logs off extra user sessions for the same entitlement.. This option is available only for floating desktop entitlements and application entitlements.
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.
Determines whether to allow users to use the HTML Access feature to access desktops or applications in the global entitlement. When you enable the HTML Access policy, end users can use a Web browser to connect to remote desktops and are not required to install any client software on their local systems.
Allow user to initiate separate sessions from different client devices
Determines whether to allow users to initiate separate desktop sessions from different client devices. When you enable the multiple sessions per user 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 setting, users are always reconnected to their existing desktop sessions, regardless of the client device that they use. You can enable this setting only for floating desktop entitlements.Note:
If you enable this policy, all the desktop pools in the global desktop entitlement must also support multiple sessions per user.
Determines whether to launch the application session before a user opens the global application entitlement in Horizon Client. When you enable the pre-launch policy, users can launch 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.
Determines whether to restrict access to the global entitlement to specific client computers. 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.Note:
You can enable this policy only for floating desktop entitlements and global application entitlements.
- To modify the application path, version, and publisher information for a global application entitlement, type values in the application text boxes.
If you add an application pool to the global application entitlement after you modify these values, the values are overwritten with values from the application pool.
- Click OK to save your changes.