WakeUp ensures that all PCs targeted for software distribution are turned on and ready to receive it, reducing the chance that a PC will miss a vital patch. Because you can guarantee that each PC will be available when it is needed, the total power consumption of the enterprise will be reduced (as PCs can be powered off when not in use).

The software uses a combination of standard ‘Magic Packets’ and an agent service to enable Wake-On-LAN to function over networks which do not support directed subnet broadcasts.

WakeUp is used to turn PCs on and NightWatchman turns off PCs in combination these provide an effective power management and software update solution. NightWatchman can turn off PCs on demand, or according to a schedule, thereby reducing power consumption. It also saves any open documents thereby ensuring that no data is lost during the shutdown.

WakeUp and NightWatchman can be purchased together as a cost effective power management and software updating solution - the Power & Patch Management Pack.

Wake-On-LAN is a technology which allows administrators to remotely power on systems from sleep or standby modes. To use Wake-On-LAN technology on a PC, it must be supported by both the operating system and the system hardware.

Wake-On-LAN technology is a result of the Intel-IBM Advanced Manageability Alliance. A Wake-On-LAN capable network adapter is able to draw power from the power supply when the system is switched off. The network adapter continuously monitors the network watching for a specific type of network packet called a Magic Packet. When it receives that packet it alerts the system to boot into a full power state.

A Magic Packet is a specially formatted network packet which contains MAC address information. The network card listens out for a Magic Packet containing its MAC address. Once the packet has been received the network adapter will send a message to the motherboard to initiate a power on event.

Magic Packets are sent using a directed broadcast, which is a broadcast to all machines on a particular subnet. For example, a directed broadcast address could be specified as 192.168.100.255, which would go to all machines on the 192.168.10.x/24 network.

Many administrators turn off routing of subnet directed broadcasts, because they can be abused by hackers in order to generate large amounts of extra network traffic.

If you want to use WakeUp with its full functionality, providing statistical feedback on wake ups and utilizing Policy Refresh, you must install in Multi-Agent mode. This is the supported mode.

Yes, you must install WakeUp on your central site. Doing this enables you to perform right-click wake ups on collections from the SMS / ConfigMgr Administrator Console.

WakeUp has two components, the wakeup server and the agent.

The WakeUp server

The WakeUp Server integrates directly with SMS/ConfigMgr. It provides an interface that is available through the Administrator console and acts as the central controller for the wake ups. It does this by generating Magic Packets to awaken specific machines, either on user request or as a by-product of a scheduled advertisement. The WakeUp Server can also distribute the Magic Packets by communicating over IP using the WakeUp Agents.

The WakeUp Agent

The WakeUp Agent is a component of the 1E Agent.It should be installed on a remote subnet and receives instructions from a specific WakeUp Server. The Agent should be installed on all the computers in each subnet.

WakeUp integrates with Configuration Manager 2007 with or without SP1 or SMS 2003 SP2 and above.

Additionally it requires the following agents to be enabled:

• Hardware Inventory Client Agent
• Advertised Programs Client Agent

To utilize Wake-On-LAN technology you need all of the following hardware configurations:

• A network card which can support Wake-On-LAN - Your network card vendor can tell you if your network adapter supports Wake-On-LAN (most modern adapters do). If it does support Wake-On-LAN, it must be configured to enable remote wake up. Some adapter drivers are disabled by default within the operating system.
• Wake-On-LAN enabled system BIOS - Wake-On-LAN must be enabled in the system BIOS. This option can usually be found in the `Boot` menu of the BIOS configuration program
• Power management - ACPI should be enabled, otherwise the user of the machine should ensure that it is powered off by pressing the off button after shutdown.
  Read more

A quick way to tell if a system is Wake-On-LAN ready is to power down the system and then look at the network adapter display LED`s. If the lights are still on, then chances are that the system is OK. 1E also provides a diagnostic tool called Magic Test that will determine the ability for a single machine to react to a Magic Packet wake up.

WakeUp is licensed per seat with the license being applied to the WakeUp Server installation. WakeUp will manage your licenses centrally which can be confirmed by checking the log file. The first line in the log file should give the status of the license.

If WakeUp is initially installed using the 30-day evaluation license, it can be relicensed later without requiring re-installation. Once a full license has been purchased, the following command line is used:

C:>wakeupsvr.exe -relicense=CustID-xxxx-xxxx-xxxx-xxxx

Where CustID-xxxx-xxxx-xxxx-xxxx represents the license key purchased from 1E.

Note: the full license must be applied to every WakeUp Server installation.

You only need to apply the license to the WakeUp Server, though you need to purchase licenses for all seats being serviced. To apply the license via an unattended install of the WakeUp Server you add the following to the msiexec command line for the WakeUp Server installer:

C:> msiexec.exe /i WakeUpSvr.msi PIDKEY=CustID-xxxx-xxxx-xxxx-xxxx /qn

Where CustID-xxxx-xxxx-xxxx-xxxx represents the license key purchased from 1E.

To obtain a license key for WakeUp or purchase additional licenses for more seats you should contact info@ahtech.com.au

The WakeUp Server and Agent can be upgraded directly from the previous version.

WakeUp is a Windows only application. Currently there is no support for non-Windows platforms such as UNIX or Linux.

This depends on the configuration of the laptop. Laptops are usually configured to not respond to wake up packets when they are running on batteries. If the laptop is running on mains and not battery power then the wake up should work as on a standard PC.

By default WakeUp uses TCP and UDP ports 1776 to communicate with the Agent services. You will need to refer to your router documentation to see how to open this port.

Note: The Windows firewall available in Windows XP Service Pack 2 and Windows Vista restricts port access by default, so port 1776 must be re-opened prior to using the WakeUp Agent. Details on how to do this are provided in the ‘Troubleshooting’ section of The WakeUp Administrator`s Guide.

Without WakeUp, because Magic Packets themselves do not have any kind of security, if the unauthorized users are on the local network, or are able to send directed broadcasts into the network you cannot prevent them from waking up PCs by sending their own Magic Packets.

WakeUp Server and Agent communications can be encrypted by installing the services using full encryption mode. This will prevent unauthorised users from gaining information about the network when using WakeUp.

Some makes of PC can have a different boot order configured in the BIOS for when they are woken from the network as opposed to when they are physically powered up. For example some HP machines have an option called “Remote Wakeup Boot Source” and this can be set to either “Remote Server” or “Local Hard Drive”.

1E provide two simple utilities for testing the sending and receiving of Magic Packets. These tools, named RECVFROM and MAGICTST are available for download from the 1E website.

Magic Test

The 1E magictst.exe utility, as seen below, lets you send a Magic Packet to a single machine to test the functioning of Wake-On-LAN hardware.

For this test you need two PCs, a sender and a target. The sender and target PCs should both be on the same subnet. Follow the steps below to carry out the test.

1. Make sure both systems are powered on.
2. On the sender system, start the Magic Test utility – magictst.exe.
3. In the ‘Target Name’ field, fill out the name of the target system.
4. Click on the ‘Resolve Name’ button. This will automatically complete the ‘IP Address’ and ‘Subnet Mask’ fields. If you know the IP information already you can fill in the fields manually.
5. Once the IP Address information is complete – click on the ‘Ping for MAC Address’ button. This will complete the MAC Address field.
6. If all of the above fields have been completed, you now have enough information to perform the test.
7. Shutdown the target system.
8. On the sender system, click on the ‘Send Magic Packet’ button. This should now send a magic packet to the target system, causing it to boot.

The magic test utility

MAC address resolution

The MAC Address can be resolved providing your router is currently aware of it. The resolution uses the DOS utility "ARP", which can only resolve the MAC address if the MAC info is currently in the router ARP cache. This means that for the resolution to work the target machine would need to have been rebooted recently as the router ARP cache is normally cleared out frequently.

For testing purposes the MAC address can be entered manually. The resolution issue with Magic Test will not affect 1E WakeUp as MAC address information is retrieved directly from SMS / ConfigMgr.

Receive from test

This test uses the Magic Test and the recvfrom.exe tool. The recvfrom.exe tool is used to listen out for Magic Packets. It can be executed on the target machine on the remote subnet and will log all Magic Packets that are received at the subnet.

Follow the steps below to carry out the test.

1. Make sure both systems are powered on.
2. On the target machine run the recvfrom.exe tool.
3. On the sender system, start the Magic Test utility – magictst.exe.
4. In the Target Name field, fill out the name of the target system.
5. Click on the Resolve Name button. This will automatically complete the IP Address and Subnet Mask fields. If you know the IP information already you can fill in the fields manually.
6. Once the IP Address information is complete – click on the Ping for MAC Address button. This will complete the MAC Address field.
7. If all of the above fields have been completed, you now have enough information to perform the test.
8. On the sender system, click on the `Send Magic Packet` button. This should now send a magic packet to the target system.
9. You should now see the magic packets arriving at the target machine, as shown in `The output from recvfrom.exe` figure below.

The output from recvfrom.exe

WakeUp draws client information directly from the SMS / ConfigMgr database. The client registers its IP and Subnet information as part of the SMS / ConfigMgr discovery process. VLSM therefore will not affect WakeUp.

See here for more information about VLSM.