Forum Discussion
PavithraT
Microsoft
May 14, 2020Resolved - Windows Client for Spring update 2020 - Subscription error
As part of the Spring update 2020, the Windows client was updated to discover feed for both Fall 2019 and Spring update environments, in that order. Since the Fall 2019 feed discovery requires consent, customers having only Spring update 2020 environments see a feed discovery failures. Workaround to get this to work is to temporarily consent to the Fall 2019 client and server apps (https://rdweb.wvd.microsoft.com/) and that should unblock feed discovery. Another option is to use the web client temporarily. The team is working on a fix and this should be out end of May.
The May update of the Windows Desktop client (MSRDC) has been released this morning. See the following post for updated guidance on using the new client to subscribe to Spring Update resources.
- PavithraT
Microsoft
crshovrd Are you talking about supporting email discovery based feeds OR subscribing to the Spring update feed manually? Both will work with the latest released client.
You dont need consent anymore.
To consent to Fall 2019, please follow this doc - https://docs.microsoft.com/en-us/azure/virtual-desktop/virtual-desktop-fall-2019/tenant-setup-azure-active-directory#grant-permissions-to-windows-virtual-desktop
- DavidBelanger
Microsoft
The May update of the Windows Desktop client (MSRDC) has been released this morning. See the following post for updated guidance on using the new client to subscribe to Spring Update resources.
- ablv1Copper Contributor
Hi PavithraT
We have the opposite problem. We have both Fall 2019 and Spring 2020 environments set up. However both clients (web and desktop) are only showing the Fall 2019 resources. Consent isn't an issue, because we're seeing the Fall 2019 resources.
How do we fix this?
Thanks
Adrian
- PavithraT
Microsoft
ablv1 For web, you need to use a different URL : https://docs.microsoft.com/en-us/azure/virtual-desktop/connect-web
For Windows, you will need to subscribe/ sign-in to view the Spring update/ ARM related resources. Once you have validated that the user can see the ARM resources, then we can see why your Windows client is not displaying it.
- ablv1Copper Contributor
Good morning PavithraT and thanks for the note.
With the link you provided, I was able to see the resources. With the Mac OS client, I was able to see the resources only if I specified the feed URL as described here.
How can I get this to work with email address? I can't find this documentation.
Thanks again
Adrian
- arexhajCopper Contributor
there is another option:
I kept getting an error with the Remtote Desktop, trying to connect to the new WVD (arm deployed) environment.
While checking the logs, I saw that the Remote Desktop apps fetches the registry key "DefaultFeedURL" located in [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSRDC\Policies].
I understood that the remote desktop app should redirect automatically to the new ARM Workspace, but that didn't work for me.That's why is set the key like this:
"DefaultFeedURL"="https://rdweb.wvd.microsoft.com/api/arm/feeddiscovery"
After restarting the Remote Desktop app, I could see the new workspace and could successfully login to my desktop.
I've described that here https://techcommunity.microsoft.com/t5/itops-talk-blog/windows-virtual-desktop-spring-update-enters-public-preview/bc-p/1390429#M861
- Cláudio RodriguesCopper Contributor
PavithraT Understood. But based on what you posted one has to assume the client was updated to deal with both Fall 2019 and Spring 2020 environments but that is not the case as for 2020 only environments it fails. Yes, giving consent does fix the issue for Windows 10 clients (all other clients work as expected).