Does anyone know what would cause the SAME user to login into multiples sessions even though we don't allow multiple logins in our View environment?
We saw this a lot with View 4.6.1, and occasionally with View 5.1.1.
I believe the issue is because the desktop VM that is selected for the user by the Broker is busy doing something (CPU 100%) and the View Agent in the VM cannot process the request from the broker in a timely manner. I believe the Broker gives up after a few seconds of no response from the agent and then chooses another available desktop.
So if the user disconnected from their desktop and then return later, but their desktop has a process stuck in a loop and using 100% CPU, the agent has a hard time getting back to the Broker so the broker gives up and chooses another desktop.
The desktops we are using are WinXP SP3 with 1 vCPU and 2GB ram.
Is it just the one user or does it happen to multiple users?
Is it a fairly consistent problem or just seems to happen from time to time?
When you say "is not allowed" I assume this to mean in the pool settings you have set the 'Allow multiple sessions per user' setting to 'No' as well? Correct?
It happens randomly. Not everyone is affected.
When you say "is not allowed" I assume this to mean in the pool settings you have set the 'Allow multiple sessions per user' setting to 'No' as well? Correct? Correct.
We saw this a lot with View 4.6.1, and occasionally with View 5.1.1.
I believe the issue is because the desktop VM that is selected for the user by the Broker is busy doing something (CPU 100%) and the View Agent in the VM cannot process the request from the broker in a timely manner. I believe the Broker gives up after a few seconds of no response from the agent and then chooses another available desktop.
So if the user disconnected from their desktop and then return later, but their desktop has a process stuck in a loop and using 100% CPU, the agent has a hard time getting back to the Broker so the broker gives up and chooses another desktop.
The desktops we are using are WinXP SP3 with 1 vCPU and 2GB ram.
Hi!
I am also experiencing the same on my end.
Were you able to fix this issue? If yes, how did you fix it?
Thanks.