Client checklist
- Confirm each client PC can reliably reach the server over the local network.
- Test lock screen behavior before and after a timed session.
- Review application restrictions, drive access, browser access, and restart behavior.
- Check whether the client starts correctly after Windows login or reboot.
Client security screen
In archived CyberCafePro installations, client security settings are configured from the server, not from the workstation itself. The client settings screen groups six tabs covering machine-level security, system behavior, browser restrictions, advanced session rules, customer-facing help text, and promotional marquees. A default access password, sometimes called the master password, is used when a client cannot reach the server, so an unset password is treated as a security gap that should be closed before opening the location.
Security tab options
The security tab controls which system functions are exposed to customers on each client. Common restrictions include:
- Disabling hotkeys that would otherwise open system menus or switch programs.
- Blocking access to the Windows control panel.
- Disabling CD or removable drive auto-run and, separately, disabling access to those drives entirely.
- Disabling the print spooler until a staff member or a paid session enables it.
- Restricting access on a per-drive basis so customers cannot browse drives that hold configuration or business data.
- Blocking specific window titles, which can catch unwanted programs or websites by matching text in the window caption rather than filtering content directly.
System settings tab
The system settings tab controls session-level behavior rather than machine lockdown. Operators typically review:
- Whether system sounds and speaker warnings are enabled during a session.
- Whether registry startup items and the Windows startup folder are allowed to run, since unmanaged startup programs are a common way for customers to bypass session billing.
- Whether the client reboots or locks automatically at the end of a session, which is useful for locations running disk-protection software or that want customers to return to the counter between sessions.
- Whether customers can adjust volume, start a chat with staff, or order point-of-sale items directly from the client screen.
- Which account types, such as timecodes or user accounts, are allowed to log in on that client.
- Where banner images and start or end-of-session programs are read from, noting that paths on a network share can add noticeable delay compared with a local path.
Browser and advanced restrictions
A dedicated browser tab restricts common escape routes inside Internet Explorer or a similar browser, including local file access, file open and save dialogs, the browser options menu, favorites, downloads, toolbar editing, and browsing history retention between sessions. An advanced tab adds lower-level controls: which processes are allowed to keep running after a session ends, which processes are terminated by name or by window title, whether the interface reappears automatically once no program is detected running, and the process priority assigned to the client software itself. These settings are aimed at operators troubleshooting a specific recurring issue rather than a typical first-time setup.
Help text, marquees, and manual timers
Two lighter-weight tools round out client configuration. A help tab lets staff publish plain-text or HTML instructions that a customer can open from the client screen, which is useful for locations without a staffed front counter at all times. A marquee tab scrolls promotional text across the login screen and can be targeted to specific clients rather than the whole location. Separately, archived CyberCafePro installations support manual timers for equipment that cannot run client software directly, such as a console attached to a television. A manual timer can be linked to point-of-sale items so that time and product sales appear on the same running tab for that station.
Busy-hour concerns
- A single misconfigured image can create repeated support issues across many PCs.
- Session start and stop events should be tested on several workstations, not only one.
- Staff need a documented recovery path for frozen screens and disconnected clients.
Modernization triggers
- Unsupported operating systems, unreliable client locks, and weak recovery workflows are signs that migration planning should begin.