In a Remote Desktop Services environment where you make use of RD Connection Broker, this blogpost about its polling intervals might come in handy.
To keep track of the status of RD Session Hosts Servers, the RD Connection Broker keeps track of whether the connections that it redirects to the RD Session Host servers in the farm go through successfully. If such a redirection fails, then there might be a problem with the RD Session Host server (or i.e. the network). Therefore, 1 minute after the initial redirection request, the RD Connection Broker starts pinging the RD Session Host server that didn’t respond. If the RD Session Host server does not respond to a specified number of pings (by default 3, with a interval of 10 seconds) then the RD Connection Broker will remove that RD Session Host server from the database.
To keep track of the status of RD Session Hosts Servers, the RD Connection Broker keeps track of whether the connections that it redirects to the RD Session Host servers in the farm go through successfully. If such a redirection fails, then there might be a problem with the RD Session Host server (or i.e. the network). Therefore, 1 minute after the initial redirection request, the RD Connection Broker starts pinging the RD Session Host server that didn’t respond. If the RD Session Host server does not respond to a specified number of pings (by default 3, with a interval of 10 seconds) then the RD Connection Broker will remove that RD Session Host server from the database.
In the meantime, users that are trying to connect could end up not being able to. That raises the question, how long could it potentially take before the record of the RD Session Host in RD Connection broker database gets updated? You could end-up having to wait about two to three minutes from the time the RD Connection Broker attempted to redirect a connection to the unavailable RD Session Host before the RD Connection Broker will stop trying to redirect to that server. You will have the same issue when removing the RD Session host from the TS Session Directory Computers group because that won’t directly delete it from the RD Connection Broker database.
There is a way to speed up the process of bringing the database up to date by changing the intervals RD Connection Broker uses and here’s how:
Open the registry of the machine that holds the RD Connection Broker Role and open the following path:
HKLM/SYSTEM/CurrentControlSet/Services/Tssdis /Parameters
And there you’ll see the parameters to control the intervals and you will be able to change them!
And to re-add the RD Session Host server to the RD Connection Broker database, re-add the RD Session Host Server to the Session Broker Computers Group.
No comments:
Post a Comment