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
Procedure
u
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"
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.
Remove a Desktop Pool From a Global Entitlement
You can remove a desktop pool from a global entitlement.
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.
Chapter 4 Managing a Cloud Pod Architecture Environment
VMware, Inc. 35