Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

When using SSH jobs users might experience limitations that are specific for Windows operating systems. One reason for such limitations is the fact that SSH is not available with the OS but is implemented by third party products.

  • A complete re-write of the JITL SSH Job is provided by
    JITL-123 - Getting issue details... STATUS  

When using this JITL job please consider our experiences with some SSH products for Windows.


Copssh is a Windows SSH Service based on the Linux SSH Implementation OpenSSH provided by Itefix in collaboration with Cygwin. We experienced the following limitations when using Copssh 5.0.3:

  • Interactive Shell
    • Problem
      • The Windows shell can only be used as an interactive shell and does not support command or script executions.
      • The reason for this behavior is the fact that newer versions of CopSSH do not support the non-interactive shell any more.
      • For details see
    • Solution
      • Using the "Bash and sFTP shell" with Copssh will work for Windows systems when using the cygwin supported Linux commands.
    • Examples for Limitations
      • Limitation: the Windows command set will not be recognized. 
        • Workaround: use export instead.
      • Limitation: the % special character to mark an environment variable such as %VARIABLENAME% will not be recognized.
        • Workaround: use $VARIABLENAME instead.
        • Hint: be careful when using mixed case spelling for environment variables.
      • Limitation: executing chained Windows commands in one line with the command delimiter & or && will result in executing only the first command.
        • Workaround: use the Linux command delimiter ";" together with the proper Linux command instead.
      • Limitation: prefixing a command with cmd /C does not execute the specified command.

bitvise SSH Server

  • Environment Variables
    • Limitation: setting environment variables with set would not allow using this variable in further commands.
    • Example: unsuccessful use of an environment variable in a subsequent command:
      • set TESTFILE=test.txt
      • echo MYPARAM=myTestParam >> %TESTFILE%
      • This example shows that %TESTFILE% is not substituted, instead a file with the name %TESTFILE% is being created and MYPARAM=myTestParam is being written to that file.



  • No labels
Write a comment…