Forum Discussion

Hermanbonnie's avatar
Hermanbonnie
Copper Contributor
Aug 29, 2019

Internal error occurred when connecting to RD

We have set up a WVD tenant but have not been able to logon to the VM.   When connecting we get the error "Internal error occurred".   Please see the output of the get-rdsdiagnosticsactivies belo...
michawets's avatar
michawets
Iron Contributor
Sep 04, 2019

Hi Hermanbonnie ,

 

Could you exec this cmd ?

Get-RdsDiagnosticActivities -TenantName $myTenantName -UserName "UPN@UPN.com" -Detailed | Select-Object Errors -ExpandProperty errors

 

This will give the details from the errors in this case.

  • Hermanbonnie's avatar
    Hermanbonnie
    Copper Contributor
    Sep 04, 2019

    Hi michawets ,

     

    Please see the result below:

     

    PS C:\WINDOWS\system32> Get-RdsDiagnosticActivities -TenantName $myTenantName -UserName "UPN@DOMAIN.COM" -Detailed | Select-Object Errors -ExpandProperty errors


    Errors : {Microsoft.RDInfra.Diagnostics.Common.DiagnosticsErrorInfo}
    ErrorSource : RDAgent
    ErrorOperation : AddUserToRDUGroup
    ErrorCode : -2147467259
    ErrorCodeSymbolic : ConnectionFailedAdErrorNoSuchMember
    ErrorMessage : Failed to add user = ≤UPN@DOMAIN.COM≥ to group = Remote Desktop Users. Reason: Win32.ERROR_NO_SUCH_MEMBER
    ErrorInternal : False
    ReportedBy : RDGateway
    Time : 04/09/2019 10:27:45

    • michawets's avatar
      michawets
      Iron Contributor
      Sep 04, 2019

      Hi Hermanbonnie ,

       

      Just a small question: is the user available in both Windows AD & Azure AD?

      Is it in both cases the same UPN?

       

      And perhaps this could be the issue:

      https://docs.microsoft.com/en-us/azure/virtual-desktop/troubleshoot-client-connection#error-o_add_user_to_group_failed--failed-to-add-user--username-to-group--remote-desktop-users-reason-win32error_no_such_member

       

      • Hermanbonnie's avatar
        Hermanbonnie
        Copper Contributor
        Sep 05, 2019

        Hi michawets ,

         

        Is it mandatory to join the Virtual desktop to a Windows active directory domain?

         

        I was under the impression that the setup of virtual desktop joins the VD to Azure AD and users in that Azure AD can logon to it.

         

        There is no mention of an on-prem AD requirement in the documentation.

Resources