I was curious if there was any setting for this when not dealing with the Web Client. I am wanting to implement this in a full client environment.
Yes, there is! In the Laserfiche Administration Console (either desktop or web), go to Repository Options. In the Sessions section, select "Session will disconnect after being left inactive" and set the number of minutes you want to pass before the idle logout occurs. The setting is repository-wide and will affect everyone, including those logging in on full Clients.
After seeing this post, I remembered that I have a question about this topic....
I have always had our inactivity threshold at 15 minutes and for the most part, it works great!....but I've also found that some users are logged in to LF but they've been inactive for way past 15 minutes....
I'm looking at one right now that has been idle for 3 h 43 m ..... earlier, one user was idle for 18 h 37 m. This happens with the client active but on occasion, LFScan.exe is also active for the same user.
Our license model is United and we are using LF Content repository Server 9.0.2 build 671.
Is this a known issue?.....What causes this behavior? Is there something that I can tweak that will force these inactive users to be logged off?
Thanks in advance for your help.
This is actually intended behavior. We want to ensure that the timeout doesn't cause operations to get stopped in the middle - for example, if a briefcase or OCR operation is occurring, the Client process that monitors timeout might not know whether it's waiting for the Server to process items or if it's actually inactive, so it errs on the side of ensuring data isn't lost by logging out in the middle of operations. As far as scanning is concerned, it can't tell at all - so if scanning is open, it will not logout.
This is to address these types of issues that could occur in prior versions: https://support.laserfiche.com/KB/1011903 (obviously that's not current, but that's the type of scenario that was being addressed).
Our office is having a similar issue. Disconnect is set at 180 minutes (3 hours) but we have users idle for 8+ hours - not scanning, OCRing, etc. Server was upgraded to 9, as were a few test clients. Most clients are still running 8.3.
Has this issue been resolved?
Is there a change to a file or a registry key that can be done to force users that have been idle for lets say in 180 minutes, other then the Idle Disconnect setting in the Admin console?
Still have this problem. Is there a prompt for users stating they have been idle for too long? We are now on 9.2 and planning on migrating to 10 around Jan 1.
One of our clients are also having this issue. They are concurrent licensing so it takes up a license and IT has to manually disconnect it. The idle disconnect is set for 15 minutes and it goes up to 8 hours. Is there a file that I can tweak to make sure that at 15 minutes it will disconnect?
After 10 years, it seems there is still no solution to force to log out user if the operation taking too long.
We are using Weblink 11, some users take too long to download multiple documents/ folders and their sessions are holding over 4 hours. This is no good for the server.
LaserFiche should do some fixes or new auto features to terminate the download time. I checked disable KeepAliveTimer is not available in LF 11.