Please enable JavaScript to view this site.

Remote Desktop Manager Jump

Remote Desktop Manager Jump connects to a remote host, often called a Jump Box, Service Host, or a Bastion Server, which in turn connects to other hosts.

This can be compared to RD Gateway from Microsoft and to some extent SSH port forwarding.

The Jump is performed through Remote Desktop Manager Agent. 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.

Remote Desktop Manager must be installed on the jump host for the agent to be able to run commands. The application does not have to connect to any data source, as Remote Desktop Manager only serves as a shell for the agent to run commands.

How does it work?

Both instances of Remote Desktop Manager Jump or Remote Desktop Manager and RDM Agent running on the Jump Host communicate through an RDP channel. Commands are sent securely over the RDP channel and are then executed on the Service Host. Commands include running a script or opening a remote session of any type. It can even launch a VPN client on the Service Host prior to running the remote session.

Please consult the Configure Remote Desktop Manager Jump topic.

Usage scenarios

There are two targeted scenarios:

1. Accessing a secure network through a single host

This allows you to have a strict firewall policy that allows connections only from a specific IP address. This configuration only grants you access to hosts that are accessible from the Jump Box. Let's imagine you have the following infrastructure:

You need to access the remote hosts, but you want to limit risks and expose only the jump host to the internet traffic. This allows you to create strict firewall rules and to open only a single port. Therefore, it forces you to connect to the jump host before hopping to a remote host.

Remote Desktop Manager Jump helps achieve that goal simply and efficiently.

2. Workaround limitations of some VPN clients

These limitations make it impossible to use multiple VPN clients 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 launch the remote session.

Remote Desktop Manager Jump to handle incompatible VPN clients

Remote Desktop Manager Jump to handle incompatible VPN clients