jc296
Enthusiast
Enthusiast

Horizon Client and timers - new user can't log in after user disconnects

Guys, strange use case but I need help to understand why a new user can't log into a VM desktop when an existing user has disconnected from his client session. So heres the scenario: user 1 logs into the Pool and is connected to his Wins desktop, he doesn't log at the Windows Log in page but decidesto close the horizon client session; in Horizon admin, the VM in the pool shows "Available" throughout, which is expected i guess as he didn't log in so wouldn't show connected. However, when the 1st user disconnects ie closes the horizon client, anyone else who has an entitlement to that desktop pool can't log in for approx 15-20mins. Is there a timer that I can adjust to bring that time down to say 30secs?? 

Horizon 8.7

View Agent 8.2

Horizon Client 8.7

Wins10 Test VM 

Reply
0 Kudos
Jubish-Jose
Hot Shot
Hot Shot

Use the setting 'Logoff After Disconnect' under Desktop Pool Settings. You can choose to logoff Immediately or set a time period. 


-- If you find this reply helpful, please consider accepting it as a solution.
jc296
Enthusiast
Enthusiast

It is set to log off immediately.  Our users have a habit of connecting to their desktop using Horizon Client (being presented with the Wins Login page), don't login then just disconnect so in theory they don't even log in.  I would expect the Desktop to be available for the next entitled user.

Some of our VMs are not domain joined and we have alimited use case where we share a desktop from several clients (and session stealing has been enabled).

Reply
0 Kudos
jc296
Enthusiast
Enthusiast

JJ, thanks. I've set it to log off immediately but unfortunately this doesn't help because the Users often don't log in - the Wins Login page will sit there so even when you disconnect the Horizon Client session the VM becomes unusable by any other user for 900secs.

I have found that when you add a WIns registry string VdmConnectionTicketTimeout on the VM (not domain joined btw) and add string 60secs the desktop becomes usable again after thsi time give or take 1-2 mins. Problem solved.

Reply
0 Kudos