Considerations for Assignments in a Universal Broker Environment When a Pod Goes Offline

When working with end-user assignments in a Universal Broker environment, you may experience limited availability of resources in an assignment if one of its participating pods loses connectivity and goes offline.

You may encounter the following situations when working with end-user assignments in a Universal Broker environment.

Floating VDI Assignments

• If a floating VDI assignment includes desktops from multiple pods and one or more participating pods go offline, Universal Broker disregards the offline pods and only searches for desktops from the online pods to fulfill users' requests, provided that the requests do not exceed maximum capacity.
• If a participating pod in a floating VDI assignment goes offline and then comes back online later, the end user may see multiple connection sessions for that assignment across multiple pods. The multiple instances typically represent the earlier session established with the pod that went offline and a later session initiated with a different online pod to fulfill the user's request. When the user selects one of the sessions, the other session is automatically logged off.

Dedicated VDI Assignments

• If an end user has received a dedicated desktop from a dedicated VDI assignment and the pod containing that desktop goes offline, the user loses access to the desktop. The user regains access to the desktop only when the pod comes back online.
• If an end user has not received a dedicated desktop yet from the assignment and one or more participating pods go offline, Universal Broker disregards the offline pods and only searches for a desktop from an online pod to fulfill the user's request, provided that the request does not exceed maximum capacity.

RDSH Session Desktop and Applications Assignments

• If a pod participating in an RDSH assignment goes offline, you cannot access the assignment or any of the included session desktops in Horizon Universal Console. Although end users can still see the session desktops in the assignment, any attempt to open a connection session with a desktop will fail. The assignment and session desktops will become available again in the console and to end users when the pod comes back online.
• If an RDSH assignment includes applications from a participating pod that goes offline, you cannot access those particular applications in the console. Although end users can still see remote applications from the offline pod, any attempt to start a session with these applications will fail. Applications in the assignment from pods other than the offline pod remain available in the console and to end users. Applications from the offline pod will become available again in the console and to end users when the pod comes back online.