6.0
Table Of Contents
- Administering View Cloud Pod Architecture
- Contents
- Administering View Cloud Pod Architecture
- Introduction to Cloud Pod Architecture
- Designing a Cloud Pod Architecture Topology
- Setting Up a Cloud Pod Architecture Environment
- Initialize the Cloud Pod Architecture Feature
- Join Pods to the Pod Federation
- Find and Change a Pod Name
- Create and Configure a Global Entitlement
- Create and Configure a Site
- Assign a Home Site to a User or Group
- Test a Cloud Pod Architecture Configuration
- Sample Scenario: Setting Up a Basic Cloud Pod Architecture Environment
- Managing a Cloud Pod Architecture Environment
- View a Cloud Pod Architecture Configuration
- View Pod Federation Health in View Administrator
- View Desktop Sessions in a Pod Federation
- Determine the Effective Home Site for a User
- Add a Pod to a Site
- Remove a Pod From a Pod Federation
- Modifying Global Entitlements
- Remove a Home Site Association
- Disable the Cloud Pod Architecture Feature
- lmvutil Command Reference
- Index
Example
lmvutil --authAs adminEast --authDomain domainEast --authPassword "*" --createGlobalEntitlement -
entitlementName "Agent Sales" --scope LOCAL
--isDedicated
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 this 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
Specifies the name of the global entitlement to modify.
--scope
Specifies the 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 within 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) Specifies a 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 functionality if the
--fromHome option was previously specified for the global entitlement.
Administering View Cloud Pod Architecture
54 VMware, Inc.