Forum Discussion

cwljack's avatar
cwljack
Copper Contributor
Nov 06, 2019

No Heartbeat on Session Host after shutdown

I've been trialing WVD and followed the Microsoft guides to setup.

 

I've then expanded the trial to include a custom image using the guide here:

https://www.robinhobo.com/how-to-create-a-custom-windows-10-multi-user-image-with-lob-applications-for-windows-virtual-desktop-preview-wvd-hostpool-deployments/

 

Last night I shutdown the session host, powered up this morning and attempted to run:

 

Get-RdsStartMenuApp <tenantname> <hostpoolname> "RemoteApp Application Group"

 

Which gave the error "Get-RdsStartMenuApp : There are no Session Hosts available in the HostPool to service the Start Menu request"

 

Then ran: Get-RdsSessionHost <tenantname> <hostpoolname>

 

Which showed:

 LastHeartBeat : 05/11/2019 20:40:59
AgentVersion : 1.0.1486.900
AssignedUser :
OsVersion : 10.0.18362
SxSStackVersion : rdp-sxs190905003
Status : NoHeartbeat
UpdateState : Succeeded
LastUpdateTime : 05/11/2019 20:37:26
UpdateErrorMessage :

 

Have checked the vm and confirmed that the RDAgentBootLoader service is started as suggested on other threads.

 

What should be the next steps I need to be taking to troubleshoot this? 

 

For now, as it's a test environment redeploying the host pool seems to resolve but if I were to use this in production I would expect to use azure automation to power down unused VM's outside of business hours to reduce compute costs.

 

WVD

9 Replies

  • Christian_Montoya's avatar
    Christian_Montoya
    Icon for Microsoft rankMicrosoft
    Dec 30, 2019

    cwljack : Your instincts and actions are correct, and we definitely suggest to power down VMs when not using them. Have you hit this again recently? We were seeing some sporadic agent errors back in November, so likely this is fixed, if you're able to test again.

    • Mrossi's avatar
      Mrossi
      Copper Contributor
      Feb 24, 2020

      Hi Christian_Montoya,

       

      I have same issues on Application Pool and Desktop Pool. Agent is running perfectly until first connection and First reboot, after that Agent is in NoHeartBeat Status on WVD

       

       

      I found this Warning in EventViewer on my Virtual Machine wvd-dev-30

      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

       

      Do you have any case on this error ? do you need more information ?

       

      Matthieu

       

       

      • Christian_Montoya's avatar
        Christian_Montoya
        Icon for Microsoft rankMicrosoft
        Feb 24, 2020

        Mrossi : Thanks for bringing this up! At the moment, I'm unaware of similar cases. Can you file a support ticket for Windows Virtual Desktop through the Azure Portal? This will help us better triage and dive into this.

    • cwljack's avatar
      cwljack
      Copper Contributor
      Jan 14, 2020

      Christian_Montoya: Thanks for coming back to me, the original environment was deleted but I've built a new test environment and created two host pools.

       

      One is running Windows Server 2016 built from the gallery image and one is the multi session image of Windows 10 slightly customised with some basic LOB applications and deployed from blob storage.

       

      This afternoon I stopped and de-allocated both VM's from the Azure portal and when I've started them back up this evening and ran Get-RDSSessionHost and this is showing as available now so it does look like the issue is resolved.

Resources