Often you do not need the full desktop, just a few commands. The remote command line is a lighter channel: no picture, only text — faster and far cheaper on bandwidth.
What it suits
Reading logs, restarting services, running scripts, checking processes and ports: all quicker through the command line than through a desktop session.
- Read and follow log files
- Restart services and run maintenance scripts
- Inspect processes, ports and resource use
- Run ops commands in bulk
Permissions and risk
A command line equals local administrator power, so authorise it carefully. Enable it only on trusted devices and limit what it may do.
- Enable only on devices you own or manage
- Remote command line can be switched off
- Keep an audit trail of executed commands
- Never pass secrets as plain command arguments
Usage tips
It is a text-only channel, so garbled output usually means an encoding mismatch; for long tasks redirect output to a file so nothing is lost if the session drops.
- Check console code page and encoding for CJK text
- Redirect long-running output to a log file
- Be careful with destructive commands
- Confirm working directory and environment first
FAQ
Does it work on Linux and macOS?
Yes, the terminal opens on those systems with the same commands; permissions follow the account running the client.
Why do I get permission denied?
The client runs with insufficient rights. Run it as administrator on Windows, or use sudo where required on Linux and macOS.