# How to run a command file in PuTTY using automatic login in a command prompt?

I am using the following to login automatically to a remote server and then run commands listed in a commands.txt, like this:

commands.txt contains the following:

ps -elf|grep 'sometext'

However, when I try to do so a new window for PuTTY appears, but it closes and exits instantly after login. As a result, I cannot see the output of the command(s).

I don't understand what's going on here. Am I wrong in my approach or do I need to take more steps to make the PuTTY window pause for some time before exiting?

• Consider to use Plink.exe instead (typically bundled with Putty, remember to include in PATH). I spent 2 hours googling how to specify rsa key in a command line for PuTTY because it's unsafe to hard code passwords. I overlooked Plink solution because, I thought the call had to start with putty. Check answer below mentioning Plink. e.g. Plink.exe -ssh host -l user -i c:\Users\myName\.ssh\myGeneratedPuttyKey.ppk Nov 22, 2016 at 14:55

First you would need to create a separate file containing all the commands you would like to be executed.

Example: I would like to download and install Drupal on my domain using PuTTY. To do that you must:

First create a .txt file. Within that file are the commands. Mine are: "drush dl drupal" next line, "drush si --account-name=[account name] --account-pass=[account pass] --db-url=mysql://[user]:[pass]@localhost/[database name] --y"

After saving that file, you are now going to create a BAT file or type it in the CMD prompt:

• ssh.cmd
• @echo on [for you to see what's going on]
• [Navigate to your PuTTY installation. Mine is:] cd C:\Program Files\Putty
• Start putty.exe -ssh [domain name] -l [username] -pw [password] -m [the directory of the .txt file you created which contains the codes you want to be executed]
• The -m option does not work for me. it is giving out an error saying cannot open command file <path to my text file> Mar 7, 2015 at 2:38
• @user590849 does the path to your command text file have any white space? Because I just Mar 11, 2016 at 16:28

You should use plink.exe (a command-line interface to the PuTTY back ends) and not putty.exe

It seems the only way is to use the -log <logfile> options and then print its content and delete it.

• I cannot use plink or other command line interfaces. Is there any other way to do this
– supportpb
Dec 6, 2012 at 6:14
• @supportpb "I cannot use plink" -- why? what happens if you try? Dec 6, 2012 at 11:37
• @gertvdijk what happens is that he gets fired for using non-approved software on corporate machines... May 11, 2017 at 13:31
• unsupported option: -log Jun 28, 2017 at 11:36

Your approach seems good, however, there's one default setting in the behaviour that's causing you trouble here and probably making you believe nothing's happening.

However, when I try to do so a new window for PuTTY appears, but closes and exits instantly after login

Your session ends immediately after the command was executed, and PuTTY closes the window by default. See the documentation of PuTTY on how to change this behaviour for your session.

4.1.3 Close Window on Exit'

Finally in the Session panel, there is an option labelled `Close
Window on Exit'. This controls whether the PuTTY terminal window
disappears as soon as the session inside it terminates.
• Interesting, but that will affect manual sessions as well... Dec 6, 2012 at 11:43
• @AviramSegal It's a session setting. Just duplicate the session configuration, say session-noclose and use that one in scripting. Dec 6, 2012 at 12:00
• oh session setting, then yes that will work Dec 6, 2012 at 12:01

There would be no issue if you just want to create the batch file to open the Unix machine. Below is the example:

The PuTTY path should be in double quotes, like "C:\Program Files\putty\putty.ext"

machinename = machinename without double quotes