Securecrt License File Location
Barb Magario
To find out where SecureCRT/SecureFX are currently storing configuration files, open the SecureCRT or SecureFX Global Options dialog and select the Configuration Paths category.
SecureCRT/SecureFX users are typically prompted for the configuration folder location the first time they launch the application. Different versions of SecureCRT/SecureFX running on different versions of Windows will store the configuration folder in different default locations. So be sure to check the Global Options dialog, rather than assume your current configuration is stored in the same place shown in the graphic above.
To back up your configuration, browse to the location of your configuration folder as shown above and copy the entire folder contents to your backup location. You can also choose to add your configuration folder to a compressed archive such as a zipped folder.
Tip: If you copied the configuration folder path from the Global Options dialog to the Clipboard, you can paste the path into the Windows Explorer address bar and press ENTER to navigate to the configuration folder more quickly. To activate the Windows Explorer address bar in preparation for pasting, press ALT+D.
To restore your configuration, browse to the location of your backup files and copy them to your configuration folder. If you backed up your configuration to a compressed archive such as a zipped folder, extract the contents of the archived file to your configuration folder.
SecureCRT, SecureFX, VShell, Entunnel, AbsoluteFTP, Basepoint, We Listen. Then We Make Software Better., VanDyke Software, and the VanDyke Software logo are trademarks or registered trademarks of VanDyke Software, Inc. in the United States and/or other countries. All other trademarks or registered trademarks are the property of their respective owners.
Copyright 1995 - VDS_year(); VanDyke Software, Inc. All rights reserved.
Here you can control cookies using the checkboxes below. Some cookies are essential for the use of our website and cannot be disabled. Others provide a convenience to the user and, if disabled, may reduce the ease of use of our site. Finally, some cookies provide anonymous analytic tracking data that help us provide the user with a richer browsing experience. You can elect to disable these cookies as well.
If the script approach doesn't work for you, keyword highlighting definitions can be imported manually by copying the corresponding .ini file in the Keywords sub-folder found in SecureCRT's Configuration folder location.
Once you have placed a copy of the keyword highlighting .ini file into the Keywords sub-folder, the title of the imported keyword file will become visible and available for selection in the Keyword Highlighting category of the Session Options window in SecureCRT.
Note:
If you desire to have the same keyword highlighting title selected in all of your saved sessions, you can change the keyword highlighting entry in the Default Session in SecureCRT and apply that change to all of your existing sessions when prompted. See the video, Sessions: 2) The Default Session for more information about how to make configuration changes apply to all of your existing and future sessions.
Now, to make a backup the session profile, we will have to use the CLI. Before we start, we need to find the location of the session profiles. By doing so, go to Options > Global Options then the location is going to be under the Configuration folder. See Figure 2
Now, to navigate to this location, first open your command line use either OS X Terminal or SecureCRT. Now, use the command pwd to see where you are at. Most likely you will be at the home directory of your account. See Example 1
SecureCRT can be configured to begin logging to a file starting from the moment a connection is fully established. You can also configure SecureCRT to automatically name the log file with date, time, and specific session information (like hostname or session name), or even place the log file into a folder structure that parallels what you see in SecureCRT's Session Manager.
The video SecureCRT Log File Name Substitution Parameters on the VanDyke Software YouTube channel shows how to set up automated logging and how to use SecureCRT's log file name substitution parameters.
The log file name and the path where the file is saved can be configured in the Log file name entry box. If you want a new log file to be generated each time you connect, SecureCRT's log file substitutions can be used in the Log file name entry box to ensure a unique log file name is generated upon each connection. Here's one example that would create a unique path and log file name for the session whenever a new connection is made:
In this example, here's what an automated logging setup might look like: The log file name, path, and substitution variables have been configured in the Log file name entry box, and the Start log upon connect and Timestamp each line options have been selected.
Note: If you don't see the Timestamp each line option in the Session Options / Log file dialog, it means your version of SecureCRT is an earlier version that does not support this feature.
To ensure that every one of your sessions is configured this way, instead of changing just one session, you can make the changes in SecureCRT's Default session. When you make a change to SecureCRT's Default session, you are offered the opportunity to apply the changes to ALL of your sessions at once.
Important: Prior to making any major changes in the Default session, make sure to back up your full configuration to an XML file via the Tools / Export Settings... menu option so you can revert to the saved configuration if something unexpected goes awry.
Once you've opened the Default Session, simply make the changes outlined above: configure a session- and time-based log file name, then enable Start log upon connect in the Terminal / Log File category of the Session Options - Default window. Once this new logging information has been configured in the Default session, simply press OK, and when SecureCRT asks if you want to apply the changes to all of your sessions, select the option Change ALL sessions (no undo).
Note: In order for settings from the Default session to be applied to all sessions, the option you want to propogate must not already be the desired value in the Default session before you begin editing. If this is the case, SecureCRT won't be able to detect any changes to apply. Only settings which have different values than those that were in place before the Default session was opened for editing are applied to all sessions. If your first attempt at propogating Default session option values to all your sessions doesn't work as expected, try changing the targeted option values to something undesired and apply that change only to the Default session. Then you can edit the Default session and set the targeted options to the desired value and apply the changes to all of your existing sessions.
The same general capabilities apply to SecureCRT on macOS and Linux platforms, but some of the underlying details may be different than face value. For instance, in the examples shown above, the path to the Log file name entry box is displayed in the Session Options window as:
By design, SecureCRT uses the substitution named $VDS_USER_DATA_PATH to represent the "Documents" folder. This approach facilitates the same configuration files being used on Windows, macOS, or Linux platforms. The "Documents" folder is a well-known location for which a substitution name is used in its place. Here is a list of substitution names for all of the well-known locations:
This means that if this same session configuration is loaded on a Windows machine where the configuration folder is set to C:\Users\user\Application Data\Roaming\VanDyke\Config, when read in from the .ini file, the $VDS_CONFIG_PATH is automatically converted to reflect SecureCRT's current configuration path.
Now this works fine but SecureCRT nests the session .ini files in folders (and I have a few hundred of these based on the device locations), so I find myself having to include the path in the keyword argument. For example "keyword \folder\host.ini".
What I'd like to be able to achieve is a way of searching the folders for the host .ini and then passing the resulting path to the command line argument that launches the appropriate session in the app.
4a15465005