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
For information about configuring the scope policy for a global entitlement, see “Create and Configure a
Global Entitlement,” on page 18.
Configuring Home Sites to Control Desktop Placement
A home site is the affinity between a user and a Cloud Pod Architecture site. With home sites, you can
ensure that a user always receives desktops from a specific site rather than receiving desktops based on the
user's current location. The Cloud Pod Architecture feature includes the following types of home site
assignments.
Global home site
You can assign home sites to users and groups. 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. For example, if a user has a home site in New York but is visiting
London, the Cloud Pod Architecture feature looks 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 specify the --fromHome
option when you create or modify the global entitlement.
Per-global-entitlement
home site
When you create a home site for a user or group, you can use the
--entitlementName option to specify a global entitlement. Per-global-
entitlement home sites override global home site assignments.
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, the Cloud
Pod Architecture feature looks in the London site to satisfy the user's
desktop request rather than allocating a desktop from the New York site.
When creating a per-global-entitlement home site, you must explicitly entitle all Active Directory user
groups that contain the home site users. If you have nested user groups, it is not sufficient to entitle only the
parent group. In this case, the parent group is explicitly entitled to the global entitlement, but the subgroups
are not, and the --createGroupHomeSite option fails.
Configuring home sites is optional. If a user does not have a home site, the Cloud Pod Architecture feature
searches for and allocates desktops as described in “Finding and Allocating Desktops in a Pod Federation,”
on page 10.
For information about creating home sites, see “Assign a Home Site to a User or Group,” on page 22. For
information about creating global entitlements, see “Create and Configure a Global Entitlement,” on
page 18.
Chapter 2 Designing a Cloud Pod Architecture Topology
VMware, Inc. 11