Forum Discussion
Add or Update Session Host failed
I spoke with the the product team today and my specific issue was related to the our key vault configuration.
TLDR (Key Vault requires public network access to be enabled for the credentials to be retrieved)
The process that runs the domain join is now a part of the RD host session host agent. Previously it could access your Key Vault using "Azure Resource Manager for template deployment". There is an existing limitation with this new agent approach which requires public network be enabled for your key vault to retrieve the domain join secrets.
Hello,
In my opinion, there may be many reasons why session hosts fail to join the domain. The common ones for me include connectivity issues with the domain controller, incorrect DNS settings, or changes in Active Directory policies. It’s also possible that the image template wasn’t properly Sysprepped, or the domain join credentials in Azure are incorrect or maybe they lack sufficient permissions.
Check the NetSetup log for detailed errors and also ensure that the Azure Virtual Desktop agent is up to date. If manual domain join works, you can compare it with the automated process to identify differences. If none of these resolve the issue, you can try to review Azure activity logs and consider contacting Microsoft Support for further investigation.
Hope it helps!
Hi,
All the suggestions you mentioned have already been checked, and everything is fine.When I check the NetSetup log in C:\Windows\debug, I can see that there was no attempt to join the domain. It seems as though the workflow responsible for adding the VD to the host pool, installing the AVD agents, etc., stops before attempting to join the VD to the domain and leaves it in this incomplete state.
Do you know where I can find logs on the VD that could help me better understand why the workflow didn’t complete?
Hello,
If i'm not wrong the VD agent logs are in C:\ProgramData\Microsoft\Azure\Config\AVDLogs\ and also you can check the RDAgentBootLoader log in C:\Windows\Temp\RDAgentBootLoader.log. These should provide you some insights about where the process failed. Additionally, reviewing the Event Viewer (Application and System logs) on the VM and Azure Activity Logs in the portal might help pinpoint the issue.
Let me know what you find! I hope it helps, cause I'm running out of ideas =)Hello Luchete,
To expand further this doesn't present like a problem with the RD Agent installation as my session hosts are registering correctly with the host pool.
This issue seems to be entirely the with the "session host configuration" feature (in Preview...) which lets you build a configuration to automate the lifecycle of your session hosts. There is an Active Directory domain join component (shared in the screenshot attached) that for whatever reason isn't triggering or failing.
But the mystery is there are no failure logs in either the Deployment or on the Session host itself?