Forum Discussion
tomdw
Nov 02, 2022Brass Contributor
Anyone experiencing session hosts becoming unavailable at random
Since the end of last week we have had three occasions where one of the session hosts randomly becomes unavailable. This happened in two separate AVD environments. Users get kicked out of their ses...
KristofH
Nov 16, 2022Brass Contributor
I don't see that warning anymore on our session hosts. (Others yes, but not that one)
KristofH
Nov 16, 2022Brass Contributor
Correction! We still see that error when the RDAgent version is 1.0.5555.1008, we don't see it on the downgraded versions. I will report this to Microsoft in our ticket also.
- fev17Nov 16, 2022Copper ContributorWhat is still interesting about our error that still exists.
Windows User with Remote Desktop Client: Connection NOT possible
Windows User via Web: Connection possible
Mac User with Remote Desktop Client: Connection possible
Mac User via Web: Connection possible
Same Session Host.
Agent version 1.0.5555.1008
Defender version 4.18.2210.6- KristofHNov 16, 2022Brass ContributorStrange! If you have a case open with MS, please talk to me in private message, don't mind sharing our MS ticket numbers..
- KristofHNov 16, 2022Brass Contributor
KristofH FYI, the feedback I got from Microsoft after mentioning this:
I see this error, Microsoft.RDInfra.RDAgent.Service.AgentUpdateStateImpl too on my Lab. I have questioned the SME and this error does not impact at all the agent. Is just a warning for the agent updater.
This error is showing because the agent tries to check the repository if they have a new agent and, if they don’t have any new one, they have this unexpected error. When they have a new on the repository, they update without any issue.
I of course responded I find this "not normal" as this only occurs since this version and it also occurs 6 times in 2 minutes. And it shouldn't be a warning.