Beta build v22.214.171.124 has brought some minor changes on how you configure Jump, this article has been modified accordingly. For those of you who registered for the RDM Jump Beta, you should receive your email shortly. Follow the steps outlined below to get started using the beta.
Please visit the following link to register to RDM Jump Beta: http://jump.remotedesktopmanager.com/
Enable Jump in RDM
First step is to enable RDM Jump. In your email you received a Jump serial, simply to go Help -> Register Version -> Jump tab and enter the serial.
Configure RDP to Jump Host
The Jump Host is a standard embedded RDP session. Configure it like any other RDP session. Set the computer name, credentials, configure the VPN (if required) and test that it connects properly. On the Information tab set check the "Is Jump Host" check box.
Configure Jump Destination
The jump destination can be any session type (RDP or other). To keep it simple, configure an RDP session to the jump destination. This is essentially no different than any other RDP session. Set its credentials and other session settings you like. Prior to saving make sure to set the jump host by clicking on the jump button. If you created a child session you can set the parent as the jump host if not select the jump host for the drop down list or click the button to select the session. Select Inherited if you are going to define the jump settings in the parent session or parent folder. If not, select Session and select a jump host from the drop down.
Ready to Jump?
So the client side all is done but we need to configure the jump host to accept jump requests. To do this we need to install RDM on the jump host. Download the installer and install RDM (prerequisite Microsoft .NET Framework 4). Once installed start RDM and go to Tools -> RDM Agent. This will start & configure the RDM Agent to accept jump requests (you may be prompted for elevated privileges on start of the RDM Agent). Close RDM and the RDP session.
Note: the use of the RDM installer is important since the installer will register the required extensions with the OS. This won’t be the case if deploy via the .zip file. You can use copy deployment (.zip) or the installer (.exe) to install RDM on the jump host.
Now jumping is as simple as double clicking on the jump destination session. The system will take care of the rest, opening the jump host connection, establishing the secured channel link to the RDM Agent and then initiating the open session on the jump destination.
We actually have to two ways to configure jump. The one mentioned above or via the VPN tab. You can configure the Jump host like a VPN and use the VPN settings like “always connect” or “connect if unable toping/scan”. Great for mobile work forces that may or may not be within the private network. When working from the office you connect directly but when working from home it will connect via the jump host. Follow the discussion here: http://forum.devolutions.net/topic15035-remote-desktop-manager-jump-beta.aspx
In this article I’ve only discussed the RDM Jump capabilities of the RDM Agent. In the next post I will describe in depth the capabilities of RDM Agent and how we are only scratching the surface of what we can achieve. Join the conversation on our forum: Remote Desktop Manager Jump Beta.
For more information about RDM and to register to the Beta, please visit: http://blog.devolutions.net/2014/04/