Launch RDP or HTTP Connections from SecureCRT's Session Manager

[jdev]

UPDATE: 2021/05/05
SecureCRT 9.0 for Windows introduced native support for RDP connections.



This script example facilitates management of RDP, HTTPS, and HTTP connections from within SecureCRT's session manager. Currently designed to work only in SecureCRT for Windows.

1. Download the script file and save it to the location on your local machine where it will always be available.
   
   Idea: Store the script file inside SecureCRT's configuration folder -- just inside the main "Config" level.
   
   
2. Map a button on SecureCRT's button bar to run the script.
   
   
   
3. Run the script.
   • The first time it runs, it will create three template sessions for you.
     
     
     
   • To create RDP, HTTP, or HTTPS sessions, simply double-click the template session for the protocol you desire, and you'll be prompted for the information associated with the machine/address you'd like to connect to. Then a session will be saved and automatically connected. Alternatively you can create new sessions by running the script again (say, by clicking on the button you've created on the button bar). The process will be similar, except you'll first be prompted to specify which protocol (RDP, HTTPS, or HTTP) you want to use for the new session.
     
     
     
   • If you desire to create a multiplicity of RDP/HTTP/HTTPS sessions in bulk, populate the clipboard with data like is demonstrated below, and then run the script by clicking on the button you've created.

     http://www.vandyke.com/support 
     https://forums.vandyke.com/showthread.php?t=10365
     rdp://192.168.1.97
     rdp://192.168.1.143
     rdp://192.168.1.146
     rdp://127.0.0.1:33389

   
   
4. Create RDP/HTTP/HTTPS sessions using the techniques described. New sessions are created in a folder that will appear in SecureCRT's session manager, named #_New_HTTP-RDP_Sessions (so named so that it appears near the top of the session manager).
   
   
   
5. Feel free to move new sessions to the session manager folder location of your choice.
   
   
6. Double-click a saved session to connect.

Enjoy!

--Jake

If you're looking for the legacy version of this example script (which was much more cumbersome to use/maintain), you can find it here.