Can not connect to WVD RDS session host unavailable

%3CLINGO-SUB%20id%3D%22lingo-sub-1387064%22%20slang%3D%22en-US%22%3ECan%20not%20connect%20to%20WVD%20RDS%20session%20host%20unavailable%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1387064%22%20slang%3D%22en-US%22%3E%3CP%3EI%20created%20a%20new%20WVD%20for%20a%20customer%20this%20morning%20using%20the%20newly%20updated%20image.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eusing%20get-rdssessionhost%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Estatus%20says%20unavailable%20I%20can%20see%20the%20session%20desktop%20in%20the%20html5%20browser%20but%20it%20does%20not%20connect.%20No%20errors%20on%20the%20join%20process%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1387088%22%20slang%3D%22en-US%22%3ERe%3A%20Can%20not%20connect%20to%20WVD%20RDS%20session%20host%20unavailable%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1387088%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F305776%22%20target%3D%22_blank%22%3E%40christianmontoya%3C%2FA%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1387175%22%20slang%3D%22en-US%22%3ERe%3A%20Can%20not%20connect%20to%20WVD%20RDS%20session%20host%20unavailable%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1387175%22%20slang%3D%22en-US%22%3E%3CP%3EUnavailable%20is%20reported%20for%20cases%20where%20service%20is%20unable%20to%20reach%20the%20VM%20to%20establish%20the%20connections.%20This%20can%20happen%20when%20either%20the%20VM%20is%20shutdown%20or%20if%20there%20are%20issues%20with%20domain%2C%20network%20or%20agent.%20Can%20you%20ensure%20VM%20is%20booted%20up%20and%20get%20us%20output%20of%20following%20two%20commands%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EGet-RdsSessionHost%20-TenantName%20%3CTENANTNAME%3E%20-HostPoolName%20%3CHOSTPOOL%3E%20-Name%20%3CHOSTNAME%3E%3C%2FHOSTNAME%3E%3C%2FHOSTPOOL%3E%3C%2FTENANTNAME%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CDIV%3E%24h%20%3D%20Get-RdsSessionHost%20-TenantName%20%3CTENANTNAME%3E%20-HostPoolName%20%3CHOSTPOOL%3E%20-Name%20%3CHOSTNAME%3E%3CBR%20%2F%3EConvertFrom-Json%20%24h.SessionHostHealthCheckResult%26nbsp%3B%26nbsp%3B%3C%2FHOSTNAME%3E%3C%2FHOSTPOOL%3E%3C%2FTENANTNAME%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1392386%22%20slang%3D%22en-US%22%3ERe%3A%20Can%20not%20connect%20to%20WVD%20RDS%20session%20host%20unavailable%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1392386%22%20slang%3D%22en-US%22%3E%3CP%3ETake%20one%20of%20the%20following%20actions%20to%20resolve.%3C%2FP%3E%3CP%3EManually%20add%20the%20VMs%20to%20a%20domain.%3C%2FP%3E%3CP%3ERedeploy%20the%20template%20once%20credentials%20have%20been%20confirmed.%20See%20Create%20a%20host%20pool%20with%20PowerShell.%3C%2FP%3E%3CP%3EJoin%20VMs%20to%20a%20domain%20using%20a%20template%20with%20Joins%20an%20existing%20Windows%20VM%20to%20AD%20Domain.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1400055%22%20slang%3D%22en-US%22%3ERe%3A%20Can%20not%20connect%20to%20WVD%20RDS%20session%20host%20unavailable%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1400055%22%20slang%3D%22en-US%22%3EI%20got%20it%20fixed%20i%20appreciate%20all%20the%20replies%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1481805%22%20slang%3D%22en-US%22%3ERe%3A%20Can%20not%20connect%20to%20WVD%20RDS%20session%20host%20unavailable%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1481805%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F322816%22%20target%3D%22_blank%22%3E%40tommy_barnes%3C%2FA%3E%26nbsp%3B%2C%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ecan%20you%20share%20your%20solution%20or%20what%20things%20you%20did%20that%20finally%20fixed%20it%20%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1506863%22%20slang%3D%22en-US%22%3ERe%3A%20Can%20not%20connect%20to%20WVD%20RDS%20session%20host%20unavailable%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1506863%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F322816%22%20target%3D%22_blank%22%3E%40tommy_barnes%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHi%20Tommy%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20did%20you%20do%20to%20fix%20it%3F%26nbsp%3B%20Do%20you%20have%20a%20link%20or%20something%20you%20could%20share%3F%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3CP%3EMike%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1507097%22%20slang%3D%22en-US%22%3ERe%3A%20Can%20not%20connect%20to%20WVD%20RDS%20session%20host%20unavailable%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1507097%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F575397%22%20target%3D%22_blank%22%3E%40no-va%3C%2FA%3E%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESorry%20for%20the%20late%20response.%26nbsp%3B%20I%20ended%20up%20deleting%20the%20setup%20and%20recreated%20setup%20all%20from%20powershell%20and%20then%20i%20set%20up%20everything%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1508641%22%20slang%3D%22en-US%22%3ERe%3A%20Can%20not%20connect%20to%20WVD%20RDS%20session%20host%20unavailable%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1508641%22%20slang%3D%22en-US%22%3E%3CP%3ECan%20you%20elaborate%20on%20what%20you%20did%20to%20troubleshoot%26nbsp%3Bthe%20issue%3F%20I%20ran%20into%20the%20same%20issue%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F322816%22%20target%3D%22_blank%22%3E%40tommy_barnes%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1521497%22%20slang%3D%22en-US%22%3ERe%3A%20Can%20not%20connect%20to%20WVD%20RDS%20session%20host%20unavailable%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1521497%22%20slang%3D%22en-US%22%3E%3CP%3EI%20had%20a%20similar%20issue.%20After%20deploing%20our%20custom%20image%2C%20the%20RDS%20session%20hosts%20wold%20become%20unavailable.%3CBR%20%2F%3EWe%20used%20Win%2010%20multi%20session%20as%20the%20base%2C%20the%202004%20build.%20I%20traced%20the%20issue%20back%20the%20RD%20agent%20deployment.%20The%20SxS%20stack%20was%20not%20enabled..%20I%20loggd%20into%20the%20session%20host%20via%20the%20bastion%20connection.%20Everything%20was%20fine.%20No%20major%20errors%20anywhere.%20I%20noticed%20that%20we%20had%20multiple%20versions%20of%20the%20we%20had%20multiple%20versions%20of%20the%20Remote%20Desktop%20Services%20INfrastructure%20Agent%20installed.%20I%20removed%20the%20old%20ones%20and%20kept%20the%20newest%20one.%26nbsp%3B%20I%20re-ran%20the%20script%20in%20the%26nbsp%3BC%3A%5CDeployAgent%5CEnableSxSStackScript%20folder%20to%20register%2Fstart%20the%20Sxs%20stack%20and%20restarted%20the%20machine.%20It%20should%20have%20been%20registered%2Fstarted%20on%20the%20initital%20deployment%2C%20but%20for%20some%20reason%20it%20didn't%20trigger..%20I'm%20still%20trying%20to%20figure%20out%20why.%20That%20appears%20to%20do%20the%20trick%20for%20us.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1622939%22%20slang%3D%22pt-BR%22%3ERe%3A%20Can%20not%20connect%20to%20WVD%20RDS%20session%20host%20unavailable%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1622939%22%20slang%3D%22pt-BR%22%3EGuys%2C%20%3CBR%20%2F%3E%20Follow%20the%20step%20by%20step%20to%20solve%20this%20situation%3A%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fpt-br%2Fazure%2Fvirtual-desktop%2Ftroubleshoot-vm-configuration%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fpt-br%2Fazure%2Fvirtual-desktop%2Ftroubleshoot-vm-configuration%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1764035%22%20slang%3D%22en-US%22%3ERe%3A%20Can%20not%20connect%20to%20WVD%20RDS%20session%20host%20unavailable%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1764035%22%20slang%3D%22en-US%22%3EI%20finally%20figured%20out%20why%20we%20had%20problems..%20I%20should%20have%20posted%20this%20sooner..%20Someone%20had%20pushed%20a%20GPO%20that%20messed%20up%20the%20SXS%20stack..%20Specifically%20a%20GPO%20that%20enabled%20the%20following%20setting%3A%20%22Configure%3A%20Computer%20Configuration%20%26gt%3B%20Administrative%20Templates%20%26gt%3B%20Windows%20Components%20%26gt%3B%20Remote%20Desktop%20Services%20%26gt%3B%20Remote%20Desktop%20Session%20Host%20%26gt%3B%20Application%20Compatibility%20Turn%20off%20Windows%20Installer%20RDS%20Compatibility%20-%20enabled%22%3CBR%20%2F%3EThat%20was%20enough%20to%20break%20WVD..%20We%20removed%20that%2C%20and%20everything%20started%20working%20properly.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1771344%22%20slang%3D%22en-US%22%3ERe%3A%20Can%20not%20connect%20to%20WVD%20RDS%20session%20host%20unavailable%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1771344%22%20slang%3D%22en-US%22%3E%3CP%3EI've%20noticed%20this%20on%20a%20few%20deployments%20so%20far.%3C%2FP%3E%3CP%3EI%20would%20log%20into%20the%20session%20host%20with%20the%20issue%20and%2C%20run%20qwinsta%20and%20find%20that%20the%20SxS%20stack%20wasn't%20loaded.%3C%2FP%3E%3CP%3EI%20would%20programs%20and%20features%20for%20any%20updates%20and%20find%20that%20a%20new%20version%20of%20the%20SxS%20stack%20was%20installed%20but%20the%20old%20version%20would%20still%20be%20there.%20I%20uninstall%20the%20old%20version%20and%20leave%20the%20new.%20Reboot%20and%20we're%20back.%20Still%20gathering%20more%20info%20to%20see%20if%20this%20is%20the%20actual%20fix%20or%20just%20a%20lucky%20reboot.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Contributor

