Sep 14 2020 11:06 PM
Sep 14 2020 11:06 PM
We have had a couple of users connecting to RemoteApps fine using the Windows Remote Desktop Client. It started throwing errors saying cannot refresh so we tried unsubscribing and resubscribing and this is where the fun starts:
Click subscribe > an immediate error pops up "We failed to subscribe since there is no Workspace at https://rdweb.wvd.microsoft.com/api/feeddiscovery/webfeeddiscovery.aspx:
Note that the url (I believe) is the non ARM classic URL. We have never deployed using this.
The problem persists even when we clear personal data (from the about tab) and uninstall and reinstall.
If we click Subscribe with url > does not recognise the email address (even though we have email discovery turned on and the user accounts are fine as they worked yesterday). Add in the ARM subscribe URL and it is not recognised, the Confirm button is not enabled so we can do nothing.
Clearly some strange bug with the client.
Any ideas how I can get round this?
Oct 01 2020 09:29 AM
Dec 03 2020 06:09 AM
Dec 04 2020 03:11 AM
@clang318 Afraid not. We never found a resolution to this.
Dec 07 2020 06:37 AM
Dec 07 2020 10:05 AM
Dec 08 2020 05:09 AM
@Soo Kuan Teo can you provide a URL or instructions to "file a feedback hub feedback with category Apps/Remote Desktop" I' don't know what you are talking about.
Dec 08 2020 10:32 AM
Make sure to do this from the client device where the user ran into issue. Alternatively, can you send the UPN of the user with this issue and a UTC timestamp (if repro no longer happens, otherwise, UPN should suffice).
Dec 08 2020 02:03 PM
Dec 08 2020 07:47 PMSolution
actually, what @Soo Kuan Teo suggests in #1 is the best option
Jul 01 2021 05:46 PM
Unfortunately, I also have same issues.
I use Notebook which using Windows 7 Pro 64 bit. I3 2Ghz, RAM 4 Gb.
do need to resolve this problem.
Oct 13 2021 06:58 AM
Reset Internet Explorer - Check the Delete Personal Settings box and reboot the PC.
Feb 24 2022 09:50 PM
Oct 19 2022 07:02 AM
@James Bliss Hi. We also ran into this issue on HP Thinclients with Windows 8.1 embedded. Did you manage to get it to work in the meantime? we are also curious for a solution as we have not found it yet.