Forum Discussion
Can not connect to WVD RDS session host unavailable
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 ...
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.
