We see this error rather intermittently in our environment. I wouldn't even say we see it often. When it happens, as far as we know, there are no environmental issues going on. Typically we'll see the user having the issue is actually already on a session, listed as connected in the View Admin console. What we'll then do is reset that VM, then have them authenticate again, and it seems to work. But it's kind of annoying for the user to open a ticket for such an issue. Is it something perhaps to do with the end user's connection (weak wireless signal maybe wherever they are)? Or is it something perhaps with our Horizon config we should check for. Would love to know what the root cause is that gets them to that state.
We are using today Horizon 6.2.0. Our Windows users are instructed to get whatever the latest version of the client is available.
Thanks.
