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

Ben Wosjke 136

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)

Karlie Weng 16,096 Reputation points Microsoft Vendor

2024-07-18T07:11:52.44+00:00

Hi, could you provide the error message that appears when a user cannot log in? Or specify which process is not responding?
Ben Wosjke 136 Reputation points

2024-07-18T22:19:48.22+00:00

? Huh ?

It happens to seemingly random session hosts within a collection... the users can still logon to other members in the farm - certain hosts just don't get any logons.. therefore there is no error message.

There is also no process that isn't responding, again, certain members of the farm don't take new connections - where-as others will.

Maybe don't comment on stuff you haven't run into or at least have significant experience with the product.

Share via

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