Windows Server 2019 RDS Connection Broker Issue

Question

Environment setup as follows:

1 X VM running domain controller, rds broker, rds licensing
4 X VM running rds session host

all VM's running Windows 2019 Std, fully updated
DNS round robin setup and users are able to login to the terminal server without any issues.
rds broker is load balancing the logins to different terminal servers

Issue arises, when a user disconnects from a session, when they try and log back in again, the rds broker is not connecting the user back to their disconnected session.

users are limited to one session only and all other settings in place.

Please advise how to fix.

Answer 1

Hi, 1.It is not recommended to install RDS Role on Domain controller expect RD licensing, since you don't want users to login on a domain controller and install applications.

2.Have you also configured the timeout of disconnected sessions? Log in RDCB --> Server Manager--> Collection properties(screenshot captured from RDS 2012)  

  Group policy: Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Services Session Host\Session Time Limits. Set time limit for disconnected sessions

---

Hope this helps and please help to accept as Answer if the response is useful.

Thanks, Jenny

Answer 2

Hi Jenny

the above are time out settings that have already been set, 6 hours for disconnected and 6 hours for idle and end session when time out expires

My issue is that uses are not being re-connected to their disconnected session, instead a new session is being created.

The RDS broker should be checking to see if the user is already connected and if so then re-connect to the session.

Answer 3

Hi,
Please try to lock the session before disconnecting and verify if the users were able to be redirected to previous session:
ctrl+alt+end -> lock, then close mstsc

---

Hope this helps and please help to accept as Answer if the response is useful.

Thanks,
Jenny

Answer 4

Hi,

1. I agree you should not install on a domain controller
2. Confirm that you have checked this setting in GPO which will restrict a user to a single session.
   
   3. The last item that you should be aware of is that there is a bug in RDS for session disconnect reason 0 that improperly updates the session data in the connection broker database. I am trying to get MS to review this bug and confirm. This is why it can take a long time to recover RDS if there is a large drop of users due to ISP's rerouting traffic in the middle of the day.