Forum Discussion

Paul Shadwell's avatar
Paul Shadwell
Brass Contributor
Jun 22, 2019

User can't login to HostPool.

A new host pool has been created and I am able to login myself but when I add one of my users to to the AppGroup so they can see the desktop icon, they login and get an error message:

Oops, we couldn't connect to "AzureDesktops"

Sign in failed. Please check your user name and password and try again.

The user can login to other services but not WVD.
FYI I have setup Azure AD DS. I am using AD Connect to sync with our on-prem domain DCs.
Any suggestions as to how to diagnose this one?
  • Deleted's avatar
    Deleted
    Jun 22, 2019

    HiPaul Shadwell 

     

    Are you sure deployment did not fail a domain join?

     

    Run below  cmdlet to add Azure Active Directory user to the default desktop app group for the host pool.

     

    PowerShell

    Add-RdsAppGroupUser -TenantName <tenantname> -HostPoolName <hostpoolname> -AppGroupName "Desktop Application Group" -UserPrincipalName <userupn>

     

    Thank you

    Dav,

     
    • Paul Shadwell's avatar
      Paul Shadwell
      Brass Contributor
      Jun 23, 2019

      Deleted Ah! that did the trick. I used the WebUI tool to add the user but it seems this is not working yet.

    • Paul Shadwell's avatar
      Paul Shadwell
      Brass Contributor
      Jun 23, 2019

      Deleted Domain join succeeded. Deployment completed with no errors.

  • michawets's avatar
    michawets
    Iron Contributor
    Jun 22, 2019

    Hi Paul Shadwell ,

    When you said that you were able to login, do you mean using WVD?

     

    Deleted , considering that the user has the icon for the AppGroup, I would think the user is correctly asigned, but the AD could indeed be an issue.

     

    Paul Shadwell , when you run the Get-RdsSessionHost, do you see the new sessionhost and is it Available?

  • Philby1905's avatar
    Philby1905
    Copper Contributor
    Mar 02, 2021

    @ know this is an old thread but hopefully my finding may help others.

    I have one user who cant login to the session host but has logged into the pool.
    The special thing about this user is the only user that existed in the AAD before me.

    The 1st stage login to the pool is done against Azure AD and works.
    The 2nd stage is against the Session Host and is against AAD-DS this fails. When AAD-DS was setup I had to change my Azure password before my password from AAD could sync to AAD-DS as the password syncs on change.

    I assume the failing will need to change password in Azure. It didn't affect other users as they were created in AAD after AAD-DS was setup and so their passwords are synced.

    • mziada's avatar
      mziada
      Copper Contributor
      Apr 15, 2021
      You are a life saver, that really helped me with the exact same issue I have. Creating AAD DS with WVD, so the already created users weren't able to login!

Share