Apologies if this has been answered elsewhere, but I have tried searching the forum and reading the guide and can't find the answer.
I have a Windows Server 2016 that we use as jump server. I have installed RDM on the server. I have set the that host as a Jump Host in RDM. I have set that Jump Host as the jump server for RDP connection we have in RDM. When I click on the RDP connection for the server that is set to use jump server it just times out and nothing happens.
If I logon the jump service, launch RDM, and then try again it works. So obviously RDM needs to be running on the Jump server, not just installed. However, the issue I have is that I'm not always logged onto the Jump Server and have RDM running on it.
Is it a limitation of RDM that you have have to constantly logged onto the jump server and have RDM running to allow hosts to jump from it? Or have I done something wrong?
You are almost there. Please make sure you have the RDM Agent installed and configured to "Run on startup" it will take care of starting RDM when it's not yet running and relay the message to it when it is running.
Since you already have RDM installed on the jump host, start RDM > Tools > More Tools > RDM Agent and click, it should prompt for auto-start, if not tray icon, click auto-start.
Best regards,
Stéfane Lavergne
Thanks for the reply. I have installed the RDM Agent, but I still getting this and it times out. I have confirmed that RDM Agent is installed and set to auto-start. I've also ensured that the Agent is allowed through the local server firewall.
You don't need to modify the firewall rules for RDM Agent, it communicates over the RDP channels within the RDP protocol.
Let's first test the RDM Agent. Start an RDP session to the jump server (normally), once opened in RDM (client side) right click on the Tab and select "Agent Status" This will give you the connection status of RDM & RDM Agent, since RDM isn't started on the jump host it won't connect but that is ok since RDM Agent will connect. If not connected, close the window and reopen it (there is no refresh :-( ) Now is it connected? Chances are we need to increase the timeout delay for it to work.
In RDM (client) File > Options > Types > RDP > Jump > increase the "Agent connection time out" to say 30 seconds. This should give plenty of time for the Windows sessions to start and start all its start-up tasks (including RDM Agent).
Best regards,
Stéfane Lavergne
I've started an RDP session to the jump server. Once opened I checked the Agent Status and it had a Red Cross against RDM Agent, as expected there was a Red Cross against RDM too.
If I login to the RDP session I get a Green Tick for Agent Status.
I did increased the Agent Connection time out to 60 seconds just to be sure. Tried to connect and still does not work.
So:
If I RDP to the jump server without logging in I get no connection the RDM Agent
If I RDP to the jump server and login I get a RDM Agent Connected status
It appears that in order for the RDM Agent to be running I need to be logged onto the jump server.
Yes, you are correct, the RDP session must be logged in for RDM Agent to work. Just having the RDP session, started isn't enough since RDM Agent is sessions based.
In the future we would like to have a session-less RDM Agent but we are not there yet.
Best regards,
Stéfane Lavergne
Ok thank you for your help Stefane.
One final question - we have multiple people who use the jump server. Do every person who wants to use RDM, via the jump serve, have to be logged into the jump server, or just one person so the Agent is running?
Hej Adrian01.
on the picture you posted you have a 'LegalNoticeCaption' / 'LegalNoticeText' configured on your jump server to make sure anyone who connects first has to 'approve' . we have the same, in that case make sure in you jump server properties with 'is jump host' you clear the Show Wait for RDM agent dialog
in that way you're able to press on the 'Ok' button that allows you to logon.
Regarding your other question with multiple people using jump: it is just a 'Terminal server' / 'Remote desktop connection server' where every user has his/hers own session and logs on interactively. this will also mean you may have to configure the Jump server as a RDS server to allow > 2 users to connect, including RDS licensing etc.
Regards, Ben
@Ben, wow thank you for the help, I had not noticed the "legal notice". That's what I love about this community, people help others, amazing.
@Adrian01, Ben is correct, give it a try all should work as expected.
Stéfane Lavergne
@Ben Thanks for that. That really help me. I was wondering we I couldn't click on the "OK", it works perfectly now.
Thanks all for your help.