cancel
Showing results for 
Search instead for 
Did you mean: 

COMPUTER LAB IDLE TIMEOUT

craig_knights_7
New Contributor II
We installed a lab of 24 iMacs (El Capitan) at the beginning of the year, and hoped to do the network logins by wireless on a pair of R600's with their own localised SSIDs.

Problem is that our vSZ kicks unused machines off the wireless for being idle.  This stops them logging on with a network account.  A reboot often brings the "Other..."  logon option up.  But not always.

We've resorted to using local accounts and making one for each student.  But this is not good.

I've set the timeout to the maximum of 1000 seconds, but that doesn't seem to help.  I can see in the logs clients getting kicked after 1 minute due to inactivity.  We get this on staff MacBooks too.

We're on vSZ version 3.1.1.0.450  is an update a good idea?   Does the timeout change? I still have some 7323's in low client density areas, and replacing those for v3.3 will be a hard sell to the finance people..  I have seen posts about ER-1553, where the timeout was accidentally decreased.  But I'm having trouble finding the details of the next version of vSZ that would fix this..  I'm not sure how the version number correspond between ZD and vSZ.  This version was installed about a year ago.

Apart from the idle thing, the lab works great, students seem to be getting good connections for cloud based software.

Any clever ideas?

Many thanks,
Craig
3 REPLIES 3