Remote Desktop Manager is a product that connects to a remote host, often times called a Jump Box or a Service Host, which in turn is used to connect to other hosts.
This can be compared to RD Gateway from Microsoft, or even, to some extent, to SSH port forwarding.
The Jump is performed through our Agent, in the current releases the Agent needs to be CURRENTLY EXECUTING in a Windows Session on the remote host, or set to automatically start upon login. We have decided NOT to have this available through a service at this time.
There are two scenarios which are targeted:
This allows you to have a strict firewall policy that allows connections only from a specific IP address and in turn grants you access to all of the hosts that are accessible to the Jump Box. Lets imagine you have the following infrastructure.
You need to access the remote hosts, but you want to limit risks and only expose the jump host to the internet traffic. This allows you to create strict firewall rules and to open only a single port. On the other hand, it forces you to connect to the jump host first, then to hop to a remote host.
Remote Desktop Manager Jump helps to achieve that goal and hides all of the complexity.
These limitations makes them impossible to use concurrently on the same workstation. In this case, you can have multiple virtual machines, each running a single VPN client. Using these virtual machines as jump boxes allows you to connect to the virtual machine, launch the VPN client, then the remote session.
Remote Desktop Manager Jump to handle incompatible VPN clients
An RDP channel is used to communicate with either an instance of Remote Desktop Manager or our RDM Agent running on the Jump Host. Commands are sent securely over the RDP channel and are then executed on the Service Host. It could be running a script, opening a remote session OF ANY TYPE, in fact it can even launch a VPN client on the Service Host prior to running the remote session.
Please consult How to Configure Remote Desktop Manager Jump.