Custom Action Button "Wake on LAN" for Client

Hello,

Since you have created 2 threads for the same topic, we will respond in the one below since there's already a response in this one
https://forum.devolutions.net/topic31386-custom-action-button-wake-on-lan-for-client.aspx?lastpage=1#post125952

Best regards,

I'm replying here and not in the other thread, because my issue directly relates to RDM (on Linux and macOS), not PowerShell.

This relates to docs over here:

https://docs.devolutions.net/rdm/kb/knowledge-base/wake-on-lan/

Those docs, don't actually work if you're trying to wake a Windows machine via RDM. I can run 'wakeonlan <mac_addr>' on my Mac and the Windows machine will wake up. The same works on Linux, so I know my Windows machine, network adapter, firewalls, etc. are all configured correctly.

However, configuring WoL in RDM, does not work as described. The closest I've found, is to create a custom command under Connection -> Events -> Before Open on RDM, and give it a 10-second delay.

The problem there, is that creating that command, seems to add a 10-second delay to _every single click and action_ destined for that VM. In other words, putting in my password in RDM to connect to the Windows machine, now no longer accepts the [Enter] key, and I have to click the [Ok] button at the bottom of the dialog window. When Windows starts and I can see the desktop, every single click and typed keystroke, _each_ have a 10-second delay. It's INCREDIBLY slow to interact with it.

When I disable that "Before Open" command, setting it to "None", and manually WoL the machine from the macOS shell, everything works at realtime speeds.

I've tried configuring WoL for port 7, port 9 (macOS uses port 9 and that works fine), as well as setting the MAC address under Assets -> Network.

Similarly, right-click Macros/Scripts/Tools -> Wake on Lan also appears to do nothing. I see the progress dialog indicating that it's waiting for the machine to come up, but it doesn't actually send a WoL packet to the Windows machine waiting in an idle state to receive it.

Are there any other workarounds to get this working? I'd really like to avoid having to fish the MAC out of the RDM config, open up Terminal, 'wakeonlan <mac_addr>' from there, then wait 15 seconds, and go back to RDM and connect via RDP as normal.

Thoughts?

Update: I just noticed that if I configure a 'Before Open" command with a 15 second "Post execution pause", I can't interact with RDM at all, until that pause timeout has expired. I can't open a new tab, click on a new host, not even edit the properties of the existing host, until that pause has expired.

That should be a "Post execution delay" before proceeding to the login dialog of the host, not to completely lock out access to the RDM UI itself.

It does feel like some of the code that should be interacting with the specific host itself, has leaked into the RDM application/UI and the RDM host, instead of the remote host being targeted,

Updating from my previous post. It looks like the "Wake on Lan" capability of Remote Desktop Manager running on MacOS does not function at all, without hacky workarounds that involve running pre and post commands that open shells to run 'wakeonlan <mac>' using the Terminal.

Is there any ETA on when this non-working feature will be working, or removed from the UI so it doesn't confuse others who try to get it working like I did, and also fail?

Hello,

We are going to look into the issue, in the meantime can you check if Remote desktop manager has acces to your local network in the privacy & Security options of the MacOs settings?

It can have an impact on Wake On Lan

Best regards,