You use global entitlements to entitle users and groups to desktops in a Cloud Pod Architecture environment. A global entitlement provides the link between users and their desktops, regardless of where those desktops reside in the pod federation. You must create and configure at least one global entitlement to use the Cloud Pod Architecture feature.

A global entitlement contains a list of member users or groups, a list of the desktop pools that can provide desktops for entitled users, and a set of desktop policies. You can add both users and groups, only users, or only groups, to a global entitlement. You can add a particular desktop pool to only one global entitlement.

Prerequisites

  • Decide which type of global entitlement to create, the users, groups, and pools to include in the global entitlement, and the scope of the global entitlement. See Entitling Users and Groups in a Pod Federation.
  • Decide whether the global entitlement should use home sites. See Configuring Home Sites to Control Desktop Placement.
  • Create the desktop pools to include in the global entitlement. For information about creating desktop pools in View, see the Setting Up Desktop and Application Pools in View document.
  • Create the users and groups to include in the global entitlement.
  • Become familiar with the lmvutil command authentication options and requirements and verify that you have sufficient privileges to run the lmvutil command. See lmvutil Command Authentication.
  • Initialize the Cloud Pod Architecture feature. See Initialize the Cloud Pod Architecture Feature.

Procedure

  1. Run the lmvutil command with the --createGlobalEntitlement option to create the global entitlement.
    You can run this command on any View Connection Server in the pod federation.
    lmvutil --createGlobalEntitlement --entitlementName name --scope scope {--isDedicated | --isFloating} [--description text] [--disabled] [--fromHome][--multipleSessionAutoClean] [--requireHomeSite] [--defaultProtocol value] [--preventProtocolOverride] [--allowReset]
    Option Description
    --entitlementName

    Specifies the name of the global entitlement. The name can contain between 1 and 64 characters. The global entitlement name appears in the list of available entitlements for the user in Horizon Client.

    --scope
    Specifies the scope of the global entitlement. Valid values are as follows:
    • ANY - View looks for desktops on any pod in the pod federation.
    • SITE - View looks for desktops only on pods within the same site as the pod to which the user is connected.
    • LOCAL - View looks for desktops only in the pod to which the user is connected.
    --isDedicated

    Creates a dedicated entitlement. A dedicated entitlement can contain only dedicated desktop pools. To create a floating entitlement, use the --isFloating option. An entitlement can be either dedicated or floating. You cannot specify the --isDedicated option with the --multipleSessionAutoClean option.

    --isFloating

    Creates a floating entitlement. A floating entitlement can contain only floating desktop pools. To create a dedicated entitlement, specify the --isDedicated option. An entitlement can be either floating or dedicated.

    --description

    (Optional) Specifies a description of the global entitlement. The description can contain between 1 and 1024 characters.

    --disabled (Optional) Creates the global entitlement in the disabled state.
    --fromHome

    (Optional) If the user has a home site, causes View to look for desktops on the user's home site. If the user does not have a home site, View begins searching for desktops on the site to which the user is currently connected.

    --multipleSessionAutoClean

    (Optional) Logs off extra user sessions for the same entitlement. Multiple floating desktop 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 specify 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.

    --requireHomeSite

    (Optional) Causes the global entitlement to be available only if the user has a home site. This option is applicable only when the --fromHome option is also specified.

    --defaultProtocol

    (Optional) Specifies a default display protocol for desktops in the global entitlement. Valid values are RDP and PCOIP.

    --preventProtocolOverride

    (Optional) When this option is specified, users cannot override the default display protocol for desktops in the global entitlement. If you do not specify this option, users can override the default display protocol.

    --allowReset

    (Optional) When this option is specified, users can reset desktops in the global entitlement. If you do not specify this option, users cannot reset desktops.

    For example: 
    lmvutil --authAs adminEast --authDomain domainEast --authPassword "*" --createGlobalEntitlement -entitlementName "Agent Sales" --scope LOCAL 
--isDedicated
  2. On the View Connection Server instance in the pod that contains the desktop pool to add to the global entitlement, run the lmvutil command with the --addPoolAssociation option.
    Repeat the command for each desktop pool that you want to add to the global entitlement.
    Important: You must run this command on a View Connection Server instance in the pod that contains the desktop pool to add to the global entitlement.

    lmvutil --addPoolAssociation --entitlementName name --poolId poolid

    Option Description
    --entitlementName Specifies the name of the global entitlement to which to add the desktop pool. The name must match the name of an existing global entitlement.
    --poolId Specifies the ID of the desktop pool to add to the global entitlement. The pool ID must match the desktop pool name as it appears on the pod.
    For example: 
    lmvutil --authAs adminEast --authDomain domainEast --authPassword "*" --addPoolAssociation --entitlementName "Agent Sales" --poolId "Sales B"
  3. To add a user to the global entitlement, run the lmvutil command with the --addUserEntitlement option.
    You can run this command on any View Connection Server instance in the pod federation. Repeat the command for each user that you want to add to the global entitlement.

    lmvutil --addUserEntitlement --userName domain\username --entitlementName name

    Option Description
    --userName Specifies the name of a user to add to the global entitlement. Use the format domain\username.
    --entitlementName Specifies the name of the global entitlement to which to add the user. The name must match the name of an existing global entitlement.
    For example: 
    lmvutil --authAs adminEast --authDomain domainEast --authPassword "*" --addUserEntitlement --userName domainCentral\adminCentral --entitlementName "Agent Sales"
  4. To add a group to the global entitlement, run the lmvutil command with the --addGroupEntitlement option.
    You can run this command on any View Connection Server instance in the pod federation. Repeat the command for each group that you want to add to the global entitlement.

    lmvutil --addGroupEntitlement --groupName domain\groupname --entitlementName name

    Option Description
    --groupName Specifies the name of a group to add to the global entitlement. Use the format domain\groupname.
    --entitlementName Specifies the name of the global entitlement to which to add the group. The name must match the name of an existing global entitlement.
    For example: 
    lmvutil --authAs adminEast --authDomain domainEast --authPassword "*" 
--addGroupEntitlement --groupName domainCentral\adminCentralGroup --entitlementName "Agent Sales"

Results

The Cloud Pod Architecture feature stores the global entitlement in the Global Data Layer, which replicates the global entitlement on every pod in the pod federation. When an entitled user uses Horizon Client to connect to a desktop, the global entitlement name appears in the list of available desktop pools.

When you add a desktop pool to a global entitlement, View checks to make sure that the desktop pool's default display protocol, protocol override, and virtual machine reset policies support the equivalent policies set for the global entitlement.

If a View administrator changes the pool-level display protocol or protocol override policy after a pool is associated with a global entitlement, users can receive a desktop launch error when they select the global entitlement. If a View administrator changes the pool-level virtual machine reset policy after a pool is associated with the global entitlement, users can receive an error if they try to reset the virtual machine.