Administering View Cloud Pod Architecture
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
- Creating Cloud Pod Architecture Sites
- Entitling Users and Groups in the Pod Federation
- Finding and Allocating Desktops in the Pod Federation
- Global Entitlement Example
- Cloud Pod Architecture Topology Limits
- Cloud Pod Architecture Port Requirements
- Security Considerations for Cloud Pod Architecture Topologies
- Setting Up a 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 the Pod Federation
- Determine the Effective Home Site for a User
- Add a Pod to a Site
- Modifying Global Entitlements
- Remove a Home Site Association
- Remove a Pod From the Pod Federation
- Uninitialize the Cloud Pod Architecture Feature
- lmvutil Command Reference
- Index
The View administrator adds the Sales Agents group to the 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.
2 To add the desktop pools in East Pod 1 to the global entitlement, the View administrator logs in to the
View Administrator user interface for a View Connection Server instance in East Pod 1, selects Catalog
> Global Entitlements, double-clicks the global entitlement, clicks Add on the Local Pools tab, selects
the desktop pools to add, and clicks Add.
3 To add the desktop pools in Central Pod 1 to the global entitlement, the View administrator logs in to
the View Administrator user interface for a View Connection Server instance in Central Pod 1, selects
Catalog > Global Entitlements, double-clicks the global entitlement, clicks Add on the Local Pools tab,
selects the desktop pools to add, and clicks Add.
4 To add the desktop pools in Central Pod 2 to the global entitlement, the View administrator logs in to
the View Administrator user interface for a View Connection Server instance in Central Pod 2, selects
Catalog > Global Entitlements, double-clicks the global entitlement, clicks Add on the Local Pools tab,
selects the desktop pools to add, and clicks Add.
Creating a View URL for the Example Configuration
The insurance company uses a single View URL and employs a DNS service to resolve sales.example to the
nearest pod in the nearest data center. With this arrangement, sales agents do not need to remember
different URLs for each pod and are always directed to the nearest data center, regardless of where they are
located.
When a sales agent connects to the View URL in Horizon Client, the Agent Sales global entitlement appears
on the list of available desktop pools. When a sales agent selects the global entitlement, the Cloud Pod
Architecture feature delivers the nearest available desktop in the pod federation. If all of the desktops in the
local data center are in use, the Cloud Pod Architecture feature selects a desktop from the other data center.
If a sales agent leaves a desktop session logged in, the Cloud Pod Architecture feature returns the sales
agent to that desktop, even if the sales agent has since traveled to a different region.
Chapter 3 Setting Up a Cloud Pod Architecture Environment
VMware, Inc. 25