Forum Discussion
MicrosoftHow to troubleshoot Unavailable Status of SessionHost
Martinsd Thanks for opening the support ticket. That is the right approach as we would need to troubleshoot where the failures are coming from by looking at your logs.
Did you get around an solution to this. My problem is similar, I have 2 tenant created and I have 2 host pools . Everytime I build a VM it's resides as unavailable. The agents were reinstalled , but still the problem persists. -- Ayan
Any luck with this? This just suddenly started happening to me today. My test user can connect to the host still despite it saying Unavailable. I can also login with the local admin account via Bastion. But I can't use MSIX App attach as it says none of my hosts have VMs.
Unfortunately, it was a year ago and I built a demo environment that no longer exists. Make sure that the VM is joined in the domain. I had password issues here. You need two passwords for Broker and AD. Make sure all prerequisites are installed. Microsoft has also reworked the management portal. You can now manage wvd in the Azure portal for a longer time. The Powershell patchwork is no longer necessary.
Ha yeah... little aged.
Ours was fine and working, showing available and then yesterday both were unavailable, but we can connect fine. I've uninstalled and reinstalled the agent, bootloader, and did a new reg key, and entered that when I reinstalled the wvd-agent. What I don't get is the link to download the agent appears to be substantially older than the agent listed in the Azure Portal, and it never seems to reflect the Agent version after uninstalling/reinstalling.
