RDS 2022 session host remains in collection after reboot, but does not accept connections

Question

Hi all,

RDS farm of 6 collections and 30 session hosts - everything in the farm in server 2022.

In one collection, the session hosts are rebooted each night - and when they come back up - they all appear to be be fine.... however, when users start connecting the next morning, one or more of the session hosts wont get any new connections.... even though it is not in drain mode.

Putting the session host into drain mode and back out again "fixes" this... - however, its a right pain having to check this every morning - and am looking to solve this.

It does not appear to happen on other collections - which all have identically configured session hosts. (they are all built by an SCCM task sequence - so outside of the name, they are identical in every way)

Answer 1

You may consider disabling other Session Hosts during scheduled times to access a specific SH and observe the login process. Alternatively, you can remove it from your collection and connect directly via MSTSC. If load balancing directs users to a different session host, there may be an issue with the specific SH.

Should you manage to connect after removing it from your collection, it likely indicates a load balancing problem; check your connection broker.

If the connection still fails, further investigation of your session host is required.

Please open your Event Viewer and review the System/Application logs, as well as all Remote Desktop/Terminal Services logs.