7.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
- Creating Cloud Pod Architecture Sites
- Entitling Users and Groups in the Pod Federation
- Finding and Allocating Desktops and Applications 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
- Initialize the Cloud Pod Architecture Feature
- Join a Pod to the Pod Federation
- Create and Configure a Global Entitlement
- Create and Configure a Site
- Assign a Home Site to a User or Group
- Create a Home Site Override
- Test a Cloud Pod Architecture Configuration
- Example: Setting Up a Basic Cloud Pod Architecture Configuration
- Managing a Cloud Pod Architecture Environment
- View a Cloud Pod Architecture Configuration
- View Pod Federation Health in View Administrator
- View Desktop and Application Sessions in the Pod Federation
- Add a Pod to a Site
- Modifying Global Entitlements
- Managing Home Site Assignments
- Remove a Pod From the Pod Federation
- Uninitialize the Cloud Pod Architecture Feature
- lmvutil Command Reference
- lmvutil Command Use
- Initializing the Cloud Pod Architecture Feature
- Disabling the Cloud Pod Architecture Feature
- Managing Pod Federations
- Managing Sites
- Managing Global Entitlements
- Managing Home Sites
- Viewing a Cloud Pod Architecture Configuration
- Listing Global Entitlements
- Listing the Pools in a Global Entitlement
- Listing the Users or Groups in a Global Entitlement
- Listing the Home Sites for a User or Group
- Listing the Effective Home Site for a User
- Listing Dedicated Desktop Pool Assignments
- Listing the Pods or Sites in a Cloud Pod Architecture Topology
- Managing SSL Certificates
- Index
Understanding the Scope Policy
When you create a global desktop entitlement or global application entitlement, you must specify its scope
policy. The scope policy determines the scope of the search when View looks for desktops or applications to
satisfy a request from the global entitlement.
You can set the scope policy so that View searches only on the pod to which the user is connected, only on
pods within the same site as the user's pod, or across all pods in the pod federation.
For global desktop entitlements that contain dedicated pools, the scope policy affects where View looks for
desktops the first time a user requests a dedicated desktop. After View allocates a dedicated desktop, it
returns the user directly to the same desktop.
Using Home Sites
A home site is a relationship between a user or group and a Cloud Pod Architecture site. With home sites,
View begins searching for desktops and applications from a specific site rather than searching for desktops
and applications based on the user's current location.
If the home site is unavailable or does not have resources to satisfy the user's request, View continues
searching other sites according to the scope policy set for the global entitlement.
For global desktop entitlements that contain dedicated pools, the home site affects where View looks for
desktops the first time a user requests a dedicated desktop. After View allocates a dedicated desktop, it
returns the user directly to the same desktop.
The Cloud Pod Architecture feature includes the following types of home site assignments.
Global home site
A home site that is assigned to a user or group.
If a user who has a home site belongs to a group that is associated with a
different home site, the home site associated with the user takes precedence
over the group home site assignment.
Global homes sites are useful for controlling where roaming users receive
desktops and applications. For example, if a user has a home site in New
York but is visiting London, View begins looking in the New York site to
satisfy the user's desktop request rather than allocating a desktop closer to
the user. Global home site assignments apply for all global entitlements.
IMPORTANT Global entitlements do not recognize home sites by default. To
make a global entitlement use home sites, you must select the Use home site
option when you create or modify the global entitlement.
Per-global-entitlement
home site (home site
override)
A home site that is associated with a global entitlement.
Per-global-entitlement home sites override global home site assignments. For
this reason, per-global-entitlement home sites are also referred to as home
site overrides.
For example, if a user who has a home site in New York accesses a global
entitlement that associates that user with the London home site, View begins
looking in the London site to satisfy the user's application request rather than
allocating an application from the New York site.
Configuring home sites is optional. If a user does not have a home site, View searches for and allocates
desktops and applications as described in “Finding and Allocating Desktops and Applications in the Pod
Federation,” on page 10.
Chapter 2 Designing a Cloud Pod Architecture Topology
VMware, Inc. 11