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 session host with PS with the Get-RdsSessionHost command, but the status in the output is stuck at Status : Upgrading. In the event logs in gives a bunch of errors, these are a couple of them: Events: Microsoft.RDInfra.Agent.Monitoring.MonitoringAgentInstallSettings Value of the 'AgentMonitoringAuthId' is empty Microsoft.RDInfra.Agent.Monitoring.MonitoringAgentInstallSettings RDInfraAgent key doesn't exist Unable to retrieve DefaultAgent from registry: System.NullReferenceException RDAgentBootLoader.BootLoaderSettings.get_DefaultAgentPath() i C:\agent\_work\1\s\src\RDAgent\src\RDAgentBootLoader\BootLoaderSettings.cs:rad 82

andersidahl: Can you please re-run the template and create a new host pool? Delete the existing one it got into a bad state. If this happens again please let us know as we would like to get into the root cause of those issues.

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

andersidahl I am in the same boat. Everything works fine with the template but I would like to be able to automate the creation of my own Session Hosts and can get everything moving to the point of where the RD Session Host is stuck with the Status: Upgrading. Status remained the same overnight. Anyway we can check what could be failing. RDSDiagnosticActivities does not seem to have anything regarding the failing of that registration process.

Checking Event Viewer, I see that the Remote Desktop Services SxS Network Stack is stuck in some sort of loop where the Session Host keeps re-running the MSI installer and re-configures the installed RDS SxS Network Stack product every 5 minutes: Log Name: ApplicationSource: Microsoft-Windows-RestartManagerDate: 3/28/2019 2:32:50 PMEvent ID: 10001Task Category: NoneLevel: InformationKeywords: User: SYSTEMComputer: wvdhost.test.comDescription:Ending session 0 started ‎2019‎-‎03‎-‎28T14:32:48.506934400Z.Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="Microsoft-Windows-RestartManager" Guid="{}" /><EventID>10001</EventID><Version>0</Version><Level>4</Level><Task>0</Task><Opcode>0</Opcode><Keywords>0x8000000000000000</Keywords><TimeCreated SystemTime="2019-03-28T14:32:50.599897100Z" /><EventRecordID>552</EventRecordID><Correlation /><Execution ProcessID="5600" ThreadID="2720" /><Channel>Application</Channel><Computer>wvdhost.test.com</Computer><Security UserID="" /></System><UserData><RmSessionEvent xmlns="http://www.microsoft.com/2005/08/Windows/Reliability/RestartManager/"><RmSessionId>0</RmSessionId><UTCStartTime>2019-03-28T14:32:48.506934400Z</UTCStartTime></RmSessionEvent></UserData></Event>Log Name: ApplicationSource: MsiInstallerDate: 3/28/2019 2:32:50 PMEvent ID: 1042Task Category: NoneLevel: InformationKeywords: ClassicUser: SYSTEMComputer: wvdhost.test.comDescription:Ending a Windows Installer transaction: C:\Program Files\Microsoft RDInfra\SxSStack-1.0.1902.17001.msi. Client Process Id: 4400.Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="MsiInstaller" /><EventID Qualifiers="0">1042</EventID><Level>4</Level><Task>0</Task><Keywords>0x80000000000000</Keywords><TimeCreated SystemTime="2019-03-28T14:32:50.622450000Z" /><EventRecordID>551</EventRecordID><Channel>Application</Channel><Computer>wvdhost.test.com</Computer><Security UserID="" /></System><EventData><Data>C:\Program Files\Microsoft RDInfra\SxSStack-1.0.1902.17001.msi</Data><Data>4400</Data><Data>(NULL)</Data><Data>(NULL)</Data><Data>(NULL)</Data><Data>(NULL)</Data><Data></Data></EventData></Event>Log Name: ApplicationSource: MsiInstallerDate: 3/28/2019 2:32:50 PMEvent ID: 1035Task Category: NoneLevel: InformationKeywords: ClassicUser: SYSTEMComputer: wvdhost.test.comDescription:Windows Installer reconfigured the product. Product Name: Remote Desktop Services SxS Network Stack. Product Version: 1.0.1902.17001. Product Language: 1033. Manufacturer: Microsoft Corporation. Reconfiguration success or error status: 0.Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="MsiInstaller" /><EventID Qualifiers="0">1035</EventID><Level>4</Level><Task>0</Task><Keywords>0x80000000000000</Keywords><TimeCreated SystemTime="2019-03-28T14:32:50.591183400Z" /><EventRecordID>550</EventRecordID><Channel>Application</Channel><Computer>wvdhost.test.com</Computer><Security UserID="" /></System><EventData><Data>Remote Desktop Services SxS Network Stack</Data><Data>1.0.1902.17001</Data><Data>1033</Data><Data>0</Data><Data>Microsoft Corporation</Data><Data>(NULL)</Data><Data></Data><Binary></Binary></EventData></Event>Log Name: ApplicationSource: MsiInstallerDate: 3/28/2019 2:32:50 PMEvent ID: 11728Task Category: NoneLevel: InformationKeywords: ClassicUser: SYSTEMComputer: wvdhost.test.comDescription:Product: Remote Desktop Services SxS Network Stack -- Configuration completed successfully.Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="MsiInstaller" /><EventID Qualifiers="0">11728</EventID><Level>4</Level><Task>0</Task><Keywords>0x80000000000000</Keywords><TimeCreated SystemTime="2019-03-28T14:32:50.575597200Z" /><EventRecordID>549</EventRecordID><Channel>Application</Channel><Computer>wvdhost.test.com</Computer><Security UserID="" /></System><EventData><Data>Product: Remote Desktop Services SxS Network Stack -- Configuration completed successfully.</Data><Data>(NULL)</Data><Data>(NULL)</Data><Data>(NULL)</Data><Data>(NULL)</Data><Data>(NULL)</Data><Data></Data><Binary></Binary></EventData></Event>Log Name: ApplicationSource: Microsoft-Windows-RestartManagerDate: 3/28/2019 2:32:48 PMEvent ID: 10000Task Category: NoneLevel: InformationKeywords: User: SYSTEMComputer: wvdhost.test.comDescription:Starting session 0 - ‎2019‎-‎03‎-‎28T14:32:48.506934400Z.Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="Microsoft-Windows-RestartManager" Guid="{}" /><EventID>10000</EventID><Version>0</Version><Level>4</Level><Task>0</Task><Opcode>0</Opcode><Keywords>0x8000000000000000</Keywords><TimeCreated SystemTime="2019-03-28T14:32:48.518299200Z" /><EventRecordID>548</EventRecordID><Correlation /><Execution ProcessID="5600" ThreadID="6308" /><Channel>Application</Channel><Computer>wvdhost.test.com</Computer><Security UserID="" /></System><UserData><RmSessionEvent xmlns="http://www.microsoft.com/2005/08/Windows/Reliability/RestartManager/"><RmSessionId>0</RmSessionId><UTCStartTime>2019-03-28T14:32:48.506934400Z</UTCStartTime></RmSessionEvent></UserData></Event>Log Name: ApplicationSource: MsiInstallerDate: 3/28/2019 2:32:48 PMEvent ID: 1040Task Category: NoneLevel: InformationKeywords: ClassicUser: SYSTEMComputer: wvdhost.test.comDescription:Beginning a Windows Installer transaction: C:\Program Files\Microsoft RDInfra\SxSStack-1.0.1902.17001.msi. Client Process Id: 4400.Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="MsiInstaller" /><EventID Qualifiers="0">1040</EventID><Level>4</Level><Task>0</Task><Keywords>0x80000000000000</Keywords><TimeCreated SystemTime="2019-03-28T14:32:48.491308300Z" /><EventRecordID>547</EventRecordID><Channel>Application</Channel><Computer>wvdhost.test.com</Computer><Security UserID="" /></System><EventData><Data>C:\Program Files\Microsoft RDInfra\SxSStack-1.0.1902.17001.msi</Data><Data>4400</Data><Data>(NULL)</Data><Data>(NULL)</Data><Data>(NULL)</Data><Data>(NULL)</Data><Data></Data></EventData></Event> Any thoughts?

