SecureCRT and PuTTY Saved Sessions Conversion Tool (BETA)

Get Console Session Import Tool is a small Windows app that lets you convert your existing SecureCRT and puTTY saved connections into Get Console connections - it works for Serial, Telnet and SSHv2 connections. Its designed to help engineers with hundreds of saved sessions in these programs get them into Get Console so they can use their iPad rather than their Laptop. Note that this software is currently BETA - we have tested it, however not extensively, and welcome feedback and bug reports via our forum.


Download Get Console Session Import Tool (0.3Mb)

Click Here to see instructions for installing results file via iTunes

 For users that are running into a permission problem running the downloadable .exe file above, we also have a web version of the tool. To use the web version of the tool (also BETA) click here.

Sample Scripts for Get Console's Script Manager


Get Console v1.75 and later support the use of scripts to automate common logon tasks such as sending usernames, passwords, and waiting for the terminal to generate output and then reacting to it. You can build scripts intuitively in the Get Console app, or create them offline and upload your .script files to your iPad/iPhone via iTunes (using the same method as used for uploading .connection files above). The following actions are possible with building scripts:


WaitForString: Waits for the specified string to appear on the console before continuing to the next script rule
SendString: Sends the specified string to the console (with or without enter key afterwards)
SendHexBytes: Send the specified hex bytes to the console - e.g. 0304 for Ctrl-C. Useful for sending things like ESC to console.
PauseScript:  Waits for specified period in seconds before continuing
Message: Displays a popup message to the user - useful to inform Get Console user where the script is upto, or if it has finished
LogStart: Starts logging console output. If console output is already logging this will restart the logging. You can create a specified LogName as well.
LogStop: Stops logging console output
LogUpload: Uploads the console log to the configured remote server. Use this in conjunction with LogStart - this is designed to make it easy to login to a piece of equipment, run a bunch of diagnostic commands and capture to a log file, and then at the end upload the log file automatically to the users secure portal page at the Get Console website.


Sample Script 1: Login with username and password (testuser/testpassword), change to enable mode, execute show version command, save output to a log file and upload the log to secure portal at

top TOP