Yeah, I'm thinking you'd need something in the task scheduler to run a log off script after a certain number of minutes of idle activity. I asked ChatGPT about it, and here's what I came up with, which is pretty close to what I would have said anyways.

---

This is a common issue in shared-use environments, and you're on the right track thinking about idle-time detection followed by forced sign-out. Since you're using Windows 11 Home, you don't have access to Group Policy or domain tools like you'd get with Pro or Enterprise, but we can still work with PowerShell and the Task Scheduler.

Here's a reliable and lightweight solution that doesn't require third-party software:

---

Option: Use Task Scheduler + PowerShell script to sign out users after X minutes of inactivity

Step 1: Create a PowerShell script to log out the user

Create a file called `ForceLogoff.ps1` with this content:

Code

shutdown.exe /l
Copy

That's it. `/l` is the switch for logoff.

---

Step 2: Create an idle-triggered scheduled task

Since Windows doesn't have built-in "idle timeout" for sign-out in Home edition, we'll use Task Scheduler's "On idle" trigger.

1. Open Task Scheduler
2. Create a new Basic Task
3. Give it a name like AutoLogoutIdle
4. Choose When a specific event is logged (skip this, we'll edit it later)
5. Finish the wizard, then right-click the task and go to Properties
6. Under Triggers, delete the default one and click New\...

   * Begin the task: On idle
7. Under Actions, set it to Start a program

   * Program/script: `powershell.exe`
   * Add arguments: `-ExecutionPolicy Bypass -File "C:\Path\To\ForceLogoff.ps1"`
8. Under Conditions, make sure:

   * Start the task only if the computer is idle for: X minutes
   * Adjust wait time as needed
9. Under Settings, check:

   * Stop the task if it runs longer than: 1 hour
   * If the task is already running, then the following rule applies: Stop the existing instance

---

Note: You'll need to set ExecutionPolicy to `Bypass` or sign the script if running with restricted settings.

---

Alternate: Use a custom PowerShell script to track idle time

If you want more control, you can use a PowerShell script that runs in the background and checks for idle time, like this:

Code

Add-Type @"
using System;
using System.Runtime.InteropServices;
public class IdleTime {
    [DllImport("user32.dll")]
    public static extern bool GetLastInputInfo(ref LASTINPUTINFO plii);
    [StructLayout(LayoutKind.Sequential)]
    public struct LASTINPUTINFO {
        public uint cbSize;
        public uint dwTime;
    }
    public static uint GetIdleTime() {
        LASTINPUTINFO lii = new LASTINPUTINFO();
        lii.cbSize = (uint)Marshal.SizeOf(typeof(LASTINPUTINFO));
        GetLastInputInfo(ref lii);
        return ((uint)Environment.TickCount - lii.dwTime);
    }
}
"@

$MaxIdleMinutes = 15
while ($true) {
    $idleTime = [IdleTime]::GetIdleTime() / 1000 / 60
    if ($idleTime -ge $MaxIdleMinutes) {
        shutdown.exe /l
    }
    Start-Sleep -Seconds 60
}
Copy

This runs in a loop, checks for idle time, and logs out after 15 minutes of inactivity. You can run this at startup via Task Scheduler or a shortcut in the user's Startup folder.

---

Final tips:

* This works best if users don't have unsaved work, or you want to force the habit of saving and signing out.
* If you want a friendlier experience, instead of logging out, you could lock the screen or display a warning first.

I'll put it to the test when I'm there tomorrow.

Will be 1 more thing ticked off my list of requests there since I just spent 2-days rewiring cat-6 because the genius electrician decided to run 12/2 wiring through the same conduit/holes the cat-6 was running through... 500-meg fiber internet was reaching a max 2.5 megs because the electric lines were putting "noise" across the low-voltage lines

As always, thanks for the shared wisdom!

Don

Haha yeah. Doing it with Access is easy. :)

Yeah, unfortunately on that station, there are currently no databases. It's a basic system for the folks the know everything (except how to logout, use the printer, type... lol)

I started many years ago building a database to replace the financial/bookkeeping/payroll system because it is no longer supported - the developer retired about 10 or so years ago. I think the last formal update he did was around 2000... It's a 16-bit RBase for DOS application with very little win32 compatibility let alone 64-bit. Has to have a printer connected to a parallel port print checks or reports, those kinds of issues. Every time a Windows update comes through (just about) I have to go in and reset some windows settings to keep it running.

I had started developing an app BEFORE I found Richard's lessons on YouTube (and eventually this site) and had some stuff working but that was before I learned any VBA so everything was coded with macros that I figured out by winging it. Needless to say poor code and even worse editing, lol.

When I get that app done, it will connect to the other stations as well, but until then...

Well, there was room in there for the 12/2...  :)