Can you take a picture from you Desktop pool settings ? (Desktop Assignment, entitlement and everything? )
Did you check in this duration (user logoff until error happens) is there any available machine inside your pools? Available means there is some ready machines in your pool... and as the last question, will your VM(desktop) is deleted after user logoff?!Please mark my comment as the Correct Answer if this solution resolved your problem
thank you for your reply. Please find the attached screen shots. Basically yes the users properly logs off and the vDI session is deleted. It happens normally when the user try to get a new vDI session at times. But randomly the user logs off, try to get a vDi session and then the error comes up. Not sure that is causing this. Yes there is plenty of machines available to get another session right away.
Ok can you tell me how you entitle users/groups? each user dedicated to each VM or entitle a group of users to a desktop pool?
And did you ever test it with floating setting in your desktop pool?!
Also check the problem with another type of clients, if you tried with zero/thin client, check it with horizon client or web access....
is there same problem ?Please mark my comment as the Correct Answer if this solution resolved your problem
All user are part of an AD group which they all have Domain Admin rights as well. This is an automatic floating instant clone pool. All users are getting the same indication.
Which basically is that they can log in one time, log off, log in again, log off, then the third time or fourth time they get the network error.
OK with all respect please check this situation with another type of desktop pool (full VM or composer if you can). If the problem still exist, So this can be related to your VDI clients, there may be is an interruption between clients network and horizon view servers.
If issue has been fixed with change of desktop pool type, please review events in connection server when you tried for the third time, is there any errors related to this matter in horizon operational event, or your client device or event desktop VM event viewers?
and please check every horizon view agents installed inside of the deployed VM (from instant clone pool) by logging locally to the VM, maybe there is and stopping/stopped service that be cause of the problemPlease mark my comment as the Correct Answer if this solution resolved your problem
An NSX load balancer configuration was causing this issue. Removed configuration and now vDI pool doesn't show the error anymore. Thank you for all the help!
Any idea as to what setting in the configuration was causing the issue? We are seeing something eerily similar, but we do not use NSX (F5's for us). We notice that users can log into a session fine, but when they log out they are unable to log back in the next day.
On the NSX load balancer, there is a Monitor Session setting that detects retriers. Once it detect an amount of retries, the load balancer times out for a period of time and then session are allowed again. Removed that configuration from the load balancer and things started to look better.