Skyrsoft Autologon Manager can restrict auto-logon to hours you choose, so a kiosk is only signed in when it is meant to be. A schedule lives on a group and applies to every member, or on an individual agent as an override, and it works in two shapes: a recurring or one-off window during which the machine should be signed in, and standalone events that fire a single action at a set time.
How it works
The schedule engine is one evaluator shared by the server, for previewing what a schedule will do, and the agent, for actually running it — so what an admin sees in the console editor is exactly what the machine does. Windows and events both ride the same declarative configuration channel as every other policy: a change bumps the affected agents’ configuration version, and each one picks it up on its next poll rather than being pushed to immediately.
Open-hours windows
A window is a weekly recurrence (pick the days and a start and end time) or a one-shot date range, and it names what happens outside it — log off or lock. A window that ends before it starts wraps past midnight, so an overnight shift is one entry, not two. Outside every window, the closed action applies and auto-logon is suppressed: the credential provider offers no logon tile at all, so the machine simply sits at the ordinary Windows logon screen until the next window opens.
Discrete events
Alongside windows, standalone events fire a single Logon, Logoff or Lock action at a specific time, either once or on a weekly recurrence — useful for a single scheduled maintenance lock that does not fit an open-hours shape.
Limits
Every schedule time is the agent’s own local wall-clock time, not the server’s. A window of 08:00 to 18:00 means 8am to 6pm wherever that particular machine physically sits, not wherever the server is hosted — a fleet spanning time zones needs that kept in mind when a window is set on a shared group.
A closed machine still shows a logon screen, not a blank one. Suppressing auto-logon outside a window means the credential provider declines to offer its tile; it does not lock out or power down the machine, so anyone with the real Windows account and password can still sign in by hand.
A group-level schedule bulk-applies to every member the moment it is saved, the same as any other group policy change — there is no staged or gradual rollout for a scheduling edit across a group’s machines.