With the following settings, you can configure and manage access to thin clients via a secure terminal.
Misc> Settings > Remote Access > External terminal client: Command line for the external terminal client, made up of the path to the putty.exe and the appropriate parameters. The UMS currently supports PuTTY. The minimal command line without further configuration of PuTTy is:
"<Path and file name for putty.exe>" -telnet -P <port> <hostname>
<port> and <hostname> are placeholders which are automatically replaced by the port number and the IP address of the thin client during execution. Background: The actual connection to the thin client is provided by the UMS and is available to the external terminal client as a tunnel.
If the External terminal client field is empty, the internal terminal client of the UMS will be used.
Misc > Settings > Remote Access > Show closing dialog if two or more sessions are open
If two or more sessions are open, a closing dialog will be shown if you attempt to close a window of the external terminal client.
No closing dialog will be shown when you close the window of the external terminal client.
Misc > Settings > Remote Access > Show warning for unexpectedly terminated sessions
A warning will be shown if a session with an external terminal client was terminated without any user input.
No warning will be shown.
UMS Administration > Global Configuration > Remote Access > Activate global secure terminal
Access via the secure terminal is enabled for all registered thin clients. The firmware must be IGEL Linux version 5.11.100 or higher.
Access via the secure terminal is not enabled for all registered thin clients. However, it can be enabled for individual thin clients.
UMS Administration > Global Configuration > Remote Access > Log user for secure terminals: Specifies whether the user name of the UMS user who established the connection to the thin client is logged. The log is shown under System > Logging > Remote Access.
The user name is contained in the log.
The user name is not contained in the log.
System > Logging > Remote Access: Shows the log of all secure access to thin clients.
The following data are logged:
Thin Client Name
Thin Client IP
User: The user name of the UMS user who established the connection to the thin client is logged. This is only logged if Log user name for SSH remote access is enabled.
Start time: Point in time at which the connection was established