No creation of Session Host in manual steps

[JAK1047]

I had issues with downloading the DSC file through our proxy using the new Windows Virtual Desktop resource. Don't believe there's anyway to set the proxy settings on the newly generated VM before the DSC extension deployment in the resource, so I went ahead and created the tenant, hostpool, appgroup, and domain joined my VM manually. After which I decided to just follow the steps here here to manually join the VM to the hostpool.

I see it in the web portal as a resource and can click it, but get a connection error. Running Get-RdsDiagnosticActivities shows the failure as:

“Could not find any SessionHost available in specified pool = ≤ACE-Win10-MultiSession-HP≥, due to either: sessions are not allowed, no healthy host (RDAgent did not report health information), session limit reached on all SessionHosts in the pool or the pool is empty. Run Get-RdsHostPool and Get-RdsSessionHost cmdlets to get more information.”

Running Get-SessionHost returns null, so that appears to be my issue. Looks like in the DSC extension deployment the ARM launches they set the Win10 VM as a session host using the New method off the PsRdsSessionHost accelerator you get from importing Microsoft.RDInfra.RDPowershell.dll. This is after installing the VDA, VDA Bootloader, and running the SxS Script.

(Line 203 of Script-FirstRdshServer.ps1) [Microsoft.RDInfra.RDManagementData.RdMgmtSessionHost]$rdsh = ([PsRdsSessionHost]::new($TenantName,$HostPoolName,$SessionHostName)).GetSessionHost()

Is there a step missing here or is the assumption you have an RDS sessionhost server of some kind? I see the WindowsVirtualDesktop module has a Set-RDSSessionHost command I can use, but since it wasn't on the guide I wanted to be sure.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 7bfcfbec-b7ca-57e2-67cc-e5891fdbefd7
• Version Independent ID: 16b54c4d-07de-9d14-2a74-38e321361069
• Content: Create a Windows Virtual Desktop Preview host pool with PowerShell - Azure
• Content Source: articles/virtual-desktop/create-host-pools-powershell.md
• Service: virtual-desktop
• GitHub Login: @Heidilohr
• Microsoft Alias: helohr

[JAK1047]

Slight addendum. While there is a Set-RDSSessionHost there doesn't appear to be an Add-RDSSessionHost or New-RDSSessionHost. So no commands that I see to add my VM to the HostPool.

[Karishma-Tiwari-MSFT]

Thanks for the question. We are currently investigating and will update you shortly.

[JAK1047]

I think I may have actually found my issue. The RD Agent installer that is linked to from the guide is 1.0.0.1462. The one the DSC pushes is 1.0.1.7 and about 2MB larger. After uninstalling the one from the guide and installing the one in the DSC package the session host now appears from the Powershell command. Gives me an update failed error of:

UpdateGenevaAsync - Health Check Failed:
Microsoft.RDInfra.RDAgent.Service.InstallationHealthCheckFailedException: PerformBasicMonitoringHealthCheck - no monitoring environment present in registry

But at least I can now see it!

[mimckitt]

@JAK1047 thanks for the update. I will assign to the author to review and see if there is any doc changes we can make.

Also, for any other troubleshooting assistance you can reach out to tech communities where we are currently supporting Virtual Desktop.

https://techcommunity.microsoft.com/t5/Windows-Virtual-Desktop/bd-p/WindowsVirtualDesktop

[JAK1047]

Will do. Thank you!

[ChristianMontoya]

Looks like it was resolved, and we've also made sure the packages are more up-to-date.
#please-close