Forum Discussion

andersidahl's avatar
andersidahl
Brass Contributor
Mar 25, 2019

RD Session Host stuck at Status: "Upgrading"

Hi, I am trying to add a Windows Server 2016 as a session host. I have followed the steps at: https://docs.microsoft.com/en-us/azure/virtual-desktop/create-host-pools-powershell and it shows up as a s...
andersidahl's avatar
andersidahl
Brass Contributor
Mar 26, 2019

evasse Hi Eva, thanks for reaching out.

 

I am not deploying with a template, that one works fine. I am trying to deploy to a Windows Server 2016 previously deployed.

 

The steps done are from: https://docs.microsoft.com/en-us/azure/virtual-desktop/create-host-pools-powershell. Everything seems to go fine with all steps, except that we are unable to connect after doing such steps and also when running the Get-RdsSessionHost it shows the agent as still updating. On the server its also some events which shows some error, I could send that directly if you have a secure drop for that?

 

Best regards, Anders

alhenriq_ms's avatar
alhenriq_ms
Icon for Microsoft rankMicrosoft
Apr 02, 2019

andersidahl 

Hi Anders,

 

The above exception, to me, indicates that the bootloader cannot find the agent because the required location is missing a registry key (Unable to retrieve DefaultAgent path from registry).

 

After installing the WVD Agent - it should have declared itself the default agent by creating this key in the AgentBootLoader regkey location HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\RDAgentBootLoader -> DefaultAgent

 

Can you verify that this key exists? Also please make sure you stop the AgentBootLoader service before trying to install the WVD Agent MSI.

 

thanks,

-al

 

 

 

  • andersidahl's avatar
    andersidahl
    Brass Contributor
    Apr 02, 2019

    alhenriq_ms 

     

    Hi, I can verify that this was already tested. I also tried pulling the newer versjon setup from another server-setup that worked and installing manually and changing the registerkey, but it kept reconfiguring back to 1.6/1.7 i believe the version was. Also a lot of reboots inbetween and waiting, though it kept going back to Upgrading.

    • alhenriq_ms's avatar
      alhenriq_ms
      Icon for Microsoft rankMicrosoft
      Apr 02, 2019

      andersidahl 

       

      Ok I misunderstood, I thought you had issues with the bootloader loading the agent. I can check your logs from my end, if you like. You can send me your VM name (FQDN helps)  via Private Message.

       

      thanks,

      -al

      • aspicola2605's avatar
        aspicola2605
        Copper Contributor
        Apr 04, 2019

        alhenriq_ms 

        andersidahl 

         

        It looks like the RDAgent on the doc for manually configuring is different than the version being pushed using the deployment for a host pool. The downloaded agent version appears to be 1.0.0.1462 and the version of the agent on the provisioned host pools is 1.0.1.10. It seems to upgrade it automatically but never complete for one reason or another.

         

        The boot loader and sxs installers don't have version numbers in them that I can find to confirm they are the same.

         

        Is there a download link for the correct agent version?

Resources