RDS Farm Will Not Connect or Load Balance when using RDP Client to Access

Question

I have been trying to set up an RD Farm using two Azure 2019 Datacenters. Both are session hosts, but one is also the Gateway Manager and Licensing Manager. This is mostly to reduce costs.

I've been experiencing an issue where even though I can get the RDWeb portal to work, I cannot get the direct log ins to work properly. This company uses both, and I need them both to work consistently. Although I can sometimes log in directly, I sometimes can't. The certificates are correctly configured and none of them are expired.

After one or two people log in, the licensing manager, DESPITE being activated and in working condition according to the diagnoser does not have any issues, does not apply a license to the machine and I can't log in. I've scoured the internet for resources and most of them say to add the Server to the Windows Authorization Server Group. However, I cannot seem to get permissions to add them even though I am an AAD DC Administrator. I've tried:

1) Opening the MMC as Admin.
2) Logging into the computer using /admin.
3) Adding the machines to a group and then trying to add that group to the Windows Authorization Server Group.
4) Adding the machines directly to the Window Authorization Server Group.
5) Trying to make myself a delegate of the Servers or the Windows Authorization Server Group.

And no dice. I'm open to any suggestions at this point because I am at my wits end with getting this RDFarm up and running and the client is pressuring me to get this done ASAP. Any suggestions?

Update: I've done some more sleuthing and looked at the application logs. It appears that the Terminal Services Session Broker hands off the connection to the 2nd RDServer, but that connection never actually makes it over to the second machine and is denied there. I've double checked the certificates and it does include all the correct parameters as far as I can tell. The second server has only session host and web access roles.

Answer 1

Hello there,

Do you have any logs are error message that we can look into for this behavior ?

You can set the default collection in the broker's registry. That way if a client attempts to connect without specifying a collection it will automatically be sent to the default collection.

To specify the default collection, please create the registry setting below:

HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\ClusterSettings

DefaultTsvUrl REG_SZ tsv://vmresource.1.<VDI pool ID>

To determine the correct value for DefaultTsvUrl please open RDWeb in a non-IE web browser and click on the icon for the collection you would like to be the default, then edit the downloaded rdp file with Notepad and copy the portion of the loadbalanceinfo setting that is similar to the above.

I hope this information helps. If you have any questions please let me know and I will be glad to help you out.

----------------------------------------------------------------------------------------------------------------

--If the reply is helpful, please Upvote and Accept it as an answer--