Problems authenticating from Remote Desktop Client

[Greg Eschinger]

Hello,

Does anyone have any suggestions for problems connecting from the RDP client?

I downloaded the app from Windows 365 (microsoft.com) and used the subscription URL.  Then when I login I get the following error when using Windows Hello:

An authentication error has occurred (Code: 0x8007013d).

If I instead use the Password it gets to the point of Securing Remote Connection and then it pops up the error: The logon attempt failed.

The same credentials work fine initiating the connection from the browser.

[#2]

@fwdLarry @Harry_Dev - If you're able to provide a screenshot, that'd be great! We still may need to wait for Support to get back to you, but hoping to see if anything on the screenshot sticks out.

[#3]

Hi @Christian_Montoya,

Support suggested the following. I ran the commands within the cloud PC (through the browser). No change still unable to login via the desktop RDP client. I canceled the clould PC subscription, waited and hour, added a new cloud pc license and assigned it to another user in our domain. Same issue. He was able to login via the browser but not from his windows 10 pro AD joined computer. Screenshot attached.

Hi Larry,

When you sign in from your browser can you check the dsregcmd /status on your CMD command prompt.

If the device looks deregistered try the below steps

s:

1. Open the command prompt as an administrator.
2. Enter dsregcmd.exe /debug /leave.
3. Sign out and sign in to trigger the scheduled task that registers the device again with Azure AD.

[#4]

Interesting development from my end. I'm continuing to have issues with username/password login on the Windows client.

However, I discovered that when I use the Windows Hello PIN (of my local machine), it works. I wonder if this is the same for anyone else.

This is a useful workaround for me for now, but obviously not a solution to the main issue.

[#5]

I was able to get around this by removing the remote desktop app.

After a resinstall, during authentication, it prompts with a check box to allow the organization to manage the device. I unchecked that AND clicked the lick to Login with app only. This worked right away for. @Greg Eschinger 

[#6]

We have exactly the same problem, and also only on AAD joined devices. Works fine on another device, and also of course via the browser.

[#7]

I think this login from AAD connect computers is related to MFA. I created a new user with MFA disabled and login was successful. Support recommended the following:

"To be able to use MFA with windows 365 via the desktop X64 RDP app, you need to configure this using Conditional Access, where you specify exactly which cloud app is targeted by the policy, in this case it would be the windows 365 cloud app called:
Windows Virtual Desktop

To be able to use conditional access, a license for Azure AD Premium P1 is required."

[#8]

@Christian_Montoya 

Hi Christian,
Getting a similar issue with one of our vendor who is using their own corporate Laptop (Windows 10 enterprise edition) for accessing avd session host. He is able to access it via Web client but not able to access it via RD client application.
While accessing via RD client gets an error getting continuous authentication after entering the credentials every time it keeps popping up but won't authenticate.
After checking the event viewer gets the error Event id :- 613 i.e table database property is out of date and flaunting wwahost.exe application.
Please suggest some solution for this asap. @Christian_Montoya

[#9]

@amittanwar878 

We solved it with the help of Microsoft support. It was related to conflicting configuration in MFA. I believe it was happening when MFA was enabled in Office 365 as well as in AAD, location based rule.