Forum Discussion
Solved
Windows Virtual Desktop - Your computer can't connect to Remote Desktop Gateway server
I have successfully deployed WVD to my MSDN tenant following the steps 1 and 2 in https://docs.microsoft.com/en-gb/azure/virtual-desktop/tenant-setup-azure-active-directory and https://docs.microsoft...
I think I may have worked out my problem, I have been testing with a user account I setup in Azure AD. I have only just setup the tenant and AD domain to test WVD. I have just tested with an account I had created on the AD Server (Still in Azure but with AD Connect installed to sync to AAD) and this has worked fine. I have also created another AAD account and tried to connect to the desktop but this failed with the same error.
Interestingly I am getting prompted to enter my credentials again upon connection, not sure if I have missed something with the SSO settings?
Christian_Montoya
Microsoft
Microsoftray077 : Unfortunately, we don't have that true "single sign-on" just through Azure AD. This is primarily because Windows logon requires username/password or smartcard still. We are finalizing our flow for single sign-on when federating your Azure AD to ADFS, so you would only ever get the Azure AD credential prompt (not a Windows credential prompt). We should have that document up later in the Preview.
Thanks for all your testing!
Thanks for the info, can you confirm that the behaviour I was seeing with an Azure AD only account (User was not defined in the "On-Premise" AD") was expected.
- Christian_Montoya
hdsit : Can you run the diagnostics command here to get the errors for the connection: https://docs.microsoft.com/azure/virtual-desktop/diagnostics-role-service#filter-diagnostic-activities-by-activity-type ? You may also want to run it with the -Detailed parameter, then you can see the Errors for the activity. That should be a good start.
I am experiencing the same issue and the users are sync from my On-premise AD with AD connect.
This worked initially and then stop working for the same users is no longer working.Any ideas?
- Christian_Montoya
ray077 : Yes, confirming that the issue is that the user must exist both in Azure AD and the Windows Server (on-prem) AD, so this was an expected error.
