question

JeffRiechers-6200 avatar image
0 Votes"
JeffRiechers-6200 asked RobertSteeghs-0437 commented

New AVD deployment clients get "We couldn't connect to the remote PC because of a security error. If this keeps happening, ask your admin or tech support for help. error"

So decommisioned my WVD environment and deploying a new fresh AVD environment in my demo/test lab.

Process all works great, internally I can RDP into my AVD machine.

Trying to connect externally via the APP or browser and it throws errors.

Browser: We couldn't connect to the remote PC because of a security error. If this keeps happening, ask your admin or tech support for help.

Full client: Your remote desktop connection failed because the remote computer cannot be authenticated. Your computer's settings do not allow connection to this remote computer because it cannot be identified. Either it is running a version of Windows that is earlier thank Windows Vista, or it is not configured to support server authentication.

I tried changing the CREDSSP settings in AVD, no luck.

Checked MFA and all authentication is working fine.

Can RDP directly to the machine in Azure with the same account used externally.

azure-virtual-desktop
· 5
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@JeffRiechers-6200

Just checking in to see if you deployed Azure AD joined VMs?

0 Votes 0 ·

No, I did on-premise AD. But ADConnect is syncing everything together to my Azure Cloud AD.

0 Votes 0 ·

@JeffRiechers-6200

Thanks for sharing the information.
Can you please confirm if the UPN user account synced matching from on-Prem with AAD?

0 Votes 0 ·

@JeffRiechers-6200

Any update on the issue?

Can you please confirm if this error is coming prior to putting credentials or after putting credentials?

0 Votes 0 ·

"We couldn't connect to the remote PC because of a security error"

I have the same problem on a existing host pool with a fresh build server.

If we revert back to our old CreateHostpoolTemplate.json file then we're able to logon.
But we've added some new parameters for aadjoin en intune support.

Tried this with an cloud only account and an synchronized user account from AD.

0 Votes 0 ·

0 Answers