Unable to open SessionDesktop

Question

Hello,

I am setting up the Azure Virtual Desktop and have followed the steps in the Docs. Here are the steps at the high level:

1. I have a "Pay-as-you-go" Subscription.
2. Created a resource group in Central India region.
3. Created a Virtual network and a subnet for the above Resource Group. Also have a Bastion Server as instructed in the help.
4. Created a host pool with in the same resource group with the above Virtual network and subnet having 2 VMs in the same region. Also added a Workspace
5. Once the host pool was created, added the "targetisaadjoined:i:1;: in the Advanced section of RDP properties.
6. In the Application Group of the host pool, added 1 user in the Assignments.

After doing the above steps and verifying the output, I go to https://client.wvd.microsoft.com/arm/webclient and login with the Principal user name and password. I see the "SessionDesktop" application under the Workspace created in the hostpool. When I click to open the SessionDesktop, it asks for the Username and Password again and after providing the same I get "Sign in failed. Please check your username and password and try again.". I have reset the password of my account but that still does not work.

Also while logging in to the above URL, I get a message to add additional authentication, but it also provides a "Skip Step" option as there is no other authentication needed.

I have looked at the existing tickets that are close to my issue, but have not found any solution. Any help would be appreciated.

Thank you,

SuhastAddition_auth_Azure.png

Answer 1

Hi

a few things to try as a starting point.

1. Check the status of your Session Hosts to ensure they are showing as available:

2. Make sure you have Log Analytics enabled for all aspects of your AVD deployment (Workspace, Host Pool and Session Hosts). Also install the Azure Monitor agent locally on the session hosts. Log Analytics will give you detailed information into why the logins are failing.
3. Set one of the hosts to Drain Mode to ensure logins are forced to a single host. If the error persists against both, you may need to re-deploy the hosts.
4. Check Azure AD to ensure the devices are registered correctly.

Please reply back with answers if you need further assistance.

Hope this helps,

Thanks

Michael Durkan

• If the reply was helpful please upvote and/or accept as answer as this helps others in the community with similar questions. Thanks!