I created a new WVD for a customer this morning using the newly updated image.

 

using get-rdssessionhost

 

status says unavailable I can see the session desktop in the html5 browser but it does not connect. No errors on the join process 

12 Replies

Unavailable is reported for cases where service is unable to reach the VM to establish the connections. This can happen when either the VM is shutdown or if there are issues with domain, network or agent. Can you ensure VM is booted up and get us output of following two commands:

 

Get-RdsSessionHost -TenantName <TenantName> -HostPoolName <HostPool> -Name <hostname>

 

$h = Get-RdsSessionHost -TenantName <TenantName> -HostPoolName <HostPool> -Name <hostname>
ConvertFrom-Json $h.SessionHostHealthCheckResult  

Take one of the following actions to resolve.

Manually add the VMs to a domain.

Redeploy the template once credentials have been confirmed. See Create a host pool with PowerShell.

Join VMs to a domain using a template with Joins an existing Windows VM to AD Domain.

I got it fixed i appreciate all the replies

Hi @tommy_barnes , 

 

can you share your solution or what things you did that finally fixed it ?

@tommy_barnes 

 

Hi Tommy,

 

What did you do to fix it?  Do you have a link or something you could share?

Thanks,

Mike

@no-va  

 

Sorry for the late response.  I ended up deleting the setup and recreated setup all from powershell and then i set up everything

