full image - Repost: AVD connection "no resources" connecting to VM that is not domain joined. (from Reddit.com, AVD connection "no resources" connecting to VM that is not domain joined.)
Mining:
Exchanges:
Donations:
Hello, a while back I set up an AVD workspace (hostpool has only one session host) that a few users access through the WVD browser portal, and that has been working great for their purposes.Now, I have attempted to set up access to another VM desktop in basically the way, but when I try to connect to it I get the error We couldn't connect because there are currently no available resources. Try again later or if this keeps happening, ask your admin or tech support for help. I haven't yet identified every difference between these two setups (there are probably a couple on the networking side) but the most glaring difference is that the session host that works is domain joined and the one that doesn't work is not. Based on a few other threads involving the error, it seems like being domain joined does make a significant difference in the setup. So before going any further I want to make sure this is even possible.Access to the Azure workspace I created for this newer hostpool is handled by an AD security group, but I had hoped from there it would still be able to connect to a VM that is not domain joined and that users could just enter credentials upon connect. Is there any way to make this work without joining it to the domain or is that just a no-go? I was planning to join the session host VM to a small single-DC domain created for testing.
Social Media Icons