AB Tutor Cloud cannot issue Wake on Lan commands from the server. As such, scheduled Wake on Lan is currently unavailable. Solutions are being explored to reenable this feature in the future.
Wake on Lan commands can still be triggered directly from the Console, provided the Console is on the same subnet as the target devices.
There are a number of things to check for Wake on Lan problems. Some of these are AB Tutor specific, others are general operating system settings.
In Windows 10, the default behaviour is to only allow WoL startup from suspend or hibernate states. This is to allow the computer to shutdown completely, rather than leaving the network card powered. This default can be turned off by turning off Fast Startup, either manually or with a registry setting:
Alternatively, edit the registry, go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Power and ensure that the DWORD HiberbootEnabled is set to 0. To turn it back on, set that key to 1.
Some computers will shut the network card down when they're turned off to save power. Some will only respond to WoL if the machine has been started up and shutdown since it was last unplugged - ie after it is plugged in to the mains, WoL won't work until it's been powered on and then off.
Try using an independent test tool. This will remove AB Tutor from the equation and just test WoL against your client.
Install the tool from here for Windows or Mac OSX.
Test WoL with the MAC address of the computer you want to wake using the tool.
If the test tool works and AB Tutor doesn't, please contact us with as much information as you can offer, and we will see if we can help.