Administering View Cloud Pod Architecture

Modifying a Global Entitlement
You can use the lmvutil command with the --updateGlobalEntitlement option to modify the scope,
description, and other attributes of a global entitlement.
Syntax
lmvutil --updateGlobalEntitlement --entitlementName name
[--scope scope] [--description text] [--disabled] [--enabled]
[--fromHome] [--disableFromHome] [--multipleSessionAutoClean] [--disableMultipleSessionAutoClean]
[--requireHomeSite] [--disableRequireHomeSite] [--defaultProtocol value]
Usage Notes
You can use the lmvutil command on any View Connection Server instance in a pod federation. View stores
new data in the Global Data Layer and replicates that data among all pods in the pod federation.
This command returns an error message if the global entitlement does not exist, the scope is invalid, the
Cloud Pod Architecture feature is not initialized, or the command cannot update the global entitlement.
Options
You can specify these options when you modify a global entitlement.
Table 5‑9. Options for Modifying Global Entitlements
Option Description
--entitlementName
Name of the global entitlement to modify.
--scope
Scope of the global entitlement. Valid values are as follows:
n
ANY. View looks for desktops on any pod in the pod federation.
n
SITE. View looks for desktops only on pods in the same site as the
pod to which the user is connected.
n
LOCAL. View looks for desktops only in the pod to which the user
is connected.
--description
(Optional) Description of the global entitlement. The description can
contain between 1 and 1024 characters.
--disabled
(Optional) Disables a previously enabled global entitlement.
--enabled
(Optional) Enables a previously disabled global entitlement.
--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.
--disableFromHome (Optional) Disables the --fromHome option function if the --fromHome
option was previously specified for the global entitlement.
--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.
Administering View Cloud Pod Architecture
48 VMware, Inc.