I am trying to follow the KB http://support.bigfix.com/cgi-bin/kbdirect.pl?id=1200 to create an app to do WOL through the BF server. The problem is my BF server returns a 404 for the URL http://.com:52311/WakeOnLAN.wsdl . I can access the URL http://.com:52311/WakeOnLAN but it returns the following error.
is asking for proxy authentication so I do not think it is fully proxy aware as we deliver proxy settings (and exclusions which the BF server should be) through DNS.
We don’t actually host the WSDL file on the root server. I’m not sure why the script on that KB article implies that we do. The approach I would take is to copy the text of the WSDL from that KB article, put it into a .wsdl file, and then point your SOAP framework at that .wsdl file. In the code, you will need to tell the SOAP framework to make its requests to http://.com:52311/WakeOnLAN. The KB article gives examples of how to do this for SOAP::Lite in perl, and .NET using C#.
ok, figured it out now. the exe in the kbid 555 runs a perl script and when you have an environment variable set (http_proxy) to allow other perl scripts to work via proxy it will force this one to run through the proxy as well. remove or rename that variable and it works.
I was curious about the big fix-wol-trigger-0.6.0.0.exe does this only work if you have purchase the WOL feature in power management. I ran this in command line and it comes back WOL packets successfully sent! but I wonder since it’s using the web report server I currently don’t have any WOL option in my web reports.
There is some setup that needs to be done for the agents before the WoL packets will get properly routed. The wol-trigger tool “worked” because it properly asked the server to wake up the computers. But if you don’t have WoL forwarders in your subnets, then the computers won’t get the WoL packets. The power management site has the necessary Fixlets/Tasks to help you configure all of this.