Forum Discussion

Johan_Eriksson's avatar
Johan_Eriksson
Brass Contributor
Aug 13, 2019
Solved

Started a few days ago at most: Agent on Session host no longer communicates properly with WVD

My host pool and tenant are probably from the May timeframe. The agent has version 1.0.1006.2006.   I notice that the agent posts a heartbeat on a restart of session host and then no more.   When...
  • Roop_Kiran_Chevuri's avatar
    Roop_Kiran_Chevuri
    Aug 15, 2019

    ClearForward Thanks for reporting the issue. This is service side issue and we have fixed it few minutes back. Can you please verify if it working now. We would like to further investigate if that's not the case. Thanks.

GuyPaddock's avatar
GuyPaddock
Brass Contributor
Aug 14, 2019

Johan_Eriksson I'm having what I think is a related issue. Our setup is also from May 2019, and in the last 48 hours we're having constant issues.

 

Ever since our virtual desktop VMs auto-updated to Remote Desktop Services Infrastructure Agent 1.0.1006.2006, they keep falling into a bad state of "NoHeartbeat" after only a few minutes. When the VMs first boot, the status is "Available" and "LastHeartBeat" reflects the time of boot. We're able to connect to the pool without issue and can maintain sessions, but cannot start new sessions because the status changes to "NoHeartbeat".

 

If an admin restarts the "RDAgentBootloader" service, the status changes to "Available" and "LastHeartBeat" reflects the time of the service restart.

 

For reference, I am checking on the status of the pool with the "Get-RdsSessionHost" cmdlet.

GuyPaddock's avatar
GuyPaddock
Brass Contributor
Aug 15, 2019
As a quick workaround for my issue, I'm had to setup a task with Task Scheduler that runs NET STOP and NET START of RdAgentBootloader every 1 min, starting at system boot and continuing indefinitely. This gives us about 55 seconds out of every minute where the session hosts are "Available", and 5 seconds where they're "NoHeartbeat". It's an awful hack, but it's better than nothing until MSFT can push a version of the RD Agent that can actually post heartbeats.
  • iconicmlee's avatar
    iconicmlee
    Copper Contributor
    Aug 15, 2019
    Do you mind sending me your task scheduler settings please. I am in a bind and would like to get through the testing of the task scheduler you already did by reaching out. Thanks a million! GuyPaddock
    • GuyPaddock's avatar
      GuyPaddock
      Brass Contributor
      Aug 15, 2019

      One other power user tip: I found a Powershell cmdlet that makes it really easy to monitor the status of the session hosts so you can see the scheduled task in action.

       

      You can get the cmdlet here:
      http://wragg.io/watch-for-changes-with-powershell/

       

      You can run it to monitor session hosts this way:

      { Get-RdsSessionHost -TenantName "TENANT" -HostPoolName "HOST POOL" } | Watch-Command -Verbose -Continuous

       

      If any values like status, heartbeat time, session count, etc change, it prints the output.

    • GuyPaddock's avatar
      GuyPaddock
      Brass Contributor
      Aug 15, 2019

      iconicmlee Sure!

       

      I believe you will need to configure the task to run with highest privs under an admin account, since it needs to be able to stop and start system services:

      <?xml version="1.0" encoding="UTF-16"?>
<Task version="1.2" xmlns="<a href="http://schemas.microsoft.com/windows/2004/02/mit/task" target="_blank">http://schemas.microsoft.com/windows/2004/02/mit/task</a>">
  <RegistrationInfo>
    <Date>2019-08-14T17:06:39.646478</Date>
    <Author>CLOUD\guy</Author>
    <URI>\ITSA-46 Workaround</URI>
  </RegistrationInfo>
  <Triggers>
    <BootTrigger>
      <Repetition>
        <Interval>PT1M</Interval>
        <StopAtDurationEnd>false</StopAtDurationEnd>
      </Repetition>
      <Enabled>true</Enabled>
    </BootTrigger>
  </Triggers>
  <Principals>
    <Principal id="Author">
      <UserId>S-1-5-21-2615066866-973913876-715106564-1108</UserId>
      <LogonType>Password</LogonType>
      <RunLevel>HighestAvailable</RunLevel>
    </Principal>
  </Principals>
  <Settings>
    <MultipleInstancesPolicy>IgnoreNew</MultipleInstancesPolicy>
    <DisallowStartIfOnBatteries>true</DisallowStartIfOnBatteries>
    <StopIfGoingOnBatteries>true</StopIfGoingOnBatteries>
    <AllowHardTerminate>true</AllowHardTerminate>
    <StartWhenAvailable>false</StartWhenAvailable>
    <RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>
    <IdleSettings>
      <StopOnIdleEnd>true</StopOnIdleEnd>
      <RestartOnIdle>false</RestartOnIdle>
    </IdleSettings>
    <AllowStartOnDemand>true</AllowStartOnDemand>
    <Enabled>true</Enabled>
    <Hidden>false</Hidden>
    <RunOnlyIfIdle>false</RunOnlyIfIdle>
    <WakeToRun>false</WakeToRun>
    <ExecutionTimeLimit>PT72H</ExecutionTimeLimit>
    <Priority>7</Priority>
  </Settings>
  <Actions Context="Author">
    <Exec>
      <Command>NET</Command>
      <Arguments>STOP RdAgentBootloader</Arguments>
    </Exec>
    <Exec>
      <Command>NET</Command>
      <Arguments>START RdAgentBootloader</Arguments>
    </Exec>
  </Actions>
</Task>

       

      • GuyPaddock's avatar
        GuyPaddock
        Brass Contributor
        Aug 15, 2019
        Also: once the task is created, you have to restart the VM to kick it off. Just running the task manually doesn't cause it to recur. It also seems like editing the task causes it to stop running until the next reboot.

Resources