0 vote
We have the following scenario:
Users need to use Server #1 as their point of entry to the infrastructure.
From there, they are able to connect to all other servers (Server #2, Server #3 etc). Server #1 has RDM client installed.
Connection entry to Server #2 is set to use Server #1 as jumphost with RDM jump.
Scenario
User has an RDM client installed on his workstation.
From his RDM client, he executes connection to Server #2.
This connects him to Server #1. And triggers RDM jump - basically opens RDM client on Server #1, and then connects him to server #2.
This basically opens 2 RDM clients, and the user is seeing 3 windows start menus. Which can be very confusing at times.
Are there any possibilities to change this in the future?
So that RDM jump executes in "background", without end user noticing it? So that he would only have 1 RDM client open (on his workstation)?
Hi,
Have you considered migrating from RDM Jump to Devolutions Gateway? Devolutions Gateway works at the network level instead of using nested RDP sessions, and would provide the "background" execution style you want: https://devolutions.net/gateway/
Best regards,
Marc-André Moreau