Hello,
we have the following RDS environment:
2 x RDS Broker (Server 2019)
1 x RDS Gateway (Server 2016)
1 x Collection with 3 Server Windows 2016
1 x Collection with 3 Servers Windows 2019
After rebooting a server from the 2019 collection, it randomly fails to join the farm. The issue does not seem to occur on the 2016 collection.
If everything works fine, we can see the following event on one of the broker servers:
Source: TerminalServices-SessionBroker, Evend ID:776“RD Connection Broker successfully added an RD Session Host Server Server1.xxx.intranet to Farm XXX.”
But sometimes there’s no event logged for the server. To make the server work again we have found a workaround which is to not allow/allow new connections from the RDS broker.
After that we can see the following Events on the session hosts:
Source: TerminalServices-SessionBroker-Client, Event ID: 1280“Remote Desktop Services failed to join the Connection Broker on server Broker1.xxx.intranet;Broker2.xxx.intranet
Error: Current async message was dropped by async dispatcher, because there is a new message which will override the current one.”
Source: TerminalServices-SessionBroker-Client, Event ID: 1281Remote
Desktop Services successfully joined a farm on the Connection Broker server Broker1.xxx.intranet;Broker2.xxx.intranet
Our 2019 Terminalservers have been cloned from a server which was already member of an existing RDS deployment. Not sure if this might help finding the issue.
Regards,
Philipp
Philipp Mair