Create a Host Pool

Nerdio Manager allows you to create host pools at the Account level.

To create a host pool:

1. At the Account level, navigate to AVD > Host Pools.

2. Select Add host pool.

3. Enter the following information:

   Note: For several of the required parameters, you may filter the available choices by using the Resource Selection Rules. For example, you may filter the VM Size or OS Disk choices for Intel RAM-optimized VMs only. See Resource Selection Rules Management for details.

   

   • Name: Type the name of the host pool.

   • Description: Type the host pool's description.

   • Desktop Experience: From the drop-down list, select the desktop experience.

     Note:

     • Multi user desktop (pooled): This is the full desktop experience. Users are not assigned to individual session hosts and are placed on a host based on its load. Multiple users are pooled together on a group of hosts.

     • Multi user RemoteApp (pooled): This is only published applications, not a full desktop experience. Published RemoteApps are visible to users as native apps running on their local computer. The RemoteApps are provided by a collection (pool) of session hosts.

     • Single user desktop (pooled): This is the full desktop experience. Users are placed on individual desktop VMs (one user per session host) and a preconfigured number of spare(available) desktops is maintained.

     • Single user desktop (personal): This is a personal (persistent) full desktop experience. A dedicated session host VM is assigned to each user.

   • Directory: From the drop-down list, select the directory.

     Note: The default option is the global default Nerdio Manager AD configuration. To use a custom configuration for the host pool, select the Custom option.

   • FSLogix: From the drop-down list, select the FSLogix configuration profile to be used when creating or re-imaging hosts in this host pool.

     Note: There are several limitations, including limited support for FSLogix. Review Microsoft's MFA requirements for Entra ID joined VMs. Learn more.

   • Workspace: From the drop-down list, select the workspace, which is the container for host pools and session hosts that provides desktops and RemoteApps to users.

   • Name Prefix: Type the name prefix to be used when creating multiple session hosts.

     Note: The name prefix limit is 10 valid, Windows computer name characters. When using a prefix, the system automatically appends “-xxxx” (with four random characters) to the name prefix to make a unique name.

   • Network: From the drop-down list, select the network that the VMs are connected to.

     Note: The selected network also determines the Azure region of the VM.

   • Desktop Image: From the drop-down list, select the desktop image that is used as the golden image for newly created session hosts.

   • VM Size: From the drop-down, select the VM disk size and type for newly created session hosts.

     Note: If any VM size is not available for a subscription or region, it doesn't appear in the list. At times, even if a VM size is available in a specific Azure region, it cannot be used due to the subscription having restrictions on a particular size. In such cases, we show the VM size in the drop-down list, but don't allow users to select it (the size is disabled).

   • OS Disk: From the drop-down list, select the OS Disk type and size for newly created session hosts.

     Note: This must be equal to or larger than the size of the Desktop Image selected above. Using Standard HDD (S-type) is not recommended. Premium SSD provides best performance.

   • Resource Group: From the drop-down list, select the resource group to contain the VMs.

   • Quick Assign: From the drop-down list, select the users or groups to pre-assign to newly created desktops.

     Note: The number of users specified cannot exceed the number of hosts being added for Single User desktops. User assignment can be modified after the host pool is created.

   • Use Trusted Launch: Select this option to use trusted launch.

     Note:

     • Azure offers trusted launch as a seamless way to improve the security of Gen2 VMs. Trusted launch protects against advanced and persistent attack techniques. Trusted launch is composed of several, coordinated infrastructure technologies that can be enabled independently. Each technology provides another layer of defense against sophisticated threats. See this Microsoft document to learn more about trusted launch.

     • The selected Desktop Image must be Gen2.

4. Once you have entered the desired information, select OK.