Hello everyone,
I have 60+ subnet and 10 for them won’t be able to waked up.
WakeOnLanMedic is running, and LOG file don’t have any errors…
I have check my BIGFIX Relays… I got one per subnet
I checked LMS… Got 3 per subnet (2 servers and 1 work computer)
I checked WOLFs… all computers are WOLFs ready.
What is very strange is, in one subnet it was working one day, on the day after, it won’t work anymore…
Can you help me to resolve this issue ?
Thanks a lot,
Robin
other thing,
1 subnet = 1 workplace
Every workplace don’t open at the same time.
I have a workplace that’s open at 8 AM and an other at 8.30 AM and other at…etc.
So I have created many schedule to wake up all the workspaces… But sometimes the men who came for opening a workplace, came at 8.06 AM or 8.09, whatever…Then this men must switched ON the circuit Breaker, and when this is done the WOL schedule can work.
Also I got one schedule every 2 minutes…
What I don’t understand, It’s that’s working in all subnets except 10 for them…
owww… One more question. Is it possible thats BIGFIX WOL boot some Computers with a secondary BOOT ORDER ? Because some of my computers boot on PXE with Wake On Lan… And don’t boot on PXE when manual started.
Thanks,
Robin
You have a classic problem with WOL.
Some months ago I had the same problem with a customer(around 10,000 pc with more than 500 different locations.
After researching we found the root causes:
1.- The BIOS has not active the WOL option.
2.- The driver of network card didn’t support the magic packet. The option didn’t show this option.
What is the behavior of those machines that are not woke up?
Do the start sometimes or never?
Have you used another tool to see if the machines are powered on?
Also, check power options on windows 8 and above, Microsoft has identified some issues on those platforms.
Hello,
Thank you for you reply!
WOL is activated in BIOS, and I updated the ethernet card with the latest drivers, the property " Wake on Magic Packet" is enabled.
I think the problem is somewhere else.
I have an other Problem that I have seen.
When the customer come in the office at morning, the circuit breaker is “off”. So the WOL schedule cannot work.
Then the customer of this office push the circuit breaker in the “On” position.
The computers of the office will not Wake On Lan directly. I have programmed the Schedule to check every 2 minutes, but I’ve read somewhere that to not flood the bandwith a wol packet is send every 10 mns. Is It True ?
Do you have an other solution for this ?
Thanks for your help.
Robin
Hello,
You can customize the periods to send a magic packet.
The WOLMedic utility runs every five minutes.
You can configure this if needed. If the interval is too long, for example 1 hour then this means that if the computer is scheduled to be woken up at 9:00 AM, it may get woken up at 10 AM. If the interval is too short, for example 10 seconds, depending on the size of your deployment, 10 seconds may not be enough to process the entire request. If you want, you can take a look at the log and calculate exactly how long it takes to run this command and adjust your interval according. In most cases, default value is the best value.
What you need to do is edit the file “C:\Program Files (x86)\BigFix Enterprise\BES Server\Applications\Config\ BESWoLMedic.xml”
Does the machines are receiving the packet? What you could do is put a sniffer on the machines side just to see if the packet is already sent and received.
This problem that you are describing is very common(No a software bug, but infrastructure issue).
Yes I’ve controlled that the packet come on the PC with Wireshark and I confirm that I received the packet.
But now, I’ve look to customize the periods to send this packet : the periods is by default to 300 seconds.
Edited: Ok I think I’ve found the Problem, I will check this more further.
Thanks a lot for your answers fermt !!
Robin
A last question and I stop waste your time Fermt 
If a wol packet is send, and you shut down the computer… How long it takes before the packet is send a second time ?
Because:
I progammed a wol a 9 AM
In this time it was 10.02 AM, the computer boot with WOL. That’s Ok.
Now I shutdown the computer…
When will the WOL packet be send after this ?
Is there a cooldown ? I ask this because I don’t wan’t that the computer boot with WOL in the night oO
Thank you,
Robin
I’ve read it somewhere there should be a time interval of 10mins.
let me search it for you.
Thank you Techadmin ! I will make some test to see how much time it will need to send a packet again.
Thanks for help 
What was the problem that you found?
Regarding to the last question, for what I remember is that while the machine appears offline the WOL Medic Tool will send the packet, I’m not very sure about this, you can turn on the verbose log level of the tool and take a look. =)
Any other question, let me know.
I’ve waked up a computer with the schedule… worked.
Then I’ve shutdown the computer… and the complete day it doesn’t wake up anymore…
So I don’t know how I can end up this.
For my problem, my customers are too speed lol.
If they come at the office at 9 AM and put the circuit breaker on the ON position.
And if the BESWOLMEDIC periods is 5 mns, then if the periods begin at 8.59 AM, it will try again at 9.04 AM.
Then If the customer check the Computers at 9 AM, no one will be waked up. He must wait till 9.04 AM-
I will look if I find a solution with reducing the period, but not sure it will help.
Thanks for help
You can always modify the default 5min period if that does not work for you.
the file is located here: \BigFix Enterprise\BES Server\Applications\Config\BESWoLMedic.xml
Great, happy to help!