Forum Discussion
[Feedback Requested] - Changes to the subscription logic for the Windows Desktop client (MSRDC)
- Jul 01, 2020
Thanks everyone for the feedback on this. The June release is now available with the updated subscription logic. Closing this post.
Thanks for this. Quick question. We have the following scenarios:
1. Desktop being used by end users are autologged in to the local computer. Previously we put a RDP icon on the desktop and users can login using their credentials to the RDS Server. With the workspace it seems the credentials are required for it to be added in the Workspace client - does the credentials being used to add workspace feed matter? Would any user just be able to use the workspace icon and login to their WVD environment?
2. Haven't tested this on PC - but on Mac if i connect to the workspace - I cannot again connect to that workspace using a different credentials as it shows me connected to that workspace already. Is there a way to start a second session with different credentials?
- DavidBelangerJun 10, 2020
Microsoft
Q1: Not by default. The AAD credentials used to go through the gateway are the same used to subscribe to the Workspace. When connection is launched, the AAD creds are used to determine the AD account of the user and temporarily add them to the list of allowed users on the session host so the AD credentials need to match. You might be able to test pre-adding all the users to the allowed Remote Desktop users list on the server and it might work but you'd have to test it out.
Q2: Our clients don't currently support subscribing to WVD with 2 different users at the same time. That is something we are investigating for a future release.