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
Option Description
--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.
--disableMultipleSessionAutoClean
(Optional) Disables the --multipleSessionAutoClean option
functionality if the --multipleSessionAutoClean option was previously
specified for the global entitlement.
--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.
--disableRequiredHomeSite
(Optional) Disables the --requireHomeSite option functionality if the
--requireHomeSite option was previously specified for the global
entitlement.
--defaultProtocol
(Optional) Specifies a default display protocol for desktops in the global
entitlement. Valid values are RDP and PCOIP.
For example:
lmvutil --authAs adminEast --authDomain domainEast --authPassword "*" --
updateGlobalEntitlement -entitlementName "Agent Sales" --scope ANY
--isDedicated
Delete a Global Entitlement
You can use the lmvutil command to permanently delete a global entitlement. When you delete a global
entitlement, all of the users who are dependent on that global entitlement for desktops can no longer access
their desktops. Any existing desktop sessions remain connected.
To modify the list of users or groups in a global entitlement, use the lmvutil command with the
--addUserEntitlement or --addGroupEntitlement option. To disable a global entitlement, use the
lmvutil command with the --updateGlobalEntitlement and --disabled options.
Prerequisites
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,” on
page 43.
Procedure
u
On any View Connection Server instance in the pod federation, run the lmvutil command with the
--deleteGlobalEntitlement option.
lmvutil --deleteGlobalEntitlement --entitlementName name
The --entitlementName option specifies the name of the global entitlement to delete.
For example:
lmvutil --authAs adminEast --authDomain domainEast --authPassword "*"
--deleteGlobalEntitlement --entitlementName "Agent Sales"
Chapter 4 Managing a Cloud Pod Architecture Environment
VMware, Inc. 39