Forum Discussion
Does MFA Work? & Oops, we couldn't connect to "Session Desktop"
I can't seem to connect to a WVD host after following the tutorial.
With my account (MFA enforced), access via the web prompts for a password again, then gives the error: Oops, we couldn't connect to "Session Desktop"
Access via the desktop client gets stuck in a loop, asking for my password over and over.
The Powershell diagnostics (via Get-RdsDiagnosticActivities) shows a "Failure" with each attempt -- but no more details:
ActivityId : f5dfe22c-9ec7-4c49-be1e-ab5658900000
ActivityType : Connection
StartTime : 3/26/2019 2:02:37 PM
EndTime : 3/26/2019 2:02:56 PM
UserName : ***
RoleInstances : rdwebclient;mrs-eus2r1c002-rdgateway-prod-staging::RD0003FF459F62;mrs-eus2r1c002-rdbroker-prod-stag
ing::RD0003FF45DF76;≤ahp-0.contoso.com≥
Outcome : Failure
Status : Completed
Details : {[ClientOS, Linux x86_64 Chrome 73.0.3683.88], [ClientVersion, 1.0.13-wvd], [ClientType, HTML],
[PredecessorConnectionId, ]...}
LastHeartbeatTime : 3/26/2019 2:02:56 PM
Checkpoints : {LoadBalancedNewConnection}
Errors : {Microsoft.RDInfra.Diagnostics.Common.DiagnosticsErrorInfo}
Anyone else seeing this? I'm tempted to blame MFA but ... ?
2 Replies
- Christian_Montoya
Microsoft
Nicholas Semenkovich : Can you run the same query and save the object to a variable, then look at the errors by expanding the Errors property?
Also, some quick steps to troubleshoot...does the user exist both in Azure AD and your Windows Server AD?
Closing the loop here --
We were using Azure AD online only (with Azure AD joined desktops) & just added Azure AD Domain Services for WVD.
Apparently enabling Azure AD Domain Services doesn't sync passwords to the Cloud DC on login -- you have to change user passwords for hashes to sync to the DC (which is what caused this error).
