Fix WVD Couldn’t Connect to Session Desktop | Admin has Restricted the Type of Logon | Windows Virtual Desktop

In this post, let’s see how to Fix WVD couldn’t connect to session desktop, and the admin has restricted the type of logon-related issues. Well, this is a very common error that I have seen in PoC/testing environments where admins use different sets of test accounts to access WVD session hosts.

I have explained about Fix WVD Refreshing Your Token Error | Couldn’t Connect to Session Desktop in the previous post. I have seen the admin has restricted the type of logon error also most with WVD web client.

I have also shared experience with two other common errors. Let’s have a look at those errors in later sections of this post 1. Sign-in Failed Error 2. Legacy code: 0x300006D Error.

Patch My PC

Issue – couldn’t connect to session desktop

I have seen this exact error “couldn’t connect to session desktop” many times and a couple of WVD PoC testers raised this issue.

Error Message Oops, we couldn’t connect to “Session Desktop” we couldn’t connect to the remote PC because the admin has restricted the type of logon that you can use. Ask your admin or tech support for help.

Fix WVD Couldn't Connect to Session Desktop | Admin has Restricted the Type of Logon
Fix WVD Couldn’t Connect to Session Desktop | Admin has Restricted the Type of Logon

Cause?

Well the cause of this admin has restricted the type of logon error when you try to connect to session host in WVD is mainly because of ignorance of the end-user. What? Yes of course. This is why I highlighted in the first paragraph of this post that I have seen this issue mostly with PoC/Test environments.

1E Nomad

In PoC or Test environment, the test users might have more than one user accounts to test and certify different scenarios. This error occurs when:

  • User Logs into WVD Web client with a user ID (for example – [email protected]).
  • Click on Remote Desktop Icon to logon to session desktop/remote PC.
  • The user ([email protected]) will get prompted to re-enter the user name and password (domain-level authentication).
  • But because of user error or ignorance – The user enters a different user name (anoop2@htmdforum.com) and password.
  • Click on Submit button.
Fix WVD Couldn't Connect to Session Desktop | Admin has Restricted the Type of Logon
Fix WVD Couldn’t Connect to Session Desktop | Admin has Restricted the Type of Logon

WVD Sign-in Failed Error

If a user enters wrong credentials, then the domain controller will try to authenticate and provides the following Sign-in failed error.

Error MessageOops, we couldn’t connect to “SessionDesktop”. Sign-in failed. Please check your username and password and try again.

Fix WVD Couldn't Connect to Session Desktop | Admin has Restricted the Type of Logon
Fix WVD Couldn’t Connect to Session Desktop | Admin has Restricted the Type of Logon

WVD Legacy code: 0x300006D Error

A quick note on the following WVD error. The resolution for this issue is click on close button and relaunch the remote desktop or session desktop connection.

  • Couldn’t connect. Something went wrong when we tried to connect. If this keeps happening, ask your admin or tech support for help.
  • Disconnect code: UnknownError, legacy code: 0x300006D, legacy extended code: 0x0, activityId: {cb5c561f-c822-4f0b-8d7d-0d4f9e630000}
Fix WVD Couldn't Connect to Session Desktop | Admin has Restricted the Type of Logon
Fix WVD Couldn’t Connect to Session Desktop | Admin has Restricted the Type of Logon

Resources

Categories WVD

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.