I was wondering if anyone else is using Wake on Lan rules in a large scale and if so, they could share any best practices.

We prefer to do patches at night when staff is not around but cannot guarantee the computers are on and awake, so we thought to send WOL packets to all of them and then schedul patch deployment 5 minutes later.

The process works but is extremely labor-intensive because the WOL rules won't allow wildcards in the destination (computers to wake up.) We have a working solution by using IP addresses and creating rules that cover all the IP addresses in an area, then using the rule's "map IP to name" ability, can get all computers to wake up. but it was a bear creating 20 rules (each rule can only have a maximum of 99 computers to wake up) and since we use DHCP we have to manually go in periodically and remap the IP to Name for each rule.

Has anyone else used the system? Is there a better way? this works but I am very interested in some ideas.


0 Comments   [ - ] Hide Comments


Please log in to comment

Answer this question or Comment on this question for clarity



We created virtual servers that are trunked for all the vlans and bought http://emcosoftware.com/wake-on-lan


Answered 10/09/2013 by: SMal.tmcc
Red Belt

  • very interesting. the purchase was because of frustration over the limitations of DA, or unrelated?
    • We found we needed WOL for other IT apps/tools, also you need to be on the vlan to WOL or need a relay agent. We went with this solution on 4 separate servers. The DA server is on the server subnet only. We have a couple of virtual servers on each campus's that are trunked for every subnet for DHCP and running tools like WOL.
Please log in to comment