Skip to content
This repository has been archived by the owner on Nov 17, 2023. It is now read-only.

Could not connect to resources. #8

Closed
LucaOtto opened this issue May 19, 2021 · 11 comments
Closed

Could not connect to resources. #8

LucaOtto opened this issue May 19, 2021 · 11 comments
Assignees

Comments

@LucaOtto
Copy link

I configured all the resources and when I go to https://rdweb.wvd.microsoft.com/arm/webclient/index.html I can see the list of apps and a personal desktop listed
image

However when trying to launch any of them I receive this error:
image

The VMs are running and objects in AD are also created.
image

Can you please advise? Error doesn't provide any clues.

Thanks

@dwnatwick
Copy link
Contributor

@LucaOtto. Is the user licensed for Microsoft 365 applications? Have you attempted a connection to the Remote Desktop rather than just the apps? Thank you very much.

@LucaOtto
Copy link
Author

@dwnatwick : yes I attempted to connect to the desktops ( pooled and single). Same error. The users are demo users generated through the M365 portal. It shows that users are synched via AD Connect to the local AD ( Exercises 1 to 4).

@dwnatwick
Copy link
Contributor

@LucaOtto . Did you assign the O365 licenses to the users when they were created?

@LucaOtto
Copy link
Author

@dwnatwick I just ( double-checked): I used this demo user, she seems to have all the proper licenses in place:
image

image

@dwnatwick dwnatwick assigned dwnatwick and unassigned dwnatwick May 19, 2021
@KitSkin
Copy link
Contributor

KitSkin commented May 19, 2021

@LucaOtto, if you go to the WVD Host Pool, under the Overview section, is the Unavailable listed as '0'? Another way to look at it, if you look at your Session Hosts for your host pool do they both have an 'Available' status and Drain Mode 'Off'?
image

@KitSkin
Copy link
Contributor

KitSkin commented May 19, 2021

Also, if you've been sitting idle on the website for 30 minutes or more, your token could have expired as well. To resolve this, just sign out the session and sign back in.

@LucaOtto
Copy link
Author

@KitSkin yes, they are available and drain mode off. I connected to the desktop and/or published apps within a minute of completing the backend system setup, I don't believe it's because of the above.

@KitSkin
Copy link
Contributor

KitSkin commented May 19, 2021

Could you enable diagnostics and Log Analytics to help centralize the error reporting for diagnostics?

@LucaOtto
Copy link
Author

My VS subscription has only few $$ left, I will have to wait the next billing cycle to do that.

@KitSkin
Copy link
Contributor

KitSkin commented May 19, 2021

the Log Analytics make it easier to diagnose the problem by putting everything in one place to query against, but you can also go to each resource and use the troubleshooting guides to examine errors on each:
https://docs.microsoft.com/en-us/azure/virtual-desktop/troubleshoot-vm-configuration

One thing you might want to do is try with the Remote Desktop Client rather than the web client. Sometimes the errors will be logged with more verbosity in your local Event Log that aren't necessarily translated through the web client without the diagnostic logs enabled.

@DawnmarieDesJardins
Copy link
Contributor

Closing issue - no additional communication from field & recent update merge with PR #9

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants