Open DarrylJR opened 4 years ago
This does occasionally happen. Some computers do not respect the two commands and only see the command as Hibernate, or only as Sleep. There's nothing much we can do on our end.
I can't get this to work correctly at all with workgroups. If I try to "sleep" the PC, it either just logs the user account out to the lock screen or puts me in hibernate which I cannot remotely wake up from. Also, if I try to use "custom" and put "rundll32.exe powrprof.dll,SetSuspendState 0,1,0" it actually powers down my host pc that is running the WOL tool, not the remote host ;) I did have to add that registry key to the remote system in order to accept remote access commands but still no luck.
@eric-zspace wrote:
… puts me in hibernate which I cannot remotely wake up from …
I can remotely wake systems from hibernate (and sleep) using Aqua Tech WakeOnLAN, but it takes a lot of settings being correct, including (1) BIOS, (2) network interface power settings and network interface advanced properties, (3) Windows settings (e.g., disable hybrid sleep), (4) for a RealTech network interface, registry changes, and (5) the format of the magic packet (configure in Aqua Tech WakeOnLAN). The setting might be different based on the system and network interface manufacturer and model. For example, I have a bunch of Lenovo ThinkCentere M93p desktop PCs that wake fine with an all networks broadcast (255.255.255.255) but newer Lenovo ThinkCenter M920S desktop PCs will not wake up with that magic packet and will only wake up with a subnet broadcast (for example, for a /24 network x.y.z.255), which can be configured on he Wake Up tab on Aqua Tech WakeOnLAN machine properties.
Is your not being able to wake from hibernate because of the way the system is powered down or is it because the system is not waking when receiving a magic packet? Can you put the machine in hibernate from Windows and can wake it OK, this is, it is only when you remotely put the machine hibernate that it does not remotely wake up? If you cannot wake from hibernate that was initiated via Windows (not remotely), the problem is likely one of the 5 factors that I listed above. If so, let me know and I can send you more details on how to set those factors (works on most computer manufacturers/models, but no guarantee).
When shutting down a host and selecting the Sleep radio button, it seems to put the system in Hibernate instead of sleep, that is, Sleep and Hibernate do the same thing. (From the Windows power button, Sleep works as expected.)
Also, the buttons appear in an unusual order. They are Shutdown, Sleep, Hibernate, Logoff. Most systems (e.g., Windows Power button) lists the options in order of how much power is used, e.g., Shutdown [S5], Hibernate [S4], Sleep [S3], Logoff.