Can you elaborate on what you did to troubleshoot the issue? I ran into the same issue @tommy_barnes 

I had a similar issue. After deploing our custom image, the RDS session hosts wold become unavailable.
We used Win 10 multi session as the base, the 2004 build. I traced the issue back the RD agent deployment. The SxS stack was not enabled.. I loggd into the session host via the bastion connection. Everything was fine. No major errors anywhere. I noticed that we had multiple versions of the we had multiple versions of the Remote Desktop Services INfrastructure Agent installed. I removed the old ones and kept the newest one.  I re-ran the script in the C:\DeployAgent\EnableSxSStackScript folder to register/start the Sxs stack and restarted the machine. It should have been registered/started on the initital deployment, but for some reason it didn't trigger.. I'm still trying to figure out why. That appears to do the trick for us.

 

I finally figured out why we had problems.. I should have posted this sooner.. Someone had pushed a GPO that messed up the SXS stack.. Specifically a GPO that enabled the following setting: "Configure: Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Application Compatibility Turn off Windows Installer RDS Compatibility - enabled"
That was enough to break WVD.. We removed that, and everything started working properly.

I've noticed this on a few deployments so far.

I would log into the session host with the issue and, run qwinsta and find that the SxS stack wasn't loaded.

I would programs and features for any updates and find that a new version of the SxS stack was installed but the old version would still be there. I uninstall the old version and leave the new. Reboot and we're back. Still gathering more info to see if this is the actual fix or just a lucky reboot.