Can't connect to Unattended session with RDM, but CAN with the standard Wayk Now client

Hello

Thanks for the detailed description of the issue.

We should start by just confirming that the session is configured properly in Wayk Now. What do you have for "Wayk Den source" and "Connection mode"? I would expect them to be "Default" or "Cloud" and "Host", respectively.

If you can confirm the above, can you export an example of a session and provide it to me? Either via PM, or at support@devolutions.net.

Thanks and kind regards,

For Wayk Den Source, it was originally set to Default, I then tried changing it to Cloud, I then tried both combinations with "Prefer relay" checked. I currently have set back to Default and "Prefer relay" unchecked.


Connection Mode was changed to Secure Remote Delegation, and I have at one point changed it to Default and also Secure Remote Password, just to try to get it to give me some sort of different error, but never did. I currently have it set back to Secure Remote Delegation.


Also, I have tried to see if the Unique ID needed to be with a space, and also without a space, neither change made any difference.

Thank you for engaging, I have sent the export to you via PM.

Also, just to share additional information, the error I get is nearly instantaneous after clicking "Open" in RDM, maybe a ¼ of a second. I am able to see that there is some other dialog box that spawns, but the error comes so quickly I can never see what the other dialog box is.

Hello again

Thanks for providing all the extra details and the .rdm file. Fortunately, I think the solution here is pretty straightforward; so I'll cover that first and then explain all the details.

The .rdm you sent me should work, with the small change of selecting "Host" instead of "Unique ID" under the connection mode dropdown. Note that when I tried that on my side, RDM replaced the value with the connection name. So you will need to re-enter the 6-digit Wayk ID of the machine.

Please try that and let me know if it works.

Thanks and kind regards,

That was it! Thank you!


Additionally, I have three feature questions and I'm wondering if I'm just not doing something correctly, or if it's a feature that is planned for a future release or not considered currently. Please let me know, and I can create a new thread for a proper feature request if needed.


1. Login. I see that there is the ability to send Ctrl+Alt+Del to bring up the login screen, but then, the tech needs to know the password for that account. With GoToAssist, we can store the password on the far-end device in the Unattended Client systray app. Then when we connect and send the "Ctrl+Alt+Del" GTA responds with:

"You have a stored password for Server123\Administrator.Log in."

Clicking on the words "Log in." will log you in and no one needs to know what the password is. For a team with a bit of a high turn over, it is nice to be able to allow people to connect to systems without having to share the password with them. This is one of the things we love about RDM. Tier 1 techs can connect to systems, but never know the password they are using to connect to the system. Being that a Wayk Now system already has a section for Username and Password, which I assume can be controlled via user profile as to whether they can unmask a password or not like an RDP session; it seems that this could be used to prompt a login to the remote system after "Ctrl+Alt+Del" is sent.


2. File Transfer. I can see that I can send a file to the remote system, but I do not seem to be able to pull a file from the remote system to my local system. This is important for gathering log files or packet captures that we want to review on our local machine as the tools used to review these items are not always installed on the remote system.

3. Scroll wheel support

Hello again

Thanks for confirmation of the fix and the additional feedback!

I'll start by addressing the original issue:

There are multiple ways to address a machine using Wayk Now: if you have a direct route to the machine, you can use hostname or IP address. For ease of use, especially over complex network topologies (like in your case), we recommend the 6-digit numeric Wayk ID. There is a further mechanism, using the machine's unique ID (this is a UUID generated at install time).

In RDM, "Host" means either the 6-digit Wayk ID or the hostname / IP address; "Unique ID" refers to the machine UUID. I see that the terminology we're using here is confusing and I'm going to discuss that with my colleagues on the RDM team.

There is no functional difference between "Default" and "Cloud" for the Wayk Den Source at the moment. You can also disregard the "Prefer Relay" option if all your Wayk Now installations are 2020.1.1 or newer (it sounds like they are). Finally, it sounds like in your case, you should leave the authentication as you have it to "Secure Remote Delegation" - this uses your Windows credentials and can be used to connect to the system even if it's unattended.

For the follow up questions:

1. Right now, Wayk just follows the "physical" session on the remote machine - the console is shared exactly as if you are sitting in front of it. We don't interact with login sessions at all. Hence, to solve this issue currently, I believe we would have to try and automate the Winlogon screen by injecting keystrokes or similar. The good news is that we currently have a dedicated team on improving this - we're working on giving Wayk the ability to start new, or join existing, login sessions, rather than just shadowing the physical console. That will enable the functionality you're asking for via RDM. I don't have a timeline for those improvements in Wayk, or RDM, other than to say we are working on it currently.

2. This is possible but perhaps the UI is non-intuitive. On the remote system, if you locate and right-click on the Wayk Now icon in the system tray, you will be able to access a "Sharing" context menu which allows initiating a file transfer from the remote system back to yourself. We would welcome suggestions for how this could be better integrated into your use case.

3. This was addressed in 2020.1.0.0, which is on the beta channel. So you can expect that soon in the stable RDM.

Please let us know if you have further feedback or questions.

Thanks and kind regards,