RDM Jump

What about things like HP iLO Console executable, Veeam Console, VMWare PowerCLI; how do they operate? Where do their applications need to be installed?

Hello,

RDM will be installed on WORKPC and MANAGERPC so that you can establish the jump properly.

Indeed, the jumphost would need to be a TS server to have several connections opened on the same jumphost since RDP is the protocol being used to establish the connection.

RDM license are calculated per user, not per installation, so would use the same license on the jump host.

For more information on RDM Jump, I suggest consulting this help article. There's also a video in this article if you want to see RDM Jump in action.
https://help.remotedesktopmanager.com/overview_whatisrdmjump.htm

Hello,

Regarding iLO, Veaam and VMWare, yes, you would need these applications installed on your computer to use them in RDM.

RDM will not replace them, you still need license for these applications.

Best regards,

So with Veeam B&R Console, or an iLO HTTP page, or an iLO Console application - how does that work if loaded on the WORKPC? Being a separate application, how does it know to tunnel via the RDM Jump tunnel?

Is every app/plugin/tool supported? Or are there limitations?

Hello,

RDM Jump open a RDP channel to the jumphost and from there, you can open any session type. The traffic will go through the jumphost automatically.

It's possible to configure a jumphost on any type of session. However, the jumphost needs to be an RDP session.

Best regards,

Ahh. I've had a play. Not as nice as I thought it was going to be. This literally opens a standard RDP connection to another Windows PC, logs in, opens RDM on the remote host, and then opens the second connection.

So it looks like a windows within a window - you lose a fair bit of screen real-estate as you still have some of the RDM bars up the top even with the ribbon and navigation hidden. And you need to hide the Start Bar on the remote PC.

You should make RDM have a full screen mode - no tabs/title; nothing at all. At least then you can reclaim that real estate.
It'd also be nice if the whole connection was a bit more transparent. Hide the fact that it is RDPing to the remote PC. Hide the remote RDM starting up. Hide it all until you are presented with the end connection running in full screen mode. Make it feel less like it is window-in-window.

And to clarify this statement;

You need these applications installed on the RDM Jump Host, not the RDM client that has the Data Source.

The important thing to note is, RDM connects to a PC via RDP to the RDM Jump Host. On the RDM Jump Host, RDM fires up and then behaves exactly like it would as a normal RDM PC.
In fact, alternatively, you can just RDP to a RDM PC, and load your RDM with Data Source on that.

Michael,

You are correct, RDM Jump is not the holy grail of jump servers but rather a tool to help you better manage RDP jump host situations.

I would suggest you start your remote jump sessions as "Undocked". This will cause the session to start full screen and save precious screen real estate. You can also hide the top ribbon and left tree view since they are not needed.

Also note that Jump gives a you a few advantages. Log shipping is an example. If you were to have a standalone data source on the jump host with the sessions, it can reach then you would need to connect to the jump hosts to get logs. Now imagine you have multiple jump hosts. With the way Jump works is the RDM installed on the jump host is a dummy RDM and the ship back every log (connect/disconnect). This way everything is centralized in one data source.

Note: RDM Jump is not designed to replace an RD Gateway server, for example.

Best regards,