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.
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?
Sometimes, group policy settings or AD permissions might also be blocking the join process, so you can check there are no restrictions, but probably as you sai, since the feature is in preview, it’s possible that there are bugs, so maybe ther is no mor option to check for updates . As a workaround, you can consider using a custom script to manually join the session host to the domain when automation fails. I never had this specific issue or usecase, so I cannot help you further!