Wake On Lan Settings

I am wanting to send a WoL packet to my desktops before I start a patch job to ensure they all get patched. I have enabled this in the bios but on any of my machines with an Intel NIC there is a setting called "Wake on Link" and unless it is set to "Forced" the computer will not power on. By default this setting is set to "Disabled" does anyone know how I can change it either with a script of some kind or a registry entry?

0 Comments   [ + ] Show comments

Answers (6)

Posted by: costanza 13 years ago
Yellow Belt
Any luck with this??? THis would be handy to know how to do it here as well...
Posted by: tcasey 13 years ago
Senior Yellow Belt
Absolutely none. I also haven't had a ton of time to sit down and try and figure it out lately either.
Posted by: jkatkace 13 years ago
Purple Belt
A quick search turns up this gem:


The pertinent part of which states:

Wake on Link Settings

Wakes the computer if the network connection establishes link while the computer is in standby mode. You can enable the feature, disable it, or let the operating system use its default.
NOTE: To use the Wake on Link feature with the Intel® PRO/1000 PT Dual Port Server Adapter, Intel� PRO/1000 PT Server Adapter or Intel� PRO/1000 PF Server Adapter, WOL must first be enabled in the EEPROM using IBAUTIL or iSCSIUTL.
NOTE: If a copper-based Intel adapter is advertising a speed of one gigabit only, this feature does not work because the adapter cannot identify a gigabit link at a D3 state.
NOTE: The network cable must be disconnected when entering into S3/S4 in order to wake the system up by link up event.
Default Disabled
Range Disabled
OS Controlled

The bolding is mine. It looks like Wake on Link only has to do with coming awake from Standby, and what you're doing when you use "Forced" is overriding what the OS does. It also appears that only wake from standby is supported with ACPI computers.

You might find those utilities that let you mess with the EEPROM settings. You can use those with KBOX Scripting to turn it on across your installed base, if those utilities can be run from Windows. We do this kind of thing with the Dell Client Configuration Utility all the time for Dell machines.
Posted by: afadrilan 13 years ago
Yellow Belt
I'm trying to use WOL in our environment to do patching after work hours. I was able to wake the computer but it would try to PXE boot instead of booting from the hard drive and would get stuck on that screen until a key is hit. I've checked the BIOS and PXE boot is last on the list. Is there another setting I'm missing?
Posted by: TJSmithCIQ 13 years ago
Orange Belt
I guess it depends. On a Dell workstation's on-board NIC (settings in the BIOS), your choices are Disabled, Enabled, and Enabled w/PXE. If you were to set it to Enabled w/PXE rather than Enabled, it would ignore boot order and go right to PXE.
Posted by: lindsamw 13 years ago
Orange Senior Belt
Sorry haven't been on these forums for a few days, insanely busy lately. Anyways, I had to do this exact same thing. Here is what I did. I also had to have it work across some broadcoms also. Can provide those registry keys if needed. As far as the intels go, I have had this work all the way back to Dell GX260's (not sure if they required this like the new ones do).

From my kbox scripting page

Verify that “HKLM\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002bE10318}\0001!EnablePME” exists.
Reorder | Add…
On Success
Set “HKLM\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002bE10318}\0001!EnablePME” to “1”.
Set “HKLM\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002bE10318}\0001!WakeOn” to “2”.
Set “[HKLM\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002bE10318}\0001!PnPCapabilities” to “32”.
Log “Intel NIC was found” to “status”.
Launch “$(KACE_DEPENDENCY_DIR)\wol_restart.exe” with params “”.

Those 3 are required for current intel nics with all their current security junk. You also have to restart the DHCP service. Rebooting the PC does not work, you have to actually restart the service. Haven't investigated why, been too busy. The kbox scripting language doesn't wait long enough for it to restart, and has no built in thing to sleep (ya I could just do something to ping for 7 seconds or whatever, but really how hard would it to be just to add a drop down to pause script execution for x time.) I just wrote myself a little autoit script (thats what that wol_restart.exe above is) that shuts down the service, sleeps for 7 seconds, then turns the service back on.

@afadrilan do you have a kbox 2000 with possible PXE events out there for them?
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