<div dir="ltr"><div>Chad beat me to the punch, but to the best of my knowledge, you have two options: WOL and what Chad mentioned in the firmware config. Many computers have a scheduled wake from sleep option. The downside to that second method, however, is that it's configured on each individual computer, while WoL is a Magic Packet sent from a central location (from which you can configure any number of computers to wake up on whatever schedule and change the time/day(s) quickly and centrally.</div><div><br></div><div>I use WoL at many of my libraries to wake the patron computers at appropriate times/days. It works pretty well most of the time with the caveat that on occasion a random computer may not wake correctly and may require a finger-poke. To work correctly (on a Windows computer, at least), you need to ensure that 1) the firmware is configured correctly to enable WoL, 2) the NIC driver in Windows is configured to leave the NIC in the correct state at shutdown, and 3) that the Magic Packet is being sent from a computer on the same subnet as the computer(s) you're trying to wake. (There are other, routable options for waking computers too, so I think that's where some of your variations come in.)</div><div><br></div>On a rare occasion, an improper shutdown may cause 2) to not happen correctly and can cause a computer to not wake correctly. That's where the finger-poke comes in. But the staff usually seem to be able to handle it and it self-resolves at the next use and correctly shutdown.<div><br></div><div>The WoL usually gets paired with auto-shutdown in the evenings using an unrelated method. Generally, the problems come in the form of complacency when the staff get used to ignoring the patron computers and something doesn't happen correctly (most often around a DST/ST time change.)</div><div><br></div><div>It's not hard to implement WoL. Give it a shot!</div><div>2 cents, good luck!</div><div><br clear="all"><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>______________________________<br><b>Chad Neeper</b><br><font size="1">Senior Systems Engineer</font><br><br><b>Level 9 Networks</b><br><font size="1">740-548-8070 (voice)<br>866-214-6607 (fax)</font><br><br><font size="1"><i>Full IT/Computer consulting services -- Specialized in public libraries</i></font><br></div></div></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Aug 1, 2022 at 2:20 PM Nathan Eady via OPLINTECH <<a href="mailto:oplintech@lists.oplin.org">oplintech@lists.oplin.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
Hi,<br>
<br>
I've had a request, that I set up the computers here to turn themselves<br>
on in the morning shortly before people start to arrive. My first<br>
coherent thought on the matter (after the initial "say WHAT?") was that<br>
maybe I could possibly make it happen with Wake On LAN somehow, but I'm<br>
discovering that despite how old WOL is, there's a disturbing amount of<br>
variety, from one computer to another, in terms of whether and to what<br>
extent the firmware implements WOL. (Most of our computers use onboard<br>
LAN, as opposed to expansion-slot NICs.)<br>
<br>
So now I'm wondering if there's some more reliable mechanism, that I'm<br>
not aware of, to automatically power-on computers that have been shut<br>
down for the night.<br>
<br>
-- <br>
Nathan Eady<br>
Galion Public Library<br>
_______________________________________________<br>
OPLINTECH mailing list<br>
<a href="mailto:OPLINTECH@lists.oplin.org" target="_blank">OPLINTECH@lists.oplin.org</a><br>
<a href="http://lists.oplin.org/mailman/listinfo/oplintech" rel="noreferrer" target="_blank">http://lists.oplin.org/mailman/listinfo/oplintech</a><br>
<br>
****** ****** ****** Send SMS notification messages directly to patrons at no charge: <a href="https://www.oplin.ohio.gov/sms" rel="noreferrer" target="_blank">https://www.oplin.ohio.gov/sms</a> ****** ****** ******<br>
</blockquote></div>