WaykNow Suggestions
Getting to grips with Wayk and its integration into RDM, we have come up with two suggestions.
When a remote user starts up Wayk and calls us to connect to him, I need to be able to find the appropriate session in RDM or a matching bookmark in Wayk.
Why not use an appropriately set FriendlyName as an ID. The only problem is that this name does not appear on the Wayk screen. So suggestion 1 is to put it there. Should be quite trivial to do.
The second relates to the dual function of Wayk - to make a connection or to receive a connection. I believe the two should be split.
The odd times I have used TeamViewer it has always worried me that just to connect to a remote user I actually have to open up my computer for an external connection. If I forget to close the app then my computer remains accessible.
So the suggestion is that Wayk should open in 'Take Remote Control' mode. This would also save a spurious connection to to the Den server.
If someone wants to open up to receive a connection then they can move a slider or the like and switch modes.
One step better would be to add a default setting and/or it should remember the previous setting as it was when the app is closed.
All Comments (3)
Hi,
"Why not use an appropriately set FriendlyName as an ID. The only problem is that this name does not appear on the Wayk screen. So suggestion 1 is to put it there. Should be quite trivial to do."
This appears to be linked to your other question, and I answered after you wrote this one, so you haven't seen my answer yet. Would automatic machine name aliases be sufficient? We now have a feature to create aliases in two forms:
<MachineName>
<MachineName>.<DnsDomainName> (domain-joined machines only)
So for instance if my machine is called "devolutions100" on the "devolutions.loc" domain, I will get two aliases usable as target ids:
devolutions100
devolutions100.devolutions.loc
Since these are added as Wayk aliases, they will be used to connect through Wayk Den, and no direct connectivity is required.
"The second relates to the dual function of Wayk - to make a connection or to receive a connection. I believe the two should be split."
I have a little scoop for you, if you can keep it quiet :) We are seriously considering to make such a move this fall, but until then, the application will remain dual-purpose (client + server). The reasons you gave are part of what motivate us to make this change.
Best regards,
Marc-André Moreau
Thank you. I did not realise I could have a private Wayk Den.
Looking at the notes I see it is a complex process to set up. Before starting, could you advise whether the following would work.
- A CentOs VM running on one of our servers, configured as necessary running WaykDen.
- WaykNow clients configured to point to our domain with an explicit port number so that connections can be routed to the VM by our router.
Hi,
CentOS should work, as long as you install docker correctly. We recommend using Ubuntu as this is was we use, but CentOS should work just fine.
As for the connection routing, if both machines are on the same network, a direct connection will be made, otherwise the connection will be done through a relay server. By default, Wayk Den points to our own relay servers. I would recommend getting it to work with our relay servers first, and then work on deploying your own relay servers (https://github.com/Devolutions/WaykDen-ps/blob/master/docs/getting-started-relay.adoc).
With you own relay servers in place, you will have a 100% independent deployment.
Best regards,
Marc-André Moreau