Forum Discussion
Session hosts changed from 'Unavailable' to 'Shutdown'
Sometime last Thursday, every Host pool in both of our Subscriptions changed the Session host Status from 'Unavailable' to 'Shutdown'.
None of the Host pools are Validation environments. All the Session hosts are running Agent version 1.0.6129.9100, which we have been running this version for several weeks now.
Is this a scheduled UI change that just now affected our Subscriptions and Host pools?
9 Replies
- Hi Arthur1900
The change in session host status from 'Unavailable' to 'Shutdown' could be caused by several factors, but it's not likely to be a scheduled UI change. Here are some possible reasons and troubleshooting steps to help you identify the cause:
- Check if there were any changes to the Azure Virtual Desktop (AVD) environment or subscription that could have triggered this behavior. Look for changes in resources, configurations, or updates that happened around the time the issue started.
- Verify if the virtual machines (VMs) have been deallocated or shut down in the Azure portal. If the VMs are in a shutdown or deallocated state, this could explain the change in status. In this case, you'll need to start the VMs again.
- Check the AVD agent logs on the affected session hosts for any errors or warnings. The logs can be found in the following location:
%SystemRoot%\System32\config\systemprofile\AppData\Local\rdagent\
Reviewing the logs may help you identify any issues with the agent or its communication with the AVD service.
- Ensure that the AVD agent and the associated boot loader are both updated to the latest version. If they are outdated, update them and check if the issue persists.
- Check the event logs on the session hosts, especially the 'Microsoft-RdInfra-RdAgent' and 'Microsoft-RdInfra-SessionHost' event logs, for any errors or warnings that could provide insight into the problem.
- If the issue persists, try creating a new host pool and VM to see if the issue affects the new resources. If the new resources are also affected, it could be an issue with the AVD service or the subscription.
- Reach out to Microsoft Support for further assistance if you're unable to identify the cause of the issue.
By investigating these factors, you should be able to pinpoint the cause of the change in session host status and find an appropriate solution.- It is every single Host pool, every single Session host and in both of our subscriptions.
So no, the things you’re asking for it is not needed to be done. Something globally was changed by Microsoft.- Arthur1900
I apologize if my previous response wasn't helpful in your specific situation. If you believe this issue is a result of a global change by Microsoft, it's important to get in touch with their support team as soon as possible to report the issue and seek assistance.
You can reach out to Microsoft Support through the Azure portal or by visiting their support website (https://support.microsoft.com/). Be sure to provide them with details about your Subscriptions, Host pools, and Session hosts, and explain that you believe this issue is related to a global change made by Microsoft. This information will help them understand the scope and impact of the problem and prioritize their investigation.
Additionally, keep an eye on Microsoft's Azure updates (https://azure.microsoft.com/en-us/updates/) and Azure service health dashboard (https://portal.azure.com/#blade/Microsoft_Azure_Health/AzureHealthBrowseBlade/overview) for any relevant announcements or known issues. If other customers are experiencing similar problems, it's likely that Microsoft will provide information about the issue and their efforts to resolve it through these channels.
Again, I apologize if my previous response was not helpful, and I hope you are able to find a resolution to this issue with the help of Microsoft Support.
- I've also noticed this in my environment with 6 AVDs. Looks like the new agent is doing something new. We also hade problems with AVD reboots daily. Some of the hosts came unvailable after scheduled reboot.
- We have also noticed this as of late. I'm assuming it is a UI change.
I like it, in the way that it's more accurate. I'd like if it could be a 'live' status too, eg. showing 'Starting' when the scaling plan starts booting up more machines.
Is there no official note of this change?- Can’t find any release notes. I also looked at https://learn.microsoft.com/en-us/azure/virtual-desktop/whats-new
Seems not, would suggest raise a ticket to Microsoft support when more than one hots being affected
