The environment was working except for one small issue, only 1 account was about to see Collections in the Server Manager (Fig. The following servers in this deployment are not part of the server pool: 1. ... / Under Microsoft / With 3 Comments; So for my first article I’m going to write about an issue I had with Microsoft Remote Desktop Services. 1). 2, I am able to reproduce the issue by removing the SRV-T-RDSH02 from the Active Directory, turning off the virtual machine and logging on using a different account than the DOMAIN\Administrator.
When opening the Server Manager to administer a server role topology, you receive the following error message: A Remote Desktop Services deployment does not exist in the server pool. This is due to confidentiality, I used the screenshots from my lab environment to reproduce this issue instead. 1, you can see I can see the Collections.The query should return something like the FQDN of your RDS servers (remember this is a snapshot from my lab environment, so your FQDN should be different)Double-click on the Close all windows till you only have the Windows Management Instrumentation Tester window open and select “Refresh or restart the Server Manager when you see the executed successfully window After doing these 13 steps I was able to see my Collections again from any admin account. It really sucked when we started seeing below message in the "Remote Desktop Services" in our RDCB Server Manager. I removed the server from the domain, removed the DNS record from round robin, delete the network object from AD. So for my first article I’m going to write about an issue I had with Microsoft Remote Desktop Services. On the Windows desktop, start Server Manager by clicking the Server Manager icon on the Windows taskbar. When trying to manage the RDS collection, we had an issue: The following Servers in this deployment are not part of the server pool. I know it is not the ideal and most likely a dirty way, but I was not able to reproduce it using the PowerShell command nor by removing the role using the Server Manager.
The following servers in this deployment are not part of the server pool. I just want to be able to access the collection settings.End-User Computing, application delivery and automation challenges and solutionsThe following servers in this deployment are not part of the server pool: On the Active Directory tab, select servers that are in the current domain. When opening the Server Manager to administer a server role topology, you receive the following error message: A Remote Desktop Services deployment does not exist in the server pool. [server_name] The servers must be added to the server pool. It might be confusing that I wrote about 4 RD Session Hosts and you only see 2 in the screenshots. The architect had already made the design and virtual machines, the RDS infrastructure had 1 RD Connection Broker which also was used as a RD Gateway and RD Web Access and 4 RD Session Hosts.After accepting the environment by the customer, the MSP who hired me decided they could do with 1 RD Session Host less to reduce costs. You should also be able to view the RDS topology in the Server Manager again. We couldn't manage the RDS users, my boss was mad at me, and it was a pretty sad day. The servers must be added to the server pool.
RDS error “A Remote Desktop Services deployment does not exist in the server pool”.RDS error “A Remote Desktop Services deployment does not exist in the server pool”.
When I log on using the DOMAIN\Administrator account as you can see in Fig. So, as you can see in Fig. The MSP still have access, but I don’t know their password to log in as them.Your guide is showing us to remove one server, but I don’t want to do this. Press Ctrl while selecting to select multiple servers. Then do either of the following. To create a deployment, run the Add Roles and Features Wizard and select the Remote Desktop Services installation option. The infrastructure used in my lab environment is 1 Domain Controller, 1 RD Connection Broker combined with RD Gateway and RD Web Access, 2 RD Session Hosts and 1 client. Let me give you a little background information before we dive into the actual issue. Then from the RDS management endpoint, import the RDS Powershell module by running the following cmdlet: Run the following cmdlets (depending on whether you have a session deployment or a virtual desktop deployment or both), in order to re-create the RDS deployment object: After the above cmdlets, you should be ready to add new RDS Session Host collections by running following cmdlet: In some cases, especially in older RDS versions, this error had been attributed to IPv6 protocol (should be disabled) and to PS Remoting not having been enabled on all RDS servers. In a Windows Server 2012 environment, you remove a server from the Server Manager "Servers" pool that was part of a Remote Desktop Services collection. To create a deployment, run the Add Roles and Features Wizard and select the Remote Desktop Services installation option.First of all ensure that the RDS server roles are deployed on the RDS servers of the topology and that the RDS CB highly available database is online. Then on the Manage menu, click Add Servers. To manage a deployment, you must add all the servers in the deployment to the server pool. Let me give you a little background information before we dive into the actual issue.