Let’s see how to fix the issue not able to connect to WVD personal desktop issue. This issue is experienced with the latest release of WVD (a.k.a WVD v2). I have explained about WVD v2 ARM model architecture in the last blog post.
I have shared the experience of creating new host pools, Workspaces, and Session Hosts in the following post. WVD v2 Admin Experience Create New Host Pool | Workspace | Session Host.
Problem Statement – Not Able to Connect to WVD
- Logon to https://rdweb.wvd.microsoft.com/arm/webclient/index.html with Azure AD user name and password.
- Click the Remote Desktop Session host available.
- Log in to Remote Desktop with the same Azure user name and password used above.
- We couldn’t connect because there are currently no available resources. Try again later or contact tech support for help if this keeps happening.
- Error 0x3000046
- Extended Error Code 0x0
Troubleshooting
The user is not able to connect to the personal virtual desktop (with the direct assignment) when I create a host pool and session host from the new portal for WVD (a.k.a WVD v2).
Everything works ok with the old WVD process of creating host pool and adding session hosts etc… using PowerShell. And the user is part of the Desktop App group as I explained in the above post.
- The following are the error Microsoft support engineer retrieved for the issue.
ActivityId env_name env_time ErrorSource ErrorCode ErrorMessage ReportedBy ErrorInternal
3ff94fe9-2995-48df-a938-8fe4b467800000 ##Microsoft.RDInfra.Monitoring.Events.DiagErrorInfo 2020-05-22 23:21:21.0788537 RDBroker -21678388 Host pool = ≤WVD2≥ is a PersonalDesktop pool with Direct assignment type. In order to connect to this pool, user = ≤[email protected]≥ has to have a SessionHost pre-assigned! RDGateway FalseReturning error '{
"Code": "E_PROXY_ORCHESTRATION_LB_NO_SESSIONHOST_AVAILABLE",
"Message": "UserId = ≤[email protected]≥ should have a pre-assign SessionHost to connect to. The host pool = ≤WVD-v21≥ is a PersonalDesktop pool with Direct assignment. The administrator needs to assign the SessionHost prior to user connecting to this host pool.",
"Target": null,
"Details": null,
"InnerError": null
}' HttpCode=400 ContentType='application/json; charset=utf-8'
Update-AzWvdSessionHost_UpdateExpanded: ActivityId: 419fdfb-480c-4da9-9d5f-kajskljaasbc77bcec8 Error: SessionHost does not existFix PowerShell Way
As per Microsoft documentation and Microsoft support engineer, we need to use the PowerShell command to fix this issue. There is a PowerShell command to assign this a user to a personal desktop.
NOTE! – I couldn’t find the option to assign a personal desktop to a user from WVD new portal experience (a.k.a WVD v2). This was the situation when I worked on this issue with Microsoft engineer.
- Run the following PowerShell command from using the following option WVD Management Using Visual Studio Code Instead of PowerShell ISE.
- Replace all the following variables with the host pool name, session hostname, resource group name, and userupn.
Update-AzWvdSessionHost -HostPoolName $hostpoolname -Name $sessionhostname -ResourceGroupName $resourcegroupname -AssignedUser $userupn
WVD v2 Portal Experience
Microsoft WVD black belt Tom Hickling shared a tweet to confirm, there is an option to assign personal desktop to user from WVD new portal (a.k.a WVD v2).
- Login to portal.azure.com
- Search with “Windows Virtual Desktop“.
- Click on the Windows Virtual Desktop icon.
- Select Personal Host Pool.
- Select personal desktop Session Hosts.
- Navigate to the right until you see the Assigned user column.
- Click on (Assign) link and select the user (direct assignment).
Nice one Anoop. Thanks for sharing.
BTW typo in “back belt”
Thank you
For me, I had the ‘Max session limit’ set too low on the host pool. That can be modified in the ‘Properties’ section of the host pool.
It would have been nice if the error message said something like “We couldn’t connect because the max session limit of 4 has already been reached”.
Yes true … I agree ☝️