Hi.
I'm implementing a new RDS farm with Windows Server 2019.
I have this servers deployed.
* 1 -RD Web Access
* 1 -RD Broker
* 3- RD Host Sessions
* 2 -Collections
* Collection cDEP1 ---> RDSH 1,2 --> Users/Group of DEP1
* Collection cDEP2 ---> RDSH 3 --> Users/Group of DEP2
I have 2 different departments in the company, DEP1 and DEP2
2 Department users have rights to logon vía RDP on 3 RDSH servers, I do this because in the future the RDSH hosts can be moved between Collections.
I want the users can connect to the services through RDP client and depends if the user or group belongs to DEP1 or DEP2 department, apply the collection cDEP1 or cDEP2 and then connect to his RDSH host.
I have tried this environment and I get two results.
* If I connect with browser https://RDWA/RDweb depends of the user I can see the published Apps and works fine.
* If I connect with the RDP client whit this configuration file and User belongs to DEP1, the connection opens on any of the servers. The same if I start session with user belongs to DEP2 group.
full address:s:RDCB01.DOM.NET
workspace id:s:RDCB01.DOM.net
use redirection server name:i:1
loadbalanceinfo:s:tsv://MS Terminal Services Plugin.1.cDEP1
loadbalanceinfo:s:tsv://MS Terminal Services Plugin.1.cDEP2
It seems that the broker does not redirect the connections based on the user's membership in the collection.
I don't know if this behavior is normal or this idea I have is not supported.
I would appreciate if someone could clarify something about this installation
Thanks