Forum Discussion
Microsoft[Feedback Requested] - Changes to the subscription logic for the Windows Desktop client (MSRDC)
Thanks everyone for the feedback on this. The June release is now available with the updated subscription logic. Closing this post.
Tried it out and unfortunately it only picked up my Spring 2020 Workspaces and had the Workspace available for the Fall 2019 Tenant 😞
James
MicrosoftJamesatighe Does your user account have resources on both Fall and Spring deployments?
If so, it found the Spring resources properly since we look there first. You should then automatically see the Fall resources if we were able to get an AAD token for Fall. Otherwise, you should see a placeholder Workspace on the Connection Center letting you know we found additional resources with a Subscribe button so we can get an AAD token for the other deployment.
Is that not what you are seeing?
- Hi David,
Maybe I misunderstood. I thought the change was to make the client pick up both Spring 2020 and Fall 2019 without having to subscribe twice?
I have Multiple HostPools in both Spring and Fall for my user.
When subscribing I only see the Spring resources and have to subscribe again to see the fall. This was exactly how it worked for me before this version.
Kind Regards
James- DavidBelanger
Jamesatighe The client will try to get the resources for both, Spring and Fall. It will acquire an AAD token for Spring update by prompting for an account. Once it's done subscribing, it will try to silently acquire an AAD token for Fall for the same user. If it's able to do so, it will automatically add the Fall resources. If it's unable to do, for example BYOD device where the user hasn't allowed the AAD token to be shared with other apps, it will add a placeholder Workspace on the Connection Center letting the user know they have more resources. Clicking Subscribe on the placeholder Workspace will prompt the user for their account and add the remaining resources.