Share via

We are unable to see collection group access in RDS-Pool server

Anonymous
2024-06-03T23:01:59+00:00

Hello Team,

The collection disappeared in the RDS connection broker server (Windows server 2016).
We verified that the permissions are good. Also the RDS servers are already in the groups “Remote server endpoint” and we are part of the domain admins.
Actually its working fine only for 2 users. I have mapped the same groups of those 2users, but still no luck.
Also some times the the servers are going to False mode (drain mode) and we couldn’t able to find the logs.
We are looking for a script to automate the drain mode should go into the True mode (searching for the script).

Can you guide us in correct directions on all these issues?

Windows for business | Windows Server | User experience | Remote desktop services and terminal services

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-06-04T02:18:09+00:00

    Hello,

    Here are some steps you can take to troubleshoot the issue with the RDS connection broker server where the collection has disappeared:

    1. Ensure that the collection configuration is still intact. You can use PowerShell Get-RDSessionCollection (RemoteDesktop) | Microsoft Learn to check this. Verify that the collection you are missing is listed. If it's not listed, it might have been deleted or corrupted.
    2. Service Verification: Confirm that all RDS services are running properly on the server, including the RD Connection Broker service.
    3. Event Logs: Check the server's event logs for any errors or warnings related to RDS or the RD Connection Broker service.Remote Desktop Services Events (by Role Service) in Windows Server 2008 R2 | Microsoft Learn
    4. Server Manager: Verify that all servers involved in the RDS deployment are added to the list of servers in Server Manager, as missing servers can cause visibility issues in the RDS Manager.
    5. Server Pools: Look into the server pool configuration to ensure that all hosts are correctly added to the pool and that there are no discrepancies causing the issue.
    6. Check DNS and Network Configuration: Ensure that all RDS servers can communicate with each other properly. Check DNS settings, firewall rules, and network configurations to ensure there are no connectivity issues.
    7. Validate connectivity between the RDS Connection Broker and the database server. Use a tool like ping or Test-NetConnection in PowerShell to ensure basic network connectivity to the database server. Confirm that the required SQL Server port (default is 1433 for SQL Server) is open on the firewall.

    Best Regards,

    Karlie

    0 comments