Jump (Remote Desktop Manager Agent) troubleshooting guide

Here is a quick troubleshooting guide to diagnose any issue with Jump (Remote Desktop Manager Agent).

1. Connect to the jump host via Remote Desktop Manager and wait for the Remote Desktop Manager Agent and/or Remote Desktop Manager to start automatically.

2. If the Remote Desktop Manager Agent does not start automatically, follow these verification steps:

   1. Start Remote Desktop Manager.

   2. Go to Tools – More Tools.

   3. Select RDM Agent, then click OK.

   4. Validate the installation and connection.

   5. In the system tray, right-click the Remote Desktop Manager Agent tray icon and click on About....

   6. Validate that Connected and Remote Desktop Manager is installed have a checkmark icon next to them.

   7. Right-click the Remote Desktop Manager Agent 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.

   8. You will be prompted for elevated rights as the Auto Start setting requires it. Click Yes.

3. If Remote Desktop Manager did not start automatically, you can optionally configure it through Windows.

1. In Remote Desktop Manager, start the jump host RDP session.

2. Right-click on the jump host tab and select Agent Status in the contextual menu.

3. Validate that at least the Remote Desktop Manager Agent is connected. There will be a checkmark icon next to it. Remote Desktop Manager may also have a checkmark, which is normal.

1. With the jump host RDP session running in Remote Desktop Manager, start the jump session. It should start in the jump host.

2. Right-click on the jump host tab and select Agent Status in the contextual menu.

3. Validate that there is a "1" next to Remote Desktop Manager Jump Sessions since the jump session is now open.

4. To enable logging, right-click the Remote Desktop Manager Agent tray icon and click on Settings....

5. Check the Log debug messages setting, then click Save.

6. To view the logs, right-click the Remote Desktop Manager Agent tray icon again and click on View Logs....

7. 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:

1. The jump host session will start.

2. Remote Desktop Manager will wait for the Remote Desktop Manager Agent or for Remote Desktop Manager to connect with the client Remote Desktop Manager.

3. The client Remote Desktop Manager will send the jump session to the jump host.

4. The jump session will start.

• It is not recommended to auto-start Remote Desktop Manager because:

  • Remote Desktop Manager Agent 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 Agent 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 Agent if it is not available. This is by design and has the advantage of being slightly faster at starting sessions.