Same problem here. It seems like the agent is upgrading immediately after installing. I now have two versions of the agent installed.I tried uninstalling the agent and re-installing using what looks like an upgraded installer (version 1.0.1.10) but now instead of Status: Upgrading, my RD host is in Status: Unavailable. Also have these additional errors in the RemoteDesktopServices-MonitoringLogger and RemoteDesktopServices-MonitoringAgentLoader logs respectively Microsoft.RDInfra.Monitoring.AgentMonitoringService.AgentMonitoringServiceWorkerValue of the 'AgentMonitoringAccount' in 'SOFTWARE\Microsoft\RDMonitoringAgent' is empty-------Microsoft.RDInfra.Monitoring.AgentMonitoringService.AgentMonitoringServiceWorkerFail to set default dimensions Invalid Operation: Fail to set default dimensions, error code is 2147942487.. Error code is 80070057

RD Session Host stuck at Status: "Upgrading"

17 Replies

DBR14
Iron Contributor
Dec 28, 2021
This garbage still happens even today. At least every other day to one of our hosts. We're running the newer VMs generations too - D16sv4's. Sometimes it'll upgrade with people connected and just create so many headaches, or it'll upgrade and get stuck and then nobody can log into it, but it registers as open sessions so my auto-scale logic doesn't open up more machines and again, creates issues. Figure it out...
- evasse
  Former Employee
  Dec 28, 2021
  Please reach out to support for debugging. THank you
