Often, organizations choose to keep their computers turned on all night for a variety of reasons including:
- the need to push updates/patches
- run critical maintenace tasks – scans/backups
- to make the system available to employees as soon as they walk in
In the process, large amount of energy is wasted.
Wake-on-LAN integration in Enpower allows organizations to wake systems in their network in a flexible manner; thus avoiding the need to keep systems on all the time – cutting down operating costs without affecting system availability.
Using the integrated Wake-on-LAN feature in Enpower, you can:
- Wake systems instantly at the click of a button
- Provide a schedule for each day of the week to wake systems up
- Allow select employees to be able to wake their systems from anywhere in the world
Wake-on-LAN needs to be supported by your system’s hardware as well as needs to be enabled in the BIOS and through Windows. All wake ready systems are listed in Enpower’s central console for easy management. The console shows you the current state of your network – so you know – at any moment, how many machines are turned on in your network.
From wikipedia:
The computer to be woken is first shut down (sleeping, hibernating, or soft off; i.e., ACPI state G1 or G2), with power reserved for the network card, but not disconnected from its power source. The network card listens for a specific packet containing its MAC address, called the magic packet, broadcast on the broadcast address for that particular subnet (or an entire LAN, though this requires special hardware or configuration).
The issue that system admins often face is that most routers are configured by default to block all broadcast packets originating from outside its subnet. This means a system sending magic packets trying to wake other systems up – can only do so for systems within its subnet.
Enpower works around this intelligently by selecting one “wake proxy” per subnet – which is simply a turned on computer – which has been delegated the responsibility of waking machines in its subnet, for as long as it remains on. As soon as this wake proxy goes off, the central server automatically chooses another available system in the subnet to perform this job. While this could mean that you need to have one system on per subnet to guarantee wake across your network, optionally – if you can configure your network to allow broadcast of magic packets across subnets, you can select – one “master” wake proxy – which would most often be your Enpower’s central server.
Wake-on-LAN , as on date is fully integrated into Enpower, though in the future, we do plan to release it as a stand-alone installable which can be integrated into other enterprise network management products.