The GoTo Community is currently experiencing some technical issues affecting new posts and comments. We are actively working with our service provider and apologize for the frustration.
LogMeIn (LMI) apparently currently does not support wake on LAN (WoL) functionality for any computer which uses "Modern Standby". Here's a link to Microsoft's website for some background info.
According to this document from Dell (link), Dell will no longer support disabling Modern Standby. So that appears to indicate that LMI will no longer support any Dell computer going forward. Realistically, at some point this could affect all computers assuming that other computer manufacturers/OEMs follow Microsoft's push to Modern Standby.
At least in my case, my affected computers will still successfully wake when they receive the WoL packet from any other tool. So although complete and full LMI support for Modern Standby might take some time to develop, it seems like a workaround could be implemented by LogMeIn developers in the meantime. Since these computers do successfully respond to WoL packets, it seems like it should just be a matter of making the LMI servers believe it so that they can send the commands which generate the WoL packet.
I can provide more details, talk to developers (or whoever), maybe even help beta test if desirable. But please add support.
18 Comments
Work on this was paused due to some other required work having a higher priority, but we do plan to pick it back up again and once a solid ETA is available we will post an update as Kate mentioned.
Hello,
I was meaning to follow up on this as well - for the exact same reason as 2ARM5. It will get worse in the coming months as we work to replace desktop/workstation computers which won't officially be supported by Windows 11 (in preparation for EOS of Windows 10).
Somewhat anecdotally, we also did get a new HP laptop for which WoL through LMI isn't working either, and that also appears to be because of Modern Standby. I'm not too upset about that one, because it's a laptop. But I just figured I should share that the incompatibility is not necessarily limited to Dell.
Thanks,
etb
Hi Glenn,
Any update on whether support for WOL on systems that use Modern Standby made it into this years development cycle?
We're a Dell shop. As we replace our systems with newer hardware, we have an increasing number for which WOL via LMI is non-functional.
Hi ProCentPM ,
Is there any update on this?
For full disclosure, I have not needed to deploy any new non-workstation computers recently, so I do not know to what extent Dell has continued forcing Modern Standby on newer BIOS (UEFI). In other words, I have not run into the issue recently, although I assume it is only a matter of time.
I am seeing the same issue, the wake function from the LogMeIn Client sent to some target Dell machines no longer works (nor does it on a handful of Lenovo V520 devices and one HP deskpro model) despite there being other active machines with the LogMeIn controls in the remote network.
The WoL feature in the client routers however is able to send such a signal to all these affected devices and trigger them to start back up.
This suggests something is not working in the LogMeIn Client program when used as an admin support tool, ideally could this not be fixed to use both the current process and to trigger other machines in the remote network to send a standard WoL packet so that the "best of both worlds" approach would ensure the target machine starts back up.
Currently the extra steps in having to remotely connect and send this info is time consuming and such a feature would be really good to have restored to full functionality on all hardware platforms.
