Updated 12/20/2019
With the Windows Virtual Desktop now General Available (GA), we wanted to provide a quick overview of the steps required to get your environment up and running.
Before I begin;...
Updated Mar 18, 2020
Version 14.0
Blog Post
Hi! I am having same technical issue as ShehzadUIT . I was able to deploy machines as host pool. I am able to connect to each one separately using RDP, but not from https://rdweb.wvd.microsoft.com/webclient/index.html web or rdp. Machines are deployed in VNET connected to on-prem networks. Users from local AD are synced to Azure AD and back to Azure ADDS machines are connected to.
Could you please share how you overcome this error ?
Oops, we couldn't connect to "Session Desktop"
We couldn't connect to the gateway because of an error. If this keeps happening, ask your admin or tech support for help.
From: RdsDiagnosticActivities
ActivityId : dc30cbd1-8011-41fc-8fde-d764de2e0000
ActivityType : Connection
StartTime : 5/2/2019 12:19:34 PM
EndTime : 5/2/2019 12:19:40 PM
Outcome : Failure
Status : Completed
Details :
LastHeartbeatTime : 5/2/2019 12:19:40 PM
Checkpoints :
Errors :
ActivityType : Connection
StartTime : 5/2/2019 12:19:34 PM
EndTime : 5/2/2019 12:19:40 PM
Outcome : Failure
Status : Completed
Details :
LastHeartbeatTime : 5/2/2019 12:19:40 PM
Checkpoints :
Errors :