Starting with 2026.1, [Devolutions Agent](https://docs.devolutions.net/rdm/support-resources/devolutions-agent/) now offers enhanced utility for the jump scenarios with RDM Jump considered as legacy.
RDM Jump and RDM Agent might not work with corrupted Windows profiles.
RDM Jump can run commands on one or multiple remote hosts at the same time. Since Remote Desktop Manager uses a secure RDP channel to communicate with the RDMP Jump agent, it can only operate against Windows-based hosts.
It supports both environment and Remote Desktop Manager variables. Remote Desktop Manager variables (i.e. $HOST$, and basically all the ones surrounded by dollar signs) are resolved on the client against the running session, while environment variables (i.e. %windir%, basically all the ones surrounded by percent signs) will be resolved on the remote host at execution time. You can use Remote Desktop Manager variables while running file-based scripts (.ps1) within the command. The file based script variables (.ps1) will be resolved prior to sending the script to the destination host.
RDM Jump can be used to run scripts from another Remote Desktop Manager installation. Since it uses an RDP channel for communication, it saves you from remote management headaches such as opening various ports in your firewall. This requires the lightweight installation model of just the agent package (Methods #2-4 below).
It is also used by Jump hosts session in Remote Desktop Manager for supporting many technologies. However, it does require a full Remote Desktop Manager installation on the remote host for those features.
Installing RDM Jump on a remote host can be achieved in 4 different ways:
RDM Jump must be configured to automatically start when a Windows session is established. Method 1 below performs that automatically, but in other cases, you must configure this manually using Windows features (Startup folder or Run registry key). Please consult the documentation of your operating system for details.
-
Install Remote Desktop Manager and select Tools – More tools – RDM Jump (Deprecated). It will launch and auto-register the agent to automatically start with Windows.
-
Download RDM Jump from Devolutions' website, and install the agent on the remote computer.
-
Copy the files Devolutions.Utils.dll, Devolutions.Windows.Utils.dll and RDMAgent.exe from the installation folder of the Remote Desktop Manager version that is used by your team, or download the zip file containing those files from Devolutions' website and deploy them on the remote host in the folder of your choice.
-
Via Chocolatey.
choco install rdmagent
Many new users using this technology wonder why a full installation of Remote Desktop Manager is required. There are three factors that make this a good solution:
Remote Desktop Manager on the remote host does not require a workspace, it's an empty shell.
The logging of the activity is brought back to your workspace.
Every technology supported by Remote Desktop Manager can be used remotely.
To launch a script through the RDM Agent, you first need to open an RDP connection to all the machines you wish to execute the script on. Once opened, select all the opened sessions in the navigation pane, right-click them and select Execute Script via Agent.
Execute script via Agent only needs the RDM Agent when the script is executed from the Quick Script tab. Remote Desktop Manager needs to be fully installed on the remote computer when the script is executed from the Scripts/Tools tab.
| OPTION | DESCRIPTION |
|---|---|
| Message | Send a message to all targets. |
| OPTION | DESCRIPTION |
|---|---|
| Run | Indicate the command line that you want to execute. |
| Use Default Working directory | Use the default working directory when connect to the session. |
| Run as Administrator | Elevates the process to run as an administrator. |
| Keep open | Keep the window open after the execution of the command line. |
| OPTION | DESCRIPTION |
|---|---|
| Command | Indicate the PowerShell command that you want to execute. |
| Filename | Select a PowerShell file on the network or on the computer. |
| Arguments | Arguments that are appended to the Command. |
| Run as Administrator | Elevates the process to run as an administrator. |
| No Profile | Does not load the Windows PowerShell profile. |
| No exit | Does not exit after running startup commands. |
| OPTION | DESCRIPTION |
|---|---|
| Run | Select the program or file that you want to execute. |
| Arguments | Arguments that are appended to the Command. |
| Use Default Working directory | Use the default working directory when connect to the session. |
| Run as Administrator | Elevates the process to run as an administrator. |
| OPTION | DESCRIPTION |
|---|---|
| Scripts/Tools | Select a script or a tool session that you have already created in Remote Desktop Manager. |
Search for a script or a tool you wish to execute through the RDM Agent.
| OPTION | DESCRIPTION |
|---|---|
| Open all connections | When multiple sessions are selected to Execute Script Via Agent, it will open all the selected connections. |
| Delay | Enter the time delay between opening each selected session. |
Open an RDP session, right-click on the session and select Agent Status. The Agent Status will show you that Remote Desktop Manager is installed on the remote computer or not, that the RDM Agent is active or not, and how many RDM Jump sessions are opened.
Here is a quick troubleshooting guide to diagnose any issue with Jump (Remote Desktop Manager Agent).
Connect to the jump host via Remote Desktop Manager and wait for the Remote Desktop Manager Jump and/or Remote Desktop Manager to start automatically. If the Remote Desktop Manager Jump does not start automatically, follow these verification steps:
-
Start Remote Desktop Manager.
-
Go to Tools – More Tools.
-
Select RDM Jump, then click Execute.
-
Validate the installation and connection.
-
In the system tray, right-click the Remote Desktop Manager Jump tray icon and click on About....
-
Validate that Connected and Remote Desktop Manager is installed have a checkmark icon next to them.
-
Right-click the Remote Desktop Manager Jump tray icon again and make sure that the Auto Start setting has a checkmark next to it. If not, click on it to enable it.
-
You will be prompted for elevated rights as the Auto Start setting requires it. Click Yes.
-
If Remote Desktop Manager Jump did not start automatically, you can optionally configure it through Windows.
-
In Remote Desktop Manager, start the jump host RDP session.
-
Right-click on the jump host tab and select Agent Status in the contextual menu.
-
Validate that at least the Remote Desktop Manager Jump is connected. There will be a checkmark icon next to it. Remote Desktop Manager may also have a checkmark, which is normal.
-
With the jump host RDP session running in Remote Desktop Manager, start the jump session. It should start in the jump host.
-
Right-click on the jump host tab and select Agent Status in the contextual menu.
-
Validate that there is a "1" next to Remote Desktop Manager Jump Sessions since the jump session is now open.
-
To enable logging, right-click the Remote Desktop Manager Jump tray icon and click on Settings...
-
Check the Log debug messages setting, then click Save.
-
To view the logs, right-click the Remote Desktop Manager Jump tray icon again and click on View Logs...
-
Close the jump host RDP session. By doing so, both the jump session and the jump host should close.
If you perform a full test, here is what should happen in chronological order after opening the jump host session:
The jump host session will start.
Remote Desktop Manager will wait for the Remote Desktop Manager Jump or for Remote Desktop Manager to connect with the client Remote Desktop Manager.
The client Remote Desktop Manager will send the jump session to the jump host, starting the jump session.
-
It is not recommended to auto-start Remote Desktop Manager because:
Remote Desktop Manager Jump is faster to auto-start.
Auto-starting Remote Desktop Manager may cause the jump to timeout.
We therefore recommend that you let Remote Desktop Manager Jump start Remote Desktop Manager on the first jump.
-
If Remote Desktop Manager is slow to start on the jump host, especially if it is running on TS or similar environments. See Startup Performance for a few quick solutions to improve Remote Desktop Manager startup times. You can also uncheck the Show Splash screen setting in File – Settings – Application – Application Startup to disable the splash screen.
-
The client Remote Desktop Manager will favor direct communication with Remote Desktop Manager if it is already connected, and will only fall back to Remote Desktop Manager Jump if it is not available. This is by design and has the advantage of being slightly faster at starting sessions.
Share your feedback