I lost quite a bit of sleep over the last few nights, burning the midnight oil trying to get my Dell PowerEdge 840 (server repurposed as a workstation) to work with various Dell management utilities and enable Wake On LAN (WoL) functionality.

It seems that the various OpenManage tools were no help – indeed many of the information sources I found for configuring the Baseboard Management Controller and kicking SOLProxy and IMPI into life seemed to be out of date, or just not applicable on Windows 7 (although ipmish.exe might be a useful tool if I get it working in future and it can be used to send WoL packets). I did find that, annoyingly, WinRM 2.0 needs an HTTPS connection and that a self-signed certificate will not be acceptable (according to Microsoft knowledge base article 2019527).  If I ever return to the topic of WinRM and IPMI, there’s a useful MSDN article on installation and configuration for Windows Remote Management.

In the end, even though my system is running Windows 7, the answer was contained in a blog post about a PowerEdge 1750, WoL and Debian

“Pressing ‘CTRL-S’ brings us to a configuration panel which allows for enabling the Wake-On-LAN (WOL) mode of the card.”

I’d been ignoring this because it the Ctrl-S boot option advertises itself as the “Broadcom NetXtreme Ethernet Boot Agent” (and I didn’t want to set the machine up to PXE boot) but, sure enough, after changing the Pre-boot Wake On LAN setting to Enable, my PowerEdge 840 started responding to magic packets.

On my WoL adventure, I’d picked up a few more hints/tips too, so I thought it’s worth blogging them for anyone else looking to follow a similar path…

• According to a white paper describing WoL support on Dell servers:

“Windows 2000 and Windows 2003 do not require that WOL be turned on in the NIC’s or LOM’s firmware, therefore the steps using DOS outlined in the Out?of?Box and Windows NT 4.0 procedures are not necessary and should be skipped.  Enabling WOL with IBAUTIL.EXE, UXDIAG.EXE or B57UDIAG.EXE may be detrimental to WOL under Windows 2000 and Windows 2003.”

• Presumably this advice also applies to Windows XP, Vista, Server 2008, 7 and Server 2008 R2 as they are also based on the NT kernel, so there is no need to mess around with DOS images and floppy drives to try and configure the NIC…
• I downloaded Broadcom’s own version (15.0.0.21 19/10/2011) of the Windows drivers for my NIC (even though Windows said that the Microsoft-supplied drivers were current) and I’m pretty sure (although I can’t be certain) that the Broadcom driver exposed advanced NIC properties that were not previously visible to control Wake Up Capabilities and WoL Speed. (Incidentally, I left all three power management checkboxes selected, including “Only allow a magic packet to wake the computer”). There’s more information on these options in the Broadcom Ethernet NIC FAQs.
• There is a useful-sounding CLI utility called the Broadcom Advanced Control Suite that I didn’t need to download; however its existence might be useful to others.
• Depicus (Brian Slack) has some fantastic free utilities (and a host of information about WoL) including:
• Wake on LAN tools for Windows 3.1, modern versions of Windows (GUI and CLI), Mac (GUI and CLI), iPhone and Android (with Windows Phone version in development)  – although I only used the Windows CLI version.
• A Wake on LAN .net web service to deploy on your own web server (there’s an ASP version too and a COM object).
• A WoL over the Internet service (which worked for me, once I configured my router to forward UDP port 7 requests to the IP address that I reserved for the PC I want to boot – there’s a static ARP solution too, but I didn’t use that). There’s even a Facebook WakeOnLAN app!
• Some other interesting tools including an ARP Viewer and a WoL Monitor/Sniffer.
• Other WoL tools (although I think Depicus has the landscape pretty much covered) include:
• Matcode Wake-on-LAN (mc-wol.exe), which seems to work well, although the Depicus monitor doesn’t see the packet.
• ReadPixel WakeOnLan for OS X.
• Nirsoft WakeMeOnLAN, although this scans the network to look for devices – it doesn’t seem to allow entry of target device details.
• AMD Magic Packet Wakup Application (MPWake), an elderly application written for MS-DOS that needs to be compiled before it’s run (I didn’t bother!).
• Sourceforge Wake On LAN project (I haven’t tried this).
• There’s also some more information about WoL on Lifehacker.