To provide end users with virtual desktops provisioned by cloud-connected Horizon pods, you create a multi-cloud assignment. The desktop pools in an assignment can span one or more cloud-connected Horizon pods that are in managed state.
- Change your cloud-connected Horizon pods to managed state. See Horizon Pods - Enabling a Cloud-Connected Pod for Multi-Cloud Assignments.
- Configure sites and home site associations for your brokering environment, as described in Configuring Sites for Universal Broker and Configuring Home Sites for Universal Broker.
- Using Horizon Console, configure desktop pools on the cloud-connected pods that you want to include in the assignment.
See Horizon Pods - Create a New Desktop Pool for Multi-Cloud Assignments and Horizon Pods - Prepare an Existing Desktop Pool for Use in a Multi-Cloud Assignment. Ensure that the desktop pools meet the configuration requirements for Universal Broker, as described in those topics.
- In the left pane of the console, click Assignments. If a submenu appears, select the option for VDI desktops.
- On the Assignments page, select New and select the submenu option for Horizon pods on a VMware SDDC platform.
The New Desktop Assignment wizard appears.
- On the Definition page, configure the required settings.
Setting Description Desktop Type Select one of the following:
Note: A specific user can receive at most one assigned desktop from a dedicated assignment brokered by Universal Broker, even if the assignment includes desktops from multiple pods.
- Floating: In a floating assignment, a user receives a different virtual machine with a different machine name with each login. With floating assignments, you can create desktops that shifts of users can use and that are sized based on the maximum number of concurrent users. For example, 300 users can use an assignment of 100 desktops if they work in shifts of 100 users at a time. With floating assignments, the user might see different host names for each desktop session.
- Dedicated: In a dedicated assignment, each virtual desktop gets mapped to a specific user. Each mapped user returns to the same desktop at every login. When a dedicated desktop is mapped to a specific user, that desktop is said to be assigned to that user.
This setting becomes read-only when you are editing an existing assignment.
Enter a user-friendly name for the assignment.
Entitled end users might see a form of this assignment name in the client they use to access their desktops. The name must contain only letters, hyphens, and numbers. Spaces are not allowed. The name cannot start with a non-alphabetic character.
Description Enter an optional description for the assignment. Select Pod(s) Select the check box next to each pod containing desktop pools that you want to add to the assignment. You can select multiple pods to create an assignment of desktop pools from different pods. Scope
To specify where the broker can search for desktops in response to a user's desktop request, select one of the following options:
- Any Site allows the broker to search for available desktops located in any configured geographic site.
- Restrict to One Site instructs the broker to search only for available desktops located in the user's default site, as specified by the Site Connection Affinity setting.
For an introduction to sites and desktop allocation, see Working with Sites in a Universal Broker Environment.
Site Connection Affinity
This setting specifies a certain geographic site as the default site for the user. When the user requests a desktop, the broker begins searching in the default site for available desktops. If no available desktops are found in the default site and no site restrictions are in effect, the broker continues searching for desktops beyond the default site.
Select one of the following options:
- Nearest Site specifies the nearest geographic site as the default site for the user.
- Home Site specifies the user's home site (or the home site of the group that includes the user) as the default site for that user.
Important: If you enable Home Site Restriction, the user (or the group that includes the user) must have a configured home site before they can access any desktops.
- To allow the user to access desktops beyond their configured home site, do not enable Home Site Restriction.
- To restrict the user to their configured home site when accessing desktops, enable Home Site Restriction.
After you configure the Definition settings, click Next to proceed to the next page of the wizard.
- On the Desktop page, specify the configuration properties and policies used to filter the desktop pools that can be added to the multi-cloud assignment.
For example, if you specify Windows 10 (64-bit) for Operating System and enable the Allow Users to Restart VMs policy, only desktop pools based on Windows 10 (64-bit) that have the Allow Users to Restart VMs policy enabled are available for inclusion in the assignment.
Option Description Operating System Specify the operating system of the desktop pools that you want to include in the assignment.Note: This setting becomes read-only when you are editing an existing assignment. Default Display Protocol Select the default display protocol of the desktop pools that you want to include in the assignment. Allow Users to Choose Protocol This policy filters desktop pools based on whether they allow users to select a display protocol other than the default.Note: This setting becomes read-only when you are editing an existing assignment. HTML Access
This policy filters desktop pools based on whether they allow users to connect to virtual desktops from a Web browser using the HMTL Access client. For more information about this feature, see the VMware Horizon HTML Access Documentation.
Allow Users to Restart VMs
This policy filters desktop pools based on whether they allow users to restart virtual machines with a graceful operating system restart. This policy applies only to an automated pool or a manual pool that contains vCenter Server virtual machines.Note: This setting becomes read-only when you are editing an existing assignment.
Clean Up Redundant Sessions
This policy specifies whether to close duplicate user sessions automatically.
Duplicate sessions can occur when a pod that contains a session goes offline, the user logs in again and starts another session, and the problem pod comes back online with the original session. When duplicate sessions occur, Horizon Client prompts the user to select a session.
This policy determines what happens to sessions that the user does not select. When this policy is deactivated, users must manually close their own extra sessions, either by logging off in Horizon Client or by launching the sessions and logging them off.
Select Desktop Pools
Select the check box next to each desktop pool that you want to add to the assignment. You can add multiple pools to a single assignment.
If you cannot find the desktop pool that you want in the list, verify the following:
- The desktop pool is not a manual pool. Manual desktop pools are not eligible to participate in multi-cloud assignments.
- The properties and policies of the desktop pool match the properties and policies that you specified for this multi-cloud assignment. For example, if you specified Windows 10 (64-bit) for Operating System and enabled the Allow Users to Restart VMs policy, the desktop pool must be based on Windows 10 (64-bit) and have the Allow Users to Restart VMs policy enabled.
- The desktop pool meets the configuration requirements for supporting Universal Broker, as described in Horizon Pods - Prepare an Existing Desktop Pool for Use in a Multi-Cloud Assignment.
After you configure the Desktop settings, click Next to proceed to the next page of the wizard.
- On the Users page, specify the users and user groups that you want to entitle to the assignment.
Option Description Domain
Specify the Active Directory domain in which the users and groups reside.Note: Only cloud-configured domains are available for selection.
Type the first few characters of the user or group name, and select the users or group of users from the list that appears.
Your selection is added to the Selected Users / User Groups list. You can use the Remove button to delete a selected user or group from the list.
Assign Home Site
Use this optional setting to configure a home site override for the selected user or group accessing this assignment. In this case, Universal Broker begins searching for available desktops in the override site instead of the user or group's configured home site.
For example, suppose that a user has a home site in San Francisco but you specify New York as the override site. When the user accesses the assignment, Universal Broker first searches for available desktops in New York instead of in San Francisco.Note: The Assign Home Site menu is available only if you selected Home Site for Site Connection Affinity on the Definition page of the wizard.
To specify a home site override, select the user or group and click Assign Home Site. The Assign Home Site menu displays all the available sites for pods participating in this assignment.
- To specify an override site as the default instead of the user or group's configured home site, select the override site in the menu.
- To remove the override site and use the user or group's configured home site instead, select Clear Home Site.
After you configure the Users settings, click Next to proceed to the next page of the wizard.
- Review the settings on the Summary page, and then click Finish.
Each desktop pool included in the assignment is now marked as Cloud Assigned in the Edit Pool wizard in Horizon Console. You cannot use Horizon Console to delete or deactivate a desktop pool marked as Cloud Assigned.