Terminals: The Remote Access App That Still Does the Job
It’s not flashy. It hasn’t been updated in years. But when you need to RDP into a bunch of servers, SSH into a switch, or VNC into an old box across the network — Terminals gets it done. Quietly. Consistently.
So, What Is It?
Terminals is a multi-protocol remote access client for Windows. It wraps RDP, SSH, Telnet, VNC, ICA, HTTP(S) and even VMRC into one UI — with tabbed sessions, saved credentials, and a connection manager that actually makes sense.
It was open-source, written in .NET, and built for IT folks who deal with dozens (or hundreds) of machines. You launch it, pick a saved connection, and you’re in. Tabs keep things clean. Credentials are stored (encrypted). And it runs on plain Windows — no extra dependencies.
Where It Still Makes Sense
– Admins who bounce between Windows and Linux systems daily
– Support teams managing RDP access to client servers
– Labs and test rigs with mixed protocols and legacy gear
– Anyone who wants a no-frills, tabbed, all-in-one remote tool
It’s also nice in offline or restricted environments — no cloud sync, no telemetry, no internet required.
What It Actually Does Well
| Feature | Why It Still Works for Real Admins |
| Multi-Protocol Support | RDP, SSH, Telnet, VNC, HTTP, and more — all under one roof |
| Tabbed Sessions | Easily switch between sessions without clutter |
| Credential Manager | Store logins securely — useful for trusted environments |
| Favorites and Groups | Organize machines into folders, assign colors or tags |
| Reconnect and Ping Tools | Check if hosts are alive before launching a session |
| No Installation Required | Portable version available — just unzip and run |
| Keyboard Shortcuts | Fast toggles for full screen, send Ctrl+Alt+Del, etc. |
What You’ll Need
– Windows 7, 10, 11 — works well across versions
– .NET Framework 4.x (usually already installed)
– A few remote systems to test it on — that’s it
Runs fine from USB, network shares, or as a portable tool on your admin machine.
Setup (If You Even Want to Call It That)
1. Download from the GitHub mirror or archive sites:
https://github.com/Terminals-Origin/Terminals
2. Unzip and launch Terminals.exe.
That’s it — no install wizard.
3. Add new connections.
Choose protocol, hostname, optional credentials, and hit save.
4. Start working.
Open multiple sessions in tabs, group them, tag them, whatever works.
What Admins Say
“Yeah, it’s old. But it still works better than most of the ‘modern’ replacements.”
“I use it daily for RDP and SSH. The tabbed layout is exactly what I need.”
“We’ve got it on a shared jump box. Everyone uses it. Nobody complains.”
Final Thought
Terminals isn’t maintained anymore, but it’s still alive — in toolkits, USB drives, and sysadmin desktops everywhere. It’s fast, flexible, and does what you need without making a big deal about it.
If you’re tired of juggling five different apps just to connect to your infrastructure — give it a look.
