Fix AVD Could not Connect to Session Desktop Admin has Restricted the Type of Logon Azure Virtual Desktop

In this post, let’s see how to Fix AVD could not 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 AVD session hosts.

I have explained about Fix AVD 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 AVD web clients.

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 – AVD could not connect to session desktop

I have seen this exact error “couldn’t connect to session desktop” many times and a couple of AVD 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 AVD Couldn't Connect to Session Desktop | Admin has Restricted the Type of Logon
Fix AVD Could not Connect to Session Desktop | Admin has Restricted the Type of Logon

Cause of AVD Admin has Rejected Type of Login Error

Well, the cause of this admin has restricted the type of logon error when you try to connect to session host in AVD 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 AVD 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 AVD Couldn’t Connect to Session Desktop | Admin has Restricted the Type of Logon

AVD Sign-in Failed Error

The cause of AVD Admin has Rejected Type of Login Error is given below.

If a user enters the wrong credentials, then the domain controller will try to authenticate and provide 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 AVD Couldn't Connect to Session Desktop | Admin has Restricted the Type of Logon
Fix AVD Couldn’t Connect to Session Desktop | Admin has Restricted the Type of Logon

AVD Legacy code: 0x300006D Error

A quick note on the following AVD error. The resolution for this issue is to click on the 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 AVD Couldn't Connect to Session Desktop | Admin has Restricted the Type of Logon
Fix AVD Couldn’t Connect to Session Desktop | Admin has Restricted the Type of Logon

AVD Session Host – Could not start the connection due to a webworker error

I have received any other error from the AVD Web Client. The error is a bit confusing for end-users because they might not understand what is the web worker. I just disconnected the AVD session and reconnected.

The reconnect helped to resolve the issues with the AVD webworker. I think this is just a timeout issue or something else.

Oops, we couldn’t connect to “Standard”
We could not start the connection due to a webworker error. Please click Reconnect to start a new session without webworker.

AVD Session Host - Could not start the connection due to a webworker error
AVD Session Host – Could not start the connection due to a webworker error

Fix AVD VM RD Client Connection Error 0x83886181

Let’s have a quick look at the AVD VM RD client connection error 0x83886181. I have been using the AVD VM, and the session got disconnected with the following error. The main challenge with this kind of disconnection is bad Teams meeting experience.

Couldn’t connect – Your session ended because there was a protocol error. If this keeps happening, ask your admin or tech support for help.

 Fix AVD VM RD Client Connection Error 0x83886181
Fix AVD VM RD Client Connection Error 0x83886181

Solution | Fix – AVD VM RD Client Connection Error 0x83886181 HTMD Blog (anoopcnair.com)

AVD User Wrong UserName and Password Error

This is the most common error with AVD (Azure Virtual Desktop). The reason could be because of different keyboard layouts. I always get the Wrong username and password errors because of the default UK keyboard layout configured on my AVD Session Host. However, my physical keyboard layout is en-us.

Oops, we couldn’t connect to “Standard”
Sign in failed. Please check your username and password and try again.

AVD User Wrong User Name and Password Error
AVD User Wrong User Name and Password Error

Resources

Categories AVD

Leave a Comment

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