Hey fellow system admins! I'm facing a frustrating challenge with managing user inactivity logouts in our large retail chain. We have shared workstation accounts where multiple users log in throughout the day. The issue arises when one user opens Chrome and then another user sits down without realizing the first user is still logged in, which can lead to mistakes and data mishaps. I'm looking for a solution that can log users off automatically after about 10-15 minutes of inactivity. I've tried a few things:
- A PowerShell script to edit the registry for inactivity timeouts didn't work.
- I set up a Scheduled Task to check for inactivity every minute and logout using certain commands, but that didn't go through either.
- Also tried configuring an Intune device policy, but it conflicted with existing settings, perhaps from my O365 Baseline policy.
- We're fully on Azure AD, so I can't use GPOs.
While I managed to configure some local policies that work, they only lock the computer instead of logging users out completely. I'm 20 hours deep into this and really need some fresh ideas!
5 Answers
Using screensavers with lock timers is a classic solution. Just set a black screen saver to kick in after 10 minutes. It locks the workstation, which might help until you find a better logout script.
What about implementing ID badge logins? Users could log in by swiping their cards, and once they step away and remove their badge, it locks or logs them out automatically. It's user-friendly and requires minimal effort.
Have you tried an old tool I created called SystemIdleCheck? It’s specifically designed for this kind of issue. It helps manage users on shared machines by logging them out after they leave the workstation unattended for a while.
I love that utility! We use it in our office to remind users to save their work before logging them out. Really helps to avoid data loss!
That could work for me! Can it also send notifications before logging users off?
Are you sure each user is using their individual accounts? I mean, if they are sharing login info, that’s part of the problem. Each session should be isolated, which could help with managing the workload better.
Exactly! If they aren’t signing out properly, it defeats the purpose of separate accounts. We really need to emphasize following protocols.
Check out this link to a GitHub tool called Idle Logoff. It’s been fantastic for us! You can configure it with Group Policy, and it has completely solved our issues with idle users. Definitely worth a try!
Yeah, this tool is the go-to for many folks! It’s highly configurable and takes care of the problem easily.
I second this! It's better than anything Microsoft has produced. I've used it in the past, and it worked like a charm!
That’s a decent short-term fix, but remember, locking doesn't log users out as OP mentioned!