A Remote Desktop Service (RDS) deployment pool is a collection of RD Session Host servers that work together to provide remote desktop and application services to users. The RD Session Host servers in the pool can be load-balanced to optimize resource usage and improve performance. In this guide, we shall be discussing the steps to fix “The following servers in this deployment are not part of the deployment Pool: Create an RDS Session Host and Collection”. Please see how to Remove a Remote Desktop Service Collection, and Remote Desktop Services Setup on Windows Server.
When users connect to the deployment pool, they are redirected to an available RD Session Host server in the pool depending on the use case for deployment. The RD Connection Broker service manages the connection redirection and load balancing.
RDS Deployment Pool
The goal of this task is to add a VM to an RDS session host to the deployment pool and create a collection. The following steps below will help you in actualizing this task. This specific scenario will help achieve load balancing. Please refer to these interesting guides: Determine the Remote Desktop Client Version, How to enable or disable WMI Traffic Using Firewall UI, and Allow RDP access for non-administrators: Add User to Remote Desktop Users Group in Active Directory.
To create an RDS deployment pool, you will need to have a server running Windows Server with the Remote Desktop Services role installed. You will also need to have one or more RD Session Host servers available to include in the pool.
Why was the error “following servers in this deployment are not part of the deployment Pool, the servers must be added to the Server Pool” Prompted
Note: This is not an error, it prompts up when you have a heterogenous environment and want to create a new session host on the server. This ensures a lot of Remote Desktop Session Hosts are able to use a single Remote Desktop Licensing Server.
Kindly refer to these related guides: How to install RDS via Quick Start Deployment: Install, Publish, Update and Uninstall Remote Desktop Web Client, and How to fix the issue “The remote session was disconnected because there are no Remote Desktop License Servers available to provide a license”.
Fix the following servers in this deployment are not part of the deployment Pool
This step involves adding the “RDS Session Host Servers” to the Deployment Pool. You will need to launch the RDSWebAccess Server and add the list of server not available in the pool to it. In this way, you will RESOLVE the following error “The following servers in this deployment are not part of the deployment Pool, the servers must be added to the Server Pool”.
When the above error is resolved. You can now start off by creating your Remote Desktop Session host and Collection share afterwards. You may be interested in this “Event ID 5059: Application pool has been disabled or Changing identity user for IIS Application Pool“
Add a server to RDS Server Pool
Launch the server manager if not already opened. Then click on the Manage menu, then select Add Servers. Alternatively, you can right-click on “All Servers” and select Add Servers.
On the Active Directory tab, select servers that are in the current domain. Press Ctrl while selecting to select multiple servers.
Click the right-arrow button to move selected servers to the Selected list. Select the servers that you want to add. When you are finished adding servers, click OK.
Here are some related guides: Install and License Devolutions Remote Desktop Manager, RDP Users are unable to change Passwords, and How to Remove and Manage RDS Licenses.
Create an RDS Session Host
Connect to the Remote Desktop Web Access Server. Launch the Server Manager and click on Remote Desktop Services. It will connect to the RDS broker
To install the Remote Desktop Session Host role on the VM. Please see this guide. “How to install RDS via Quick Start Deployment: Install, Publish, Update and Uninstall Remote Desktop Web Client.
You just have to click ok Add RD Session Host Sers as shown in the image above. Follow through the rest steps.
You will be prompted to select the server to which you want to add the RD Session Host Server to. Follow through the prompts as it is very easy to complete. Take a look at these. Publish Remote Desktop Web Client: Install HTML 5 Web Client for Microsoft RDS Server. And also this Laps in Windows: How to Reset Directory Services Restore Mode (DSRM) Password.
Create Remote Desktop Services Collection
Note: A session collection holds the apps and desktops you want to make available to users. After you create the collection, publish it so users can access it.
Once the RDS Session Host server is added to the deployment and you have created a collection. Users can connect to the collection and access the remote desktops hosted on the new server that you added.
Users will be redirected to the RD Session Host server that has the lowest connection load in the collection. Which helps balance the workload across the RDS deployment. (That is if this is the use case for your environment). Please see How to add and remove RDS Collection
On the Setup RDS deployment, click on Create Collection. Once the collection is created, you can configure the session settings and other options.
I hope you found this blog post helpful on the following servers in this deployment are not part of the deployment Pool: Create an RDS Session Host and Collection. If you have any questions, please let me know in the comment session.
