Treat the public session as a complete workflow
A patron needs to begin a session, use the permitted applications and finish or save work through the library's supported process. Printing may introduce another account, queue or release step. A working desktop is only one part of that path.
The acceptance test should follow representative public use through the approved session process. The library should identify which accessibility features, applications and output methods need to remain available. Those requirements should influence the replacement configuration before equipment is deployed widely.
The end of the session is as important as its beginning. The library needs to know what is removed, what is retained elsewhere and how the patron is informed about saving work before the session ends.
Shared-device settings need precise interpretation
Microsoft's Shared PC documentation distinguishes managed account deletion policies from Guest and Kiosk accounts created through the sign-in options. Those Guest and Kiosk accounts are deleted at sign-out, while pre-existing or manually created local accounts are not automatically removed simply because Shared PC mode is enabled.
That distinction matters when a library reuses an existing Windows image. Enabling a shared-device feature does not establish that every account on the machine receives the intended cleanup behavior. The actual session identity and configured deletion policy need to be checked.
The test should confirm what remains after a representative session ends and the next one begins. It should use approved test content, not a patron's personal information. The objective is to validate the library's intended configuration rather than infer it from a feature name.
Session cleanup does not describe every connected service
Deleting a local profile does not independently determine the retention behavior of a print server, reservation platform or another external service. The library should understand those separate boundaries when assessing the complete public-access workflow.
ALA's public-access computer guidance addresses data management across computers and networks, and its companion checklist calls for clearing individual-session data. The useful operating question is where each relevant category of information can remain and which supported control manages it.
This should produce a clear configuration and ownership decision, not indiscriminate deletion during an active patron session. The library's responsible staff should define the service behavior and the communication patrons receive about it.
Staff services need their own change window and tests
Public-area work can affect shared switching, printing or connectivity used by staff. The project should identify that impact before scheduling around public opening hours alone. Staff may need systems before opening and after public sessions have ended.
Acceptance should include the affected staff workflows under the appropriate identity. A test from a public computer cannot establish that a circulation or administrative application works from the staff environment. The support route and access permissions may also differ.
Where work is phased, each released area should have a coherent operating state. The library should know which public services remain available and how staff should direct patrons while the next area is being changed.
Handover should preserve the intended service behavior
The receiving team needs the device configuration, session policy, relevant service relationships and unresolved exceptions. A later repair should not accidentally replace the tested public-session behavior with an ordinary office-computer setup.
Library IT installation succeeds when public access and staff operations both work through their intended paths. Validating session cleanup alongside access, applications and printing makes the result more useful to the library and more dependable for the next person who uses a shared computer.