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
3 Select the global entitlement and connect to a desktop.
A desktop should launch successfully. Exactly which desktop launches depends on the individual
configuration of the global entitlement, pods, and desktop pools. As a general rule, the Cloud Pod
Architecture feature attempts to allocate a desktop from the pod to which you are connected.
What to do next
If the global entitlement does not appear when you connect to the View Connection Server instance, use the
lmvutil command with the --listUserEntitlements, --listGroupEntitlements, and
--listAssociatedPools options to verify that the entitlement is configured correctly. If the global
entitlement appears but the desktop does not launch, all desktop pools might be fully assigned to other
users.
Sample Scenario: Setting Up a Basic Cloud Pod Architecture
Environment
This sample scenario demonstrates how the Cloud Pod Architecture feature can solve a real-world problem.
It includes step-by-step instructions that you can follow to complete a Cloud Pod Architecture
configuration.
In this scenario, a health insurance company has a mobile sales force that operates across two regions, the
Central region and the Eastern region. Sales agents use mobile devices to present insurance policy quotes to
customers and customers view and sign digital documents.
Rather than store customer data on their mobile devices, sales agents use standardized View floating
desktops. Access to customer data is kept secure in the health insurance company's datacenters.
The health insurance company has two datacenters, one in each region. Occasional capacity problems cause
sales agents to look for available desktops in a non-local datacenter, and WAN latency problems sometimes
occur. If sales agents disconnect from desktops but leave their sessions logged in, they must remember
which datacenter hosted their sessions to reconnect to their desktops.
To solve these problems, the health insurance company designs a Cloud Pod Architecture topology,
initializes the Cloud Pod Architecture feature, joins its existing pods to the pod federation, creates sites for
each of its datacenters, entitles its sales agents to all of its desktop pools, and implements a single View URL.
Administering View Cloud Pod Architecture
24 VMware, Inc.