(imported comment written by Zakkus)
The report Ben is referring to is in our Power Management product, which used to be the only place we offered WoL. We recently pushed a subset of WoL functionality to everyone through the BES Support site, however some advanced functionality (like Wake on Web) you can still only get if you have power management…
There are a few things you might want to check:
-Make sure your endpoints hardware/bios is capable of actually accepting WOL (by default this is turned off on a lot of machines).
-Make sure you dont resend wol requests too quickly. The platform has some optimizations that to minimize network load when waking machines, but this means it wont register a new wakeup to a machine if one has been sent within the last 10 minutes.
-The platform uses the address of the NIC that was used to register to BES when trying to figure out which computer is in which subnet. This means that a computer with multiple NICs will only use one to issues wakes (which can cause confusion).
Also, unless you have a very large subnet, its best to just make every machines a WOL forwarder.