Kentucky schools have embarked on an energy management program. This was required by law and every district is participating at some level. This energy saving initiative deals with all aspects of the school, from lighting to HVAC, food service, transportation, etc.Technology can and should be involved at some level. As a successful CIO, it's always good to demonstrate leadership by participating and cooperating with high-level district initiatives such as these. Along those lines, I thought I'd take a moment to mention the capability of remotely shutting down and starting computers. This may seem minor but, to a lab manager that touches 30 machines in a lab to power off or power on a lab, this will save time and buy you some goodwill. These remote capabilities also could open the door to scheduled shutdowns and power-ons, which definitely falls in line with the energy management initiatives.
Shutting down computers is easy enough and can be done via command line. As most of you well know, if it can be done via command line, then it can be done via script or GUI-based tool. There are countless tools that allow for remote shutdown and I won't bother to feature one here. The point is simply that it can be done and, if you're not doing it now, you should consider implementing this and doing so as part of an energy-saving initiative.
Most are also aware that computers can be powered on remotely as well. The technology involved concerns Wake-on-LAN and the use of a "magic packet". Wake-on-LAN is available on every machine that's even relatively current. To enable this capability, a BIOS setting may need to be changed.
In addition to getting the machine ready, your switches would need to support the use of the "magic packet". As an aside, the magic packet is a special broadcast that is sent to the LAN or specific machines via the network. You'll want to test this to ensure that your switches and your particular network configuration supports proper transfer of this packet, but that packet is what triggers the machine to power on (and, not coincidentally, this is one reason that a slight amount of power still passes through a networked computer that is powered off).
Assuming your switches and computers are capable of supporting Wake-on-LAN and magic packet transfer, you should be ready to implement remote power-on. As with remote shutdown, there are many tools available to send those packets and automate the process. This post wasn't meant to highlight those tools and a few simple searches will lead you to multiple options. However, I thought it was worth a few minutes to highlight the concept of remote power-on and shutdown and ask you to consider implementing it as part of an overall energy management solution for your district.
1 comment:
We have been doing this for a while now. It is even better if you use something like fog since it can wake the machines up to image them and stuff.
We have fog turn the machines off, I have a script that shuts them down and I have also used the EZGPO power tools from the Energy Star site to save power as well. We have been doing that for about 3 years.
Post a Comment