Remote Desktop Connection Broker Client failed to redirect the user 1306
Windows 2016 RDS event 1306 Connection Broker Client failed to redirect the user... Error: NULL
Archived Forums Show Remote Desktop Services (Terminal Services)
Answers
All replies
3 Replies
· · ·
Thai Pepper OP
endtimesoldier
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
Maybe it doesn't like even numbers of processors. I've seen SQL Server fail to start for the opposite reason. Try giving it 3 instead of 2 0
· · ·
Poblano OP
Best Answer
OasisFan Dec 2, 2020 at 10:05 UTC
We sorted it. Seems that both the Session Host and Connection broker both need the same number of virtual CPUs. As soon as we set them both to use two vCPUs everything started working as normal. Odd, but one to remember for the future. 0
· · ·
Jalapeno OP
BB9193
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
We're running a 2012 R2 RDS environment and have a different number of cores per the CB and SH's. Unless this is something new to 2019, I'm not sure that is a requirement. A session host has much higher processing needs than a connection broker. Maybe this is a new requirement I've never heard before, but that does not sound correct to me. 0
This topic has been locked by an administrator and is no longer open for commenting. To continue this discussion, please ask a new question.
|