Forum Discussion
AVD NEW desktop client version 1.0.5555.600 now shows SHUTDOWN status on Pool Host
Christian1990 I just removed the newest version. Then stopped the rdbootloader service from task manager then then installed the newest version of the desktop agent I could find for download, it was only 1.0.4x When I uninstalled the 1.0.5555.600 version it made my pool host unavailable until I reinstalled the older version. I thought it would still work as it keeps 3 versions on at a time for this exact use scenario. I think the issue is there was new SxS updates also and must do something a bit different then the past. I hope this helps you.
Robert_Hurd I resolved the issue doing these steps:
1- First check that in the host pool that the test environment is unselected.
2- Remove the session host from the host pool and install the boot agent and rdinf agent.
3- Reboot the session host and install rdinf agent and boot agent the version will be 1.0.4x how you said. You can download it from this link HTTPS: //learn.microsoft.com/en-us/azure/virtual-desktop/create-host-pools-powershell?tabs=azure-powershell#register-the-virtual-machines-to-the-azure-virtual-desktop-host-pool.
4- check that the session host appears in the host pool.
I suspect that the host pool check how test environment upgrade the agent to the version 1.0.5555.
Regards.
- Robert_HurdSep 22, 2022Brass ContributorYes, seems that validation environments are automatically being upgraded to this new desktop agent. Would still like Microsoft to weigh in if this "shutdown" status is expected behavior?
- ChrisCoduxSep 26, 2022Copper Contributor
#1 more for the agent downgrade. God knows who enabled the Validation environment on the production host pool
The Azure Virtual Desktop Agent Troubleshooting Guide has a decent step by step process for installing the agent.- Robert_HurdSep 26, 2022Brass ContributorTested on another pool, by just taking the validation property off the pool is downgraded automatically.
- Nivek_LauSep 27, 2022Copper Contributor
hi robert, do you mean after you turn off the validation option in the property, the start VM on connect works fine with the new agent version?