Pool groups allow you to entitle desktops and applications to any users or groups at any time. Using Horizon Cloud, you can create a single-session that includes pools from any provider, and add policies to them.
For information about how sessions are distributed in pool groups, refer to: Understanding How Sessions are Distributed within a Pool Group.
Procedure
-
From the Horizon Universal Console, select Pools Groups in the left menu.
-
Click Add > Single-Session.
-
On the Add Single-Session Pool Group page, enter a unique pool Name.
-
Add a Display Name and Description. A display name cannot exceed 64 characters and will be displayed to end users on Horizon clients. If left blank, the pool group name will be used as the display name by default.
-
Select a Pool Group type from Dedicated desktop for persistent VDI desktop experience mapped to a single end user, and Floating desktop for non-persistent VDI desktop experience that multiple users can access at different times that resets after each session.
-
In the Pools section, select a pool and click Next.
-
In the Policies section for the default client settings, select a Default protocol for end-user sessions.
You can slide the toggle to Allow users to select a protocol when they log in to a desktop.
-
Select the Preferred client type to launch entitlements in Horizon Client or a Browser.
-
For Dedicated desktop pool group, select the toggle to Show assigned machine name.
Show assigned machine name displays the hostname of the assigned machine instead of the pool group display name when you log in to Horizon Client.
If a user is assigned multiple machines in a pool group, the assigned machine name will always be shown. This feature is not available for Floating desktop pool groups.
-
In the Brokering sub-section, select Scope to search for available desktops on Any site, or Restrict to One Site.
-
In the Site connection affinity field, select the default site that end users will connect to, from Nearest Site and Home Site.
You can enable the Home site restriction toggle to restrict end users (or user groups) access to the entitlement only through the entitlement home site override, or through the user's home site if an override is not designated. If not selected, the nearest site is used.
-
If available, specify Direct connect only or Internal access only as needed.
-
In the SSO sub-section, optionally choose to enable SSO for the pool.
You must have completed the prerequisites to configure one of the SSO types that Horizon Cloud supports on the Horizon Edge Gateway, and fulfilled all of the requirements for that SSO type. If the prerequisites required by the configured SSO type are not met, the end user will be prompted to enter their credentials.
-
In the Power Management sub-section, for Dedicated Pool Group specify a threshold for Unused VMs, which is the minimum number of VMs to be kept powered on relative to the total VMs in a pool group at any point in time.
An unused VM is provisioned and powered on, but without a user logged in. This setting applies to each pool group in the entitlement unless a power management schedule is specified. Rather than power off the VMs in a single-session dedicated pool for Microsoft Azure and/or Amazon WorkSpaces Core, you can choose to hibernate them. Refer to: Hibernate Pools and Virtual Machines for more information.
-
In the Power off protect time field, add the number of minutes (from 1 to 60) a VM is protected from powering off after powering on due to a headroom error. The default is 30.
-
For the Floating Pool Group type, in the Power Management section, select between Occupancy based and Non-occupancy based for Power management type.
-
In the Occupancy based sub-section, select the threshold of virtual machine utilization for this entitlement at which a new virtual machine is spun up and drained respectively, from Optimized for performance, Balanced, and Optimized for cost in the Power management mode field.
With an Optimized for performance selection, a new virtual machine is spun up more quickly, making capacity readily available for a possible enhanced user experience.
With an Optimized for cost selection, the virtual machine will have a higher utilisation rate before spinning up a new virtual machine, which may help to minimize costs.
Note: Optimization parameters determine when to power-on new VMs and when to power-off existing powered-on VMs. The number in parenthesis describes the high occupancy threshold. For example, in the case of Optimized for performance (50), as soon as the VMs session occupancy reaches 50% the service start powering ON any spare powered-off VMs to ensure that existing users can keep using the VMs with optimal performance. You can optimize for cost, performance, or a combination of cost and performance. Samples are shown below:
- Optimized for performance (50): Automatically powers on spare VMs when session occupancy reaches 50%, ensuring optimal performance for users.
- Optimized for cost (80): Prioritizes cost efficiency, managing VM power states to minimize operational expenses.
- Balanced (66): A balanced approach between performance and cost considerations.
-
Add Minimum VMs for the minimum percentage of VMs to keep powered on relative to the total VMs in a pool group at any point in time.
This setting applies to each pool group in the entitlement unless a power management schedule is specified.
-
In the Power off protect time field, add the number of minutes (from 1 to 60) .
A VM is protected from powering off after powering on due to a headroom error. The default is 30.
-
For Non-occupancy based, specify a threshold for Unused VMs, which is the minimum number of VMs to be kept powered on relative to the total VMs in a pool group at any point in time.
An unused VM is a VM which is provisioned and powered on but without a user logged in. This setting applies to each pool group in the entitlement unless a power management schedule is specified.
-
In the Power off protect time field, add the number of minutes (from 1 to 60).
A VM is protected from powering off after powering on due to a headroom error. The default is 30.
-
You can also add a Power management schedule by clicking Add Schedule and adding information.
-
Your Timeout Handling options will vary based on whether your Virtual Machine (VM) is enabled for hibernation.
For Pool Groups that are Mixed with Hibernate and Non-hibernated Pools your options are limited to:
- Log Off (When a disconnected session is logged off, the session is lost.)
- No Action
For Pool Groups with Only Hibernate-Enabled Pools you can choose from the following timeout actions:
-
Log Off (When a disconnected session is logged off, the session is lost.)
-
Hibernate
-
No Action
If you select Log Off or Hibernate, you can specify a disconnect timeout duration or set it to immediate.
Important: If you choose to hibernate a single-session dedicated pool group, disconnected VMs are deallocated during inactivity. You are billed only for storage while the VM is hibernated. Users can resume their disconnected sessions from where they left off. App Volumes applications will be detached for the pool group when hibernate is enabled.
Default Timeout Values for all Types of Pools:
- Maximum session lifetime: 10080 minutes
- Idle session timeout: 10080 minutes
-
To select App Volumes applications, click Next or click Save & Close to complete pool group creation.
-
In the App Volumes Applications section, select any App Volumes applications that you want to make available on floating desktops. Click Next.
App Volumes Applications selected at pool group level will be delivered to floating VMs. This allocation is in addition to the allocation of App Volumes applications at entitlement (user/user group) level.
Note: To deliver an App Volumes application, the App Volumes agent must be installed on the pool image, and the application package must be available in the Horizon Edge. An application package must be available in particular region in order for it to be delivered to VM in the same region. The applications without captured packages are not available for selection. The checkbox is deactivated, and cannot be selected.
-
In the Application Details section, select a package for each application.
-
If a user is entitled to different packages of the same application through the pool group and through user or user group entitlements, select between Pool group and User/user group entitlement for Conflict Precedence to choose which package should be delivered.
-
Click Save.
-
Click Entitle Pool Group to entitle this pool group to users or user groups now, or click Finish to entitle it later.
Was deze pagina nuttig?