Forum Discussion
Started a few days ago at most: Agent on Session host no longer communicates properly with WVD
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.
I am also having this issue, screenshot of the rdsSessionHost, working yesterday failing today. I ahve tried rebooting the desktops.
MicrosoftWe do have the same problem as described by GuyPaddock. Session host starts with status 'Available' and that changes shortly after to 'NoHeartbeat'. Consequently our users did get the '...no available resources' message. As said restarting the RdAgentBootloader service helps, for a minute...
'Hope this will be solved soon.
- Roop_Kiran_Chevuri
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.
No worries,
Yesterday I set up a fresh pool of dedicated machines, I entitled three users and they logged in successfully. All three users haven't done anything more than login and open a webbroswer
This morning, we are unable to connect with any of the users, we can connect to the pool gateway but none of the session hosts.
- Roop_Kiran_Chevuri
soloji 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.
Roop_Kiran_Chevuri Reiterating what was written above -- all session hosts start out as "Available" up to 1 min after boot, and then fall into "NoHeartbeat" status. Once this happens, it's not possible to connect to the host pool using Remote Desktop -- it displays this message:
If new session host VMs are created from an image that worked back in May, as soon as they update to Remote Desktop Services Infrastructure Agent 1.0.1006.2006, they drop to "NoHeartbeat" status after 1 min. Restarting the new session hosts exhibits the same behavior as the existing session hosts -- they only stay Available for up to 1 min after boot.
- Roop_Kiran_Chevuri
GuyPaddock 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.
- I can confirm that after disabling my scheduled task and then monitoring the output of Get-RdsSessionHost over the last five minutes, I no longer see NoHeartbeat status! In addition, the LastHeartBeat is updating consistently every 30 secs now.
