I am having an issue with the new WOL scheduling wizard… I don’t believe it is working. I’ve tried a couple test scheduled wakeups and no machines are waking up…
I have a WOL forwarder in all but two subnets. I have no clue how to troubleshoot this as the way it’s setup now I don’t see anyway to see what is going on (logs, action history, etc)…
And in the BESWoLMedic.log there appears to be an issue… The below is in there over and over and over…
Wed Sep 15 20:01:23 2010 INFO Running BESWoLMedic.exe version 0.5.16
Wed Sep 15 20:01:23 2010 INFO
Missing the following required parameters:
-WRPASSWORD Password of the BES Webreports user.
Use -help option for more information on available parameters.
Wed Sep 15 20:06:23 2010 INFO Running BESWoLMedic.exe version 0.5.16
Wed Sep 15 20:06:23 2010 INFO
Missing the following required parameters:
-WRPASSWORD Password of the BES Webreports user.
Use -help option for more information on available parameters.
Wed Sep 15 20:11:24 2010 INFO Running BESWoLMedic.exe version 0.5.16
Wed Sep 15 20:11:24 2010 INFO
Missing the following required parameters:
-WRPASSWORD Password of the BES Webreports user.
Use -help option for more information on available parameters.
tscott - my memoryon this is horrible, but I remember when setting up BES 8, you had to create a web reports user for the WOL stuff and youi had to supply that on install I think. We originally had our web reports user set to view only (we used it for something else previous to the plugin service), which we later found out was not enough. It needs to be at least a Normal web reports user. In your case, it does not look like the user info was entered / saved.
Hmm, my thought was that the reg keys in the article were not set. If they are set, I’m at a loss as to why the log is showing - did you blank them out before posting it here?
No, I didn’t blank anything out… The question I had is why is that log file reproducing every day and logging something every 5 minutes for what looks like 24 hours?
I think that is normal behavior. I just looked at our server / logs and we are seeing the same 5 minute polling interval in the logs. It’s just that your BESWoLMedic is failing and ours is not. Here is what a successful log should look like:
Hi tscott (and thanks jspanitz for sharing your expertise!),
The Wake-on-LAN medic runs every 5 minutes and is called by the BES Server-Side Plug-in Service (aka Master Framework Service, or MFS). Every time it is run, it checks to see whether there are any scheduled Wake-on-LAN events pending for which it needs to issue Wake-on-LAN requests. It also checks on Last Man Standing machines and attempts to wake them back up if it determines that any of them have stopped reporting in to the server.
The issue you have seen is likely related to the three registry settings that jspanitz highlighted. Are you still running into issues with Scheduled Wake-on-LAN events? If so, I’d suggest opening a support case so we can troubleshoot this further.
Hope that helps and let us know if you have any other questions about this new functionality.
Not to hijack the thread, but can i request that some functionality be added to the WoL feature.
One, once a WoL is issued (via web reports I presume?), from what I am reading here, it could be up to 5 minutes before the request is processed. Two, there also seems to be some 10 minute rule built into the clients (http://forum.bigfix.com/viewtopic.php?id=4825).
Is there any way to see all this from the console and to know where in the process the WoL request is?
And I don’t believe it did anything. There were some on but I believe that was because users left them on… Some that were off I was able to right click send WOL to them this morning and they powered on correctly…