A full overview of all features in NEO SSH-Win Manager — simply explained.
SSH drives
One click — and the server folder appears like a local disk in Explorer.
One click mounts the remote folder as a Windows drive letter — no command-line knowledge needed.
The app finds a free letter and avoids conflicts with existing drives automatically.
Drives are disconnected cleanly. If that fails, fallback methods are tried automatically.
The connection name appears directly as the drive label in Explorer.
Dropped connections are restored automatically — e.g. after a brief network outage.
The app remembers active drives and mounts them again automatically after a restart.
Authentication & security
Enter your password once — it is used automatically when mounting drives. No SSH key needed. For automatic password login in the terminal, enable PuTTY in Settings.
Standard SSH keys and certificates are supported and used automatically when connecting.
For servers where no password should be stored — a prompt appears on each connection.
All saved SSH passwords are encrypted locally — the key comes from your app login.
The app only runs once — a second launch brings the existing window to the front.
Multiple users on one PC, each with their own connections and credentials.
Interface & design
Open an SSH session with a single click using the native Xterm terminal, PuTTY, or OpenSSH, with support for passwordless login.
CPU, RAM, disk, uptime and load right in the connection card — no extra tools.
The app runs quietly in the tray. Mount or unmount drives without opening the main window.
A polished interface with light and dark themes — per-user preference.
Language per user. The interface switches after restart.
The app can start automatically at Windows login — as a tray app in the background.
Automation
Use connections from scripts or automations — with an access key, no login dialog needed.
Interaktive SSH-Session
NeoSSHWinManager-cli.exe --connect-cli "<access_key>"
Einzelnes Kommando ausführen
NeoSSHWinManager-cli.exe --connect-cli "<access_key>" --exec "uname -a"
Enable CLI access in the connection settings and generate an access key.