Internal error occurred when connecting to RD

Copper Contributor

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 below:


PS C:\WINDOWS\system32> Get-RdsDiagnosticActivities -TenantName $myTenantName -UserName "" -Detailed

ActivityId : aa119e5d-cbcf-4a96-a297-bc16f4cb0000
ActivityType : Connection
StartTime : 29/08/2019 14:03:45
EndTime : 29/08/2019 14:03:51
UserName :
RoleInstances : Workstationname;mrs-eus2r1c001-rdgateway-prod-staging::RD0004FFA4C4AF;mrs-eus2r1c001-rdbroker-prod-staging::RD0003FF8BA99A;≤WVDNDI-0≥
Outcome : Failure
Status : Completed
Details : {[ClientOS, WINDOWS; 10.0.18362], [ClientVersion,], [ClientType, MSRDC], [PredecessorConnectionId, ]...}
LastHeartbeatTime : 29/08/2019 14:05:23
Checkpoints : {LoadBalancedNewConnection, TransportConnecting, TransportConnected, RdpStackDisconnect}
Errors : {Microsoft.RDInfra.Diagnostics.Common.DiagnosticsErrorInfo}

ActivityId : 992eed1a-b079-4c2b-91e5-7f0eecedb7a6
ActivityType : Feed
StartTime : 29/08/2019 14:03:36
EndTime : 29/08/2019 14:03:36
UserName :
RoleInstances : rdwebclient;mrs-eus2r1c001-rdbroker-prod-staging::RD0003FF8BA99A
Outcome : Success
Status : Completed
Details : {[ClientOS, Win32 Chrome 76.0.3809.132], [ClientVersion,], [ClientType, HTML], [ClientIPAddress, ]...}
LastHeartbeatTime : 29/08/2019 14:03:36
Checkpoints : {}
Errors : {}


Hopefully somebody will be able to guide us in the right direction on this.

5 Replies

Hi @Hermanbonnie ,


Could you exec this cmd ?

Get-RdsDiagnosticActivities -TenantName $myTenantName -UserName "" -Detailed | Select-Object Errors -ExpandProperty errors


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

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

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:


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.

Hi @Hermanbonnie ,


Yes, I'm afraid your Sessionhost(s) needs to be in a Windows AD, which syncs with Azure AD

This can be

  • a Azure VM with Windows AD role installed, and Azure AD Connect
  • Azure AD DS 


It is mentioned in the Requirements from WVD:

Your infrastructure needs the following things to support Windows Virtual Desktop:

  • An Azure Active Directory
  • A Windows Server Active Directory in sync with Azure Active Directory. This can be enabled through:
    • Azure AD Connect
    • Azure AD Domain Services
  • An Azure subscription, containing a virtual network that either contains or is connected to the Windows Server Active Directory

The Azure virtual machines you create for Windows Virtual Desktop must be: