SetPower - configuring and using Remote Wake

SetPower allows you to wake machines on your network whether they are sleeping, hibernating or are turned off. This can be useful in a variety of situations including cases where an Administrator wants to wake a sleeping machine, or when end-users want to gain remote access to their machines withouth having to leave them running continuously.

In order to use SetPower WakeUp workstations must be configured to respond to Wake-On-LAN requests. Wake-On-LAN is a technology that allows machines to be woken when they recieve a special message on the network (usually referred to as the magic packet). In order for Wake-On-LAN to function it must be enabled in the BIOS of the PC as well as in Windows.

Enabling Bios

More often than not newer machines have Wake-on-LAN enabled by default in the BIOS.

Enabling Windows Support

Locate the Network Adapter that should be used for Wake-On-LAN and hit properties.

XP - Control Panel -> Network Connections
Vista/7 - Control Panel -> Network and Sharing Center -> Change Adapter Settings

In the resulting properties dialog press configure and visit the Power Managment tab. Ensure that Allow this device to wake the computer is checked.

Waking via SetPower via Enterprise Manager

In the SetPower Enterprise Manager choose View Clients to display a list of SetPower clients. Select the client (or clients) that you wish to wake and press the Wake button.

Waking via the SetPower Wake Page

Normally this page is used when end-users wish to access their sleeping machine remotely.

Connect to the network via a VPN connection
Visit the following Url in a web browser: http://setpower/ where setpower is the name of the server in which you have installed the SetPower Service.
Enter their windows username (without the domain prefix) and password. A list of computers they have logged into will be presented. Click on the computer they wish to wake.
Connect via their preferred remote access software (Windows Remote Desktop Connection, VNC)

Routing Issues

Some networking gear (routers or layer 3 switches) may not pass WOL Magic Packets off the local subnet . Since WOL packets are directed at the physical layer via subnet broadcast it may be necessary to allow Directed Broadcasts. This link describes the process for Cisco equipment.