> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/ras-admin-guide/parallels-ras-21-administrators-guide/rd-session-hosts/manage-rd-session-hosts/manage-host-pools-rd-session-hosts/add-host-pools-rd-session-hosts.md). # Add host pools (RD Session Hosts) ## **Creating a host pool** To create an RD Session Host host pool: 1. In the RAS console, navigate to **Farm** > \ > **RD Session HostsHost pools**. 2. Click **Tasks** > **Add** (or click the **\[+]** icon). 3. Select **Enable Host pool in site** to enable the host pool. Specify the name and the description for the new host pool. 4. Click **Next**. 5. On the **Provisioning** page, select whether this host pool will contain template-based or standalone hosts: * **Template**: (Template-based RD Session Hosts only) Hosts will be created dynamically from a template. You will need to create or select an existing template in the next step or later. Choosing **Template** as the provisioning type ensures a homogeneous host pool, which is recommended to provide consistent user experience across the host pool. For more information about creating template-based RD Session Hosts, see section [**Add a template-based RD Session Host**](/landing/ras-admin-guide/parallels-ras-21-administrators-guide/rd-session-hosts/add-a-template-based-rd-session-host.md). * **Standalone**: (Template-based and standalone RD Session Hosts) Select one or more hosts that already exist. You'll be able to do it in the next step or you can do it later. Prior to adding hosts to host pools, ensure that hosts are domain joined and have network access to the domain environment. Note that the Standalone provisioning is considered "unmanaged" as it lacks some of the functionality, such as Autoscaling. 6. Click **Next**. 7. Depending on the selection made on the **Provisioning** page (above), do one of the following * **Standalone**: Select one or more hosts from the list to be included in the host pool (you can also add hosts to the pool later). * **Template**: Select a template from the list or click **Create new** to create a new template and specify the template settings. **Versions**: If you selected an existing template, select one of its versions. **Enable autoscale**: (Multi-session hosts) Enable and configure autoscale. 8. Click **Next**. 9. (Templates only) On the **Provisioning** page, specify the following options: * **Template name**: Choose and type a template name. * **Host name**: A pattern to use when naming new hosts. * **Number of hosts deployed on wizard completion**: The number of hosts to deploy once the template is created. Please keep in mind that this will take some time because the hosts will be created one at a time. * **Host state after the preparation**: Select the power state that should be applied to a host after it is prepared. Choose from **Powered on**, **Powered off**, or **Suspended**. Note that when the power state is set to **Power off** or **Suspended**, the number of running (fully ready and waiting for incoming connections) hosts is controlled by the **Keep available buffer** setting (see above). For example, let's say the **Maximum hosts** value is set at 200, the number of guest hosts deployed on wizard completion is 100, and the power state after preparation is **Powered off**. The result of such a configuration will be 100 clones deployed and powered off. * **Maximum hosts**: Specify the maximum number of hosts that can be created from this template. * (Only for templates created from VMware vCenter instances) Select one of the following: * If you want to create all hosts in the datastore that contains the template, select **Create hosts in the primary datastore**. * If you want to create hosts in several datastores, select **Create hosts in specific datastores**. If you select this option, you will be prompted to select the datastores in the **Datastores** list on the next page. * (Only for templates created from AWS instances) **Virtual networks**: Select Availability Zones for the host pool. Choose from **Use the subnet associated with the template** and **Use specific subnets available in the VPC**. If you select **Use specific subnets available in the VPC**, then after clicking **Next** you can manaully select one or several Availability Zones. * Autoscale settings: Configure autoscale settings as described in [**Manage host pools (RD Session Hosts)**](/landing/ras-admin-guide/parallels-ras-21-administrators-guide/rd-session-hosts/manage-rd-session-hosts/manage-host-pools-rd-session-hosts.md). 10. Click **Next**. 11. On the **Specifications** page, override settings that are defined at the template level. * To override the Organizational Unit in Active Directory where hosts are joined, select **Override Organizational Unit specified in template properties.** In the target OU field, provide the distinguished name of the Organizational Unit by using the browse (…) button or entering it manually. * (Microsoft Azure only) To override the High availability settings, select **Override the high availability settings specified in template properties.** Select an availability option which can be ‘no infrastructure redundancy required’, ‘availability set', or 'availability zone’. When 'availability zone’ is selected, specify the zone where hosts should be deployed. Note that High availability settings cannot be changed after the host pool is created. * (Microsoft Azure only) To override the host size, select the **Overwrite the size specified in template properties** option and choose the desired size from the drop-down list. The selected size will only be used by this host pool. Other host pools using the same template will be unaffected. Note that available sizes may depend on the location, size, and power state of the host pool members and the template. Also note that overwriting the size requires a host reboot. * (Nutanix only) To overide the Cluster settings, select **Override the cluster specified in Template Properties**. In the Custer field, provide the cluster name by using the browse (…) button or entering it manually. * (Nutanix only) To overide the Network settings, select **Override the network specified in Template Properties.** In the Network field, provide the network name by using the browse (…) button or entering it manually. 12. On the **User profile** page, you can select from **Do not manage by RAS** (user profiles will not be managed) or **FSlogix**. Microsoft FSLogix Profile Container allows to maintain user context in non-persistent environments, minimize sign-in times and provides native profile experience eliminating compatibility issues. For complete instructions, please see [**User profile**](/landing/ras-admin-guide/parallels-ras-21-administrators-guide/rd-session-hosts/manage-rd-session-hosts/manage-hosts-rd-session-hosts/view-and-modify-rd-session-host-properties/user-profile.md). 13. Click **Next**. 14. On the **Summary** page, review the template summary information. You can click the **Back** button to correct some of the information if needed. 15. Finally, click **Finish** to create the host pool and close the wizard. After you create a host pool and later publish resources from it, you can view the list of resources by right-clicking a host pool and choosing **Show published resources** (or click **Tasks** > **Show Published Resources**). For more information, see [**Viewing published resources hosted by RD Session Hosts**](/landing/ras-admin-guide/parallels-ras-21-administrators-guide/rd-session-hosts/viewing-published-resources.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.parallels.com/landing/ras-admin-guide/parallels-ras-21-administrators-guide/rd-session-hosts/manage-rd-session-hosts/manage-host-pools-rd-session-hosts/add-host-pools-rd-session-hosts.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.