Forum Discussion

Robert_Hurd's avatar
Robert_Hurd
Brass Contributor
Sep 20, 2022

AVD NEW desktop client version 1.0.5555.600 now shows SHUTDOWN status on Pool Host

Some of our host pools have updated to this newer version of the AVD desktop client, and now when we shutdown these hosts the status now shows "Shutdown" instead of "Unavialable".  Is this expected behavior?   The new version also seemed to stop "Start VM on connect" setting from working.  

I uninstalled the 1.0.5555.600 desktop agent and then reinstalled an older version, then got it to auto update and this seemed to fix this issue.  As far as in the past with autoscale scripts, etc, if the VM was in a shutdown state it would not work.  Is this new "Shutdown" status by design?  Also noticed there is no release notes for this version of the AVD desktop agent. 

 

Thanks

 

    • Robert_Hurd's avatar
      Robert_Hurd
      Brass Contributor
      Sep 21, 2022

      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. 

      • Christian1990's avatar
        Christian1990
        Copper Contributor
        Sep 22, 2022

        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.   

  • AzReto's avatar
    AzReto
    Copper Contributor
    Sep 23, 2022

    Robert_Hurd 

    We're facing the same issue with 'Start VM on connect'. this feature does not work anymore since this week.

    Checked Agent version and it also has been updated to '1.0.5555.600'

  • PatrickBrack's avatar
    PatrickBrack
    Copper Contributor
    Sep 23, 2022

    Robert_Hurd 

     

    Same here. "Start VM on Connect" does not work anymore on Hostpools which the agent was updated to version 1.0.5555.600. Also recognized that the VM State now reports "Shutdown" instead of "unavailable". We do have an azure function which shutdowns unused Sessionhosts. Without the start vm on connect feature we cannot use this function to save costs.

     

    Hope this got fixed soon

  • jakejohnson's avatar
    jakejohnson
    Icon for Microsoft rankMicrosoft
    Oct 12, 2022

    Hi Robert_Hur ,

     

    With this agent version the shutdown status did appear more often, and this was intentional. Previously, it was less likely to pop up, but it did exist.

     

    We rolled back this agent version last week, and you should no longer have the Start VM on Connect issue you were seeing before. Going forward, we will release the 'Shutdown' status only as part of new API versions so that nothing in your environment breaks.

    We plan to post release notes for new agent versions on Tech Community in the future, so if you would like to stay up to date, subscribe to those threads when you see them. Thanks for your patience and understanding!