Resolved - Windows Client for Spring update 2020 - Subscription error

[PavithraT]

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.

[#2]

@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).

[#3]

@PavithraT 

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-...

[#4]

@arexhaj You are right that that is another option. If we change the design on an update, this might not be the best option, hence I did not list it here.

[#5]

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

[#6]

@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.

[#7]

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

[#8]

https://docs.microsoft.com/windows-server/remote/remote-desktop-services/rds-email-discovery

This is what we are pointing customers to, to setup email discovery.

[#9 · Accepted solution]

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.

https://techcommunity.microsoft.com/t5/windows-virtual-desktop/windows-client-for-spring-2020-update...

[#10]

@PavithraT So, we still can't subscribe on the Windows client via email address? Also, this doesn't appear to work at all from the macOS client. Any updates there?

Can you also describe the 2019 consent process?

[#11]

@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.

https://techcommunity.microsoft.com/t5/windows-virtual-desktop/feedback-requested-changes-to-the-sub...

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-...

[#12]

Thanks @PavithraT.

It seems the macOS client isn't able to resolve feeds via email address yet, or at least it's not in my experience. (v10.3.11)

Are you saying the Windows client does work? If so, I'll try it on my parallels VM.

Thanks!

[#13]

Thanks for your assistance so far. We now have a different problem:

In the Mac client, we can only see Spring 2020 resources, not Fall 2019. If we enter the feed URL manually (https://rdweb.wvd.microsoft.com) it says we're already subscribed.

Is this expected behaviour? How do we work around this? Thanks.

[#14]

Hi @PavithraT,

I was able to get the answer after opening a support case. The article that references the TXT record creation says to use a custom URL. This is incorrect. You must use the feed URL for the Spring 2020 version. 

_msradc IN TXT "spring feed url"

[#15]

"Thanks for your assistance so far. We now have a different problem:

In the Mac client, we can only see Spring 2020 resources, not Fall 2019. If we enter the feed URL manually (https://rdweb.wvd.microsoft.com) it says we're already subscribed.

Is this expected behaviour? How do we work around this? Thanks."

@ablv1, were you able to resolve this? I can only access one or the other. Curious if you were able to get around this.

Thanks,

Scott

[#16]

@Scott WindmillerI was actually using the wrong Remote Desktop client. There is one on the Microsoft Store and one that's a downloadable MSI. Only the downloadable MSI works with WVD resources. It has the same name too - very misleading.