Before you begin to configure the Cloud Pod Architecture feature, you must make decisions about your Cloud Pod Architecture topology. Cloud Pod Architecture topologies can vary, depending on your goals, the needs of your users, and your existing Horizon implementation. If you are joining existing Horizon pods to a pod federation, your Cloud Pod Architecture topology is typically based on your existing network topology.
Creating Cloud Pod Architecture Sites Cloud Pod Architecture environment, a site is a collection of well-connected pods in the same physical location, typically in a single data center. The Cloud Pod Architecture feature treats pods in the same site equally. Entitling Users and Groups in the Pod Federation Horizon Console to create local entitlements. These local entitlements entitle users and groups to a specific desktop or application pool on a Connection Server instance. Finding and Allocating Desktops and Applications in the Pod Federation Cloud Pod Architecture environment use shared global entitlement and topology configuration information from the Global Data Layer to determine where to search for and how to allocate desktops and applications across the pod federation. Considerations for Unauthenticated Users Cloud Pod Architecture environment, you can entitle these unauthenticated users to applications across the pod federation by adding them to global application entitlements. Global Entitlement Example Implementing Connection Server Restrictions for Global Entitlements Implementing Client Restrictions for Global Entitlements Implementing the Session Pre-Launch Feature for Global Application Entitlements Horizon Client . The session pre-launch feature enables faster start times for frequently used published applications. Enabling Multi-Session Mode for Global Application Entitlements Enabling Session Collaboration for Global Desktop Entitlements Implementing Backup Global Entitlements Considerations for Mixed-Version Environments Cloud Pod Architecture environments are supported beginning with Horizon 7 version 7.4.Considerations for Workspace ONE Mode Workspace ONE mode for a Connection Server instance, Horizon Client users can be redirected to a Workspace ONE server to launch their entitlements. Considerations for VMware Cloud on AWS Cloud Pod Architecture to interconnect VMware Horizon on-premises and VMware Horizon pods on VMware Cloud on AWS . You can entitle users to virtual desktops and published applications on-premises and on VMware Cloud on AWS . Considerations for RDS Per-Device Client Access Licensing Cloud Pod Architecture Topology Limits Cloud Pod Architecture topology consists of two or more pods, which are linked together in a pod federation. Cloud Pod Architecture Port Requirements Cloud Pod Architecture feature to work. When you install Connection Server, the installation program can optionally configure the required firewall rules for you. These rules open the ports that are used by default. If you change the default ports after installation, or if your network has other firewalls, you must manually configure the Windows firewall. Security Considerations for Cloud Pod Architecture Horizon Console or lmvutil commands to configure and manage a Cloud Pod Architecture environment, you must have certain roles or privileges.
