Logon problems with public machines

From Stacey and Brown

The bottom line on this (below) is that if the computer won't connect, we should move patrons to another machine and reboot. Only report to ERIT if rebooting doesn't work.

Here is the explanation of what is happening and why:

(Brown) Occasionally, if a machine is unable to connect, and waiting/restarting it doesn't fix the problem, then it is likely in "remediation". This is a situation where the computer in question has not met a required baseline of Windows updates or Virus Definitions. The systems group moves the machine to a separate network and runs its updates, then moves it back.

In our case, since we run software that prevents changes from occurring to the hard drive, our machines will slip out of the requisite update schedule. We're currently working on how best to mitigate this situation by shutting down the SmartShield software and running updates on the weekends only (when the library is closed). As far as our patrons are concerned, it would be best for them to attempt to logon to another available machine.