Stephen Ferrero
Copper Contributor
Apr 01, 2019
Same problem here. It seems like the agent is upgrading immediately after installing. I now have two versions of the agent installed.

I tried uninstalling the agent and re-installing using what looks like an upgraded installer (version 1.0.1.10) but now instead of Status: Upgrading, my RD host is in Status: Unavailable.

Also have these additional errors in the RemoteDesktopServices-MonitoringLogger and RemoteDesktopServices-MonitoringAgentLoader logs respectively

Microsoft.RDInfra.Monitoring.AgentMonitoringService.AgentMonitoringServiceWorker
Value of the 'AgentMonitoringAccount' in 'SOFTWARE\Microsoft\RDMonitoringAgent' is empty
-------
Microsoft.RDInfra.Monitoring.AgentMonitoringService.AgentMonitoringServiceWorker
Fail to set default dimensions Invalid Operation: Fail to set default dimensions, error code is 2147942487.. Error code is 80070057
- alhenriq_ms
  Microsoft
  Apr 02, 2019
  Stephen Ferrero
  Hi Stephen,
  
  The monitoring agent is reporting this because there was a failure onboarding - please stop the bootloader service and try re-installing the WVD Agent. Verify that the DefaultAgent key exists under
  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\RDAgentBootLoader -> DefaultAgent.
  
  Then start the bootloader service.
  
  thanks,
  -al
  - Stephen Ferrero
    Copper Contributor
    Apr 15, 2019
    alhenriq_ms
    Thanks,
    
    I seem to be OK now after a complete removal and re-install. I see the agent version incremented to 1.0.1.18 so perhaps something has changed.
    
    I do still see duplicated entries in appwiz for the RDS Infrastructure Agent. Looks like the original version I installed, and the updated agent are both still installed.
evasse
Former Employee
Mar 25, 2019
andersidahl: Can you please re-run the template and create a new host pool? Delete the existing one it got into a bad state. If this happens again please let us know as we would like to get into the root cause of those issues.
- 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
    Microsoft
    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

Forum Discussion

RD Session Host stuck at Status: "Upgrading"

17 Replies

Resources