This message was deleted.
# _general
s
This message was deleted.
k
On each collection, you have to configure which user/users or group/group have access. which user/group is configured on the old collection and which user/group is configured on the new collection?
a
i have done this already. I then test a user with mstsc to the connection broker hostname and it always redirects to collection 1 although it has only access to collection 2. IF i go from web access then the rdp file is correct and is already prepared for login to collection 2
k
My guess is that when you connect via mstsc it always connects to the first collection configured, if the user has access to that collection
a
yes im also think the same
maybe i will get the rdp file which the web interface creates and use this according to my needs
k
Using the RD Web Access/HTML/RemoteApp and Desktop Connection is the "correct" way to access RDS, as the RD Connection Broker enumerates all collections
Yes, that might also be a solution. Domain joined computers might also use the RemoteApp and Desktop Connections client
b
Anestis, create a new collection of type "personal unmanaged", you can then assign an individual user to each machine. This is how we emulate vdi with MS RDS technology in Hoster/Cloud scenario where tenant does not have access to the hypervisor. DM me for code snippets, or you can find them on MS docs page.
👍 1