Input Command for SSH Remote Sessions (Putty)

Input Command for SSH Remote Sessions (Putty)

avatar

Hi,

we use RDM very effective and we would like to use it also for our Linux/Debian/SSH Sessions.

To be exact we would like to execute a (simple) "input" command such as logout ifconfig, tail or shutdown etc. on a remote machine running PUTTY (SSH, Linux / Debian). Ideally on multiple machine with batch execute (e.g. commandline, psexec and others).

Unfortunately it did not work with the Session Script Tool "SSH Command Line". Also not with the Auto typing Macro, because it fails while the focus is not automatically located after opening sessions.

Perhaps there is another simple solution. I remember that it has already worked in the past (approximately).
This applies to the current finals as well as the beta version (11.1.0.0 and 11.1.7.0).

Thanks for your great Support.

Regards
Adriano

All Comments (18)

avatar

Hello,

Select your running sessions, right-click, Execute script in terminal


if you want to add keyboard keys, you must use our commands, for instance {ENTER} or {TAB}

they are listed in the help topic available from the help button in that window.

You also have access to variables.

Best regards,

Maurice

avatar

Hello,

We grew so dissatisfied with Rebex's unwillingness to implement new features that we created our own library based on Putty's code base.

It offers recording as well. Could you try with a "SSH Shell" session type to see if it fits your requirements?

Best regards

Maurice

avatar

Hi,

the own SSH Shell Session Type in RDM is a perfect way to use remote SSH Connections.

The obstacle is, if I am right, I cannot convert the SSH Putty Connection entrys directly to "SSH Shell" (RDM) entrys. I have to create every entry new and one after the other. Is this right ?

Thanks again.

Regards
Adriano

avatar

Hello,

If you right click your PuTTY sessions and go in edit > batch edit > batch actions, there is a batch action to convert PuTTY/Rebex entries to an SSH Shell entry. Keep in mind this won't keep certain settings like the PuTTY session.

Regards,

Hubert Mireault

avatar

Hi,

it was successful!

But one negative thing I noticed. After the conversion of Putty to "SSH Shell" Sessions, in some entries is missing the Host/IP Field. I do not know these entries and I if I connect to one entry like this, RDM freeze completely and I can only kill it over the task manager.

Thanks again for your great support.

Regards
Adriano

avatar

It's possible entries miss the Host field since you aren't required to put a host in PuTTY entries (with certain configurations) due to the fact that PuTTY sessions can specify the host. This is probably why you have sessions with no hosts.

As for the freeze when no host is specified, I'm not sure we can do much in that regard but I'll ask Denis who is in charge of our terminal integration. This technically should only happen when converting from PuTTY since when creating a new SSH Shell entry, you are required to enter a host.

Regards,

Hubert Mireault

avatar

I've looked into this and RDM seems to freeze when you connect with an SSH Shell with no host set and then close the tab. Can you confirm that the freeze happens when you close the tab? We'll add a check so it doesn't try to start the session if there is no host.

Regards,

Hubert Mireault

avatar

Yes, I can confirm that the freeze happens when I close the tab.

Regards
Adriano

avatar

Unfortunately I have found a negative characteristic of SSH Shell. The entire number keypad and also the "Enter" key no longer works. When I activate the option "Local echo" under the entry settings / Terminal the keypad works partially but not at expected (backspace clears more than normal, Enter key writes an M etc.)

Regards
Adriano

avatar

For the keypad, could you set in the Terminal tab the "application keypad mode" to disable? If this doesn't work could you send me an export of your session (without the host and credentials) so I can see the settings you have and try to reproduce? You can send it at hmireault (at) devolutions.net

Regards,

Hubert Mireault

avatar

In RDM there is always a solution!
Thanks, that was it.

If I am right, it is not possible to overwrite all these settings (Terminal, Application keypad mode etc.) once for all entrys with a BatchAction ..?

Regards
Adriano

avatar

If you want to set the default value for all your SSH Shell sessions you can go in File > Options > Types > Terminal and change the keypad mode there. :)

Regards,

Hubert Mireault

avatar

Hi, the possibility to set the default value for all SSH Shell sessions in File > Options > Types > Terminal is exactly what I wanted, but when I set the option to "Disable" and restart RDM, the value is reset again to "Enable" :-).

A quick test showed me that other values are not affected from this.

Regards
Adriano

avatar

Thanks for the feedback Adriano, I'll take a look.

Regards,

Hubert Mireault

avatar

Hi Maurice,

still one more thing...

The reason why I opened this thread was, to can "Execute script in terminal".

Now I have converted all my putty to SSH Shell Sessions ( >60 ) and when I try to Execute a script in terminal (whether "Commands" or "Typing Macro") RDM freeze completly!

I don't want to keep you busy :-).

Regards
Adriano

avatar

well I use this successfully in every demo, I will need more details.

How many sessions are selected at once?
Are they already running or you have elected to have the tool to launch them automatically?

Maurice

avatar

In this case only for one session. The session was already running.

Unfortunately now it works again with the same entry, without any problems. I'll observe it.

avatar

As for the issue with the value in File > Options > Types > Terminal not saving, this will be fixed next version.

Regards,

Hubert Mireault