Supporting Virtual Desktops in Two Different Physical Locations: Enabling Nearest Location Session Start

ABD.

To enable users to connect to the nearest physical location when accessing virtual desktops via VMware Horizon View, the following three steps must be completed:

B. Initialize the Cloud Pod Federation: This step is required to enable the creation of a Cloud Pod Architecture, which is a grouping of multiple View pods connected together to enable global entitlements and access across multiple geographic locations. Cloud Pod Federation enables unified management and configuration across multiple View pods.

C. Configure Global Entitlements: Once the Cloud Pod Federation is established, global entitlements must be configured to allow users to access virtual desktops from any pod in the Cloud Pod Architecture. This allows users to access their virtual desktops from the nearest physical location, as well as ensuring high availability and load balancing.

A. Configure one View Pod spanning two sites: To achieve the desired functionality of connecting users to the location nearest to them, a single View Pod must be configured to span across the two physical locations. This enables the pod to automatically redirect users to the nearest available desktop and ensures that the user experience is optimized for performance.

Therefore, options B, C, and A are the correct steps that must be completed to enable the functionality that the customer requires.

Option D (Configure VMware User Environment Manager) is incorrect as it is not directly related to the requirement of connecting users to the nearest location, and Option E (Configure two View Pods) is also incorrect as it would not allow for the desired functionality of connecting users to the nearest physical location. Option F (Configure Microsoft SQL Server Always On High Availability) is also incorrect as it is not directly related to the Horizon View deployment.