Start a discussion

145 views
4 replies

Remote Desktop Connection Broker stops responding

Now and then the Remote Desktop Connection Broker stops responding, and stops serving my VDI computers. Saying that there are no computers available in the pool.

If you look at the service "Remote Desktop Conncetion Broker" it is running but doesn't "answer" requests anymore. On top you are unable to stop the service.

The only solution is to manually force it to stop, by starting an (admin) comand prompt and stop it trough Taskkill tssdis.exe with the id

After that you can restart the "remote Desktop Connection Broker" service again, and all VDI computers are again available for use.

Windows Server 2019

Tested and tried several things but this thing gives me a headage for the past months.

 

Jo Lambrecht Jo Lambrecht
Published 07/19/2023 16:09
Add Comment
Mariette Knap

Hello Jo,

Yes, I have seen the same behavior but no errors or clues in the logs. I have no idea why this happens and the only 'fix' is to reboot the server.

replied 07/19/2023 16:59
Jo Lambrecht

Hi Mariette,

Rebooting is not neccesary, What i do is:

logon on to the remoteDesktop server.

Start taskmanager -> go to DETAILS and look for TSSDIS.EXE, take note of the PID

Then start the command prompt as adminitrator and stop the task

Taskkill /pid /f

(the service is now stopped)

Start services.msc  (Run -> services.msc)

Look for "Remote Desktop Connection Broker" and start the service

Voila, all connections are available again. (Without the need of rebooting)

replied 07/20/2023 06:49
Jo Lambrecht

Hi Mariette,

Any updates on this issue by any change?

 

 

replied 11/03/2023 16:15
Mariette Knap

I have no idea

replied 11/29/2023 14:43
Last Activity 11/29/2023 14:43