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
This command adds the Central Pod 1 pod to the Central Region site:
lmvutil --authAs adminEast --authDomain example --authPassword "*" --assignPodToSite --
podName "Central Pod 1" --siteName "Central Region"
This command adds the Central Pod 2 pod to the Central Region site:
lmvutil --authAs adminEast --authDomain example --authPassword "*" --assignPodToSite --
podName "Central Pod 2" --siteName "Central Region"
The pod federation site topology now reflects the geographic distribution of pods in the insurance
company's network.
Creating a Single Global Entitlement
A View administrator creates a single global entitlement to entitle all sales agents to all desktops in the sales
agent desktop pools across all pods in the pod federation.
1
The View administrator runs the lmvutil command with the --createGlobalEntitlement option to
create the global entitlement. A View administrator can run this command on any View Connection
Server instance in the pod federation. In this example, the View administrator runs the command on
east1.example.
lmvutil --authAs adminEast --authDomain example --authPassword "*" --createGlobalEntitlement
--entitlementName "Agent Sales" --isFloating --scope ANY
2
The View administrator runs the lmvutil command with the --addPoolAssociation option to add
each desktop pool to the newly created Agent Sales global entitlement. A View administrator must run
these commands on the View Connection Server instances where the pools are located. Each pod in the
insurance company's View implementation has two pools, called Sales A and Sales B.
n
To add the pools in the Eastern region pod to the Agent Sales global entitlement, the View
administrator runs the following commands on east1.example.
lmvutil --authAs adminEast --authDomain example --authPassword "*" --addPoolAssociation
--entitlementName "Agent Sales" --poolId "Sales A"
lmvutil --authAs adminEast --authDomain example --authPassword "*" --addPoolAssociation
--entitlementName "Agent Sales" --poolId "Sales B"
n
To add the pools in the first Central region pod to the Agents Sales global entitlement, the View
administrator runs the following commands on central1.example.
lmvutil --authAs adminCentral --authDomain example --authPassword "*" --
addPoolAssociation --entitlementName "Agent Sales" --poolId "Sales A"
lmvutil --authAs adminCentral --authDomain example --authPassword "*" --
addPoolAssociation --entitlementName "Agent Sales" --poolId "Sales B"
n
To add the pools in the second Central region pod to the Agent Sales global entitlement, the View
administrator runs the following commands on central6.example.
lmvutil --authAs adminCentral --authDomain example --authPassword "*" --
addPoolAssociation --entitlementName "Agent Sales" --poolId "Sales A"
lmvutil --authAs adminCentral --authDomain example --authPassword "*" --
addPoolAssociation --entitlementName "Agent Sales" --poolId "Sales B"
3
The View administrator runs the lmvutil command with the --addGroupEntitlement option to add
the Sales Agents group to the Agent Sales global entitlement.
The Sales Agent group is defined in Active Directory and contains all sales agent users. Adding the
Sales Agent group to the Agent Sales global entitlement enables sales agents to access the Sales A and
Sales B desktop pools on the pods in the Eastern and Central regions.
Chapter 3 Setting Up a Cloud Pod Architecture Environment
VMware, Inc. 27