RDP connection About RDPThe Remote Desktop Protocol (RDP) is a protocol for remote access. It can be used to display and control screen content of a remote workstation. RDP is an integral part of all Windows operating systems.

A special session is started on the server for the RDP access, and only the connected client can access this session.

The size of the displayed screen content is determined on the Thin Client's display size. If the screen content is only displayed on one half of the Thin Client it will be scaled accordingly.

A Windows server is required for several RDP connections to access one server. A client access licence is required for each client to access and connect to the Windows server. Licencing depends on the operating system of the server.

Either the computer name or the server IP address can be used for addressing.

If you want the option of redundant connections we recommend you use the DNS naming system.

VNC connection About VNCVirtual Network Computing (VNC) is a platform-independent server system. VNC operates according to the Client-Server model.

The VNC service displays the screen content of a remote PC (server) on a local computer (client) The client sends the keyboard and mouse actions to the remote server. This way, the client can use the resources, applications and programs of the server.

The server's display size determines the size of the displayed screen content. If the server display screen ratio is different to that of the Thin Client, the screen content will be compressed or displayed with black edges.

VNC allows multiple access to the server. The display of the clients is then synchronised.

The VNC service must be installed on the remotely controlled PC (host). The Thin Client accesses the VNC server via a VNC viewer application. The installation and configuration of the VNC system on the server and the client requires administrator access authority. The VNC communication between server and client does not require this level of access authority.

VNC services are available from various providers. Depending on the VNC server, these systems have different functionalities.

For detailed information and a description of the VNC service, please refer to the documentation of the provider.

In order to be able to establish a VNC connection, the VNC server system must be activated on the host. The VNC service acquires the IP address needed for this connection from the settings of the PC's network connection. Depending on the configuration, the IP address is specified manually or allocated by a DHCP server. In the firmware's address book, this IP address is defined as the server IP of the VNC connection.

KVM-over-IP connection About KVM over IP

KVM over IP provides remote access to keyboard-video-mouse systems (KVM). With these systems, a workstation is connected with keyboard, mouse and screen via an external KVM-over-IP box. The KVM-over-IP box is integrated into the network via an Ethernet interface. Data transmission is via the VNC protocol. A VNC service has been installed to establish the connection. The workstation that is part of the KVM system does not require a network connection or a software installation.

The Thin Client has been designed as a closed system based on Windows® 10 IoT Enterprise 2016 LTSB.

As a standard, the Thin Client comes equipped with the Windows 10 IoT Enterprise operating system and activated Windows 10 LTSB (Long Term Servicing Branch).

If Windows 10 LTSB is not activated (after a reset, for example), it can be activated under menu item Maintain (see Activating windows).

We recommend you activate the firewall and virus protection and permit all necessary security updates.

Any further measures to protect the process network are the responsibility of the operator of the facility.

The access control system of the Remote firmware is based on three user roles. These are tiered in a hierarchy.

The Admin and Engineer user roles can be password-protected in the "Access Control" menu.

When the firmware is started up for the first time, the user roles are de-activated and the firmware starts with the Admin user role. Password protection is not active.

The Admin and Engineer user roles should only be given to staff familiar with Thin Client administration.

The register bar contains the following functions:

The basic settings contain buttons for operating the touchscreen. If no touchscreen is connected, the functions are greyed out.

This display indicates the status of the Ethernet connection.

Applications can only be used with a Pro licence of the firmware.

Once applications (apps) have been set up, they are shown as buttons. More than one app can be started. The status of the app is shown.

The remote connections can be selected from the address book.

Operating elements vary depending on the menu.

Login is only required when the user roles have been activated. Operators have access to the system without login.

In the factory state, the user roles are deactivated and the Admin is the standard user. When the user roles have been activated, a password is required for the Engineer and Admin user roles. A user name is not required.

The automatic logon at the server can be configured in the settings of the remote connection. For this you need the user ID and the password for the server.

Only users with authority for remote access to the server can log on to the server. Check the user authority at the server or the KVM box.

The following display options are available:

You can configure how the remote connection behaves during a system startup or when it is lost, as follows:

The system allows parallel use of several active remote connections (multi-session connections). Whilst one remote connection is displayed on the screen, the other connection stays active in the background. These connections are marked as follows in the address book: connection active in the foreground connection active in the background

Activate the parallel use of several remote connections in the Settings menu under the Connections menu item. See also:

You will need the IP address or the name of the server for the configuration. These are stored in the system properties of the server.

For RDP connections, remote access must be explicitly permitted in the server's system properties. The remote access must be configured for the user.

Open the Address Book register. Click on  + Add . A new address book entry is created. Click on  Edit . In Connection Settings, via the drop-down field Type, select "RDP". Under Name, enter the name of the connection. Under Server Address, enter the IP address or the name of the server. To ensure automatic access to the connected server you have to enter the correct logon data. Please note that a domain name may have to be used together with the user name.   Under User Name and Password, enter the logon data of the server. If you want to be able to call up the remote connection via the keyboard, use Hotkey to specify a hotkey. Click on Show on to select the display option. Specify the minimum user role required for the manual set-up of the connection. If a user does not have the required authority to set up the connection, this connection is greyed out in the address book.   Click on  Apply  to set up the connection. The connection is shown in the address book.

A VNC client is pre-installed on the Thin Client. The VNC service must also be installed on the server. Administrator authority is required on the Thin Client and the server for the installation.

Set-up menu of the pre-installed VNC service

To set up the connection you require the IP address of the VNC server and, depending on the configuration, the VNC password.

To establish a connection you require a VNC service which runs on the KVM box.

To set up the connection you require the IP address of the VNC server and, depending on the configuration, the VNC password.

Open the Address Book menu. Click on  +Add . A new address book entry is created. Open the address book entry. In the Connection Settings, select "KVM over IP" from the Type drop-down field. Enter the name of the connection in the Name field. Enter the IP address of the KVM box in the Server Address field. Under User Name and Password, enter the logon data of the KVM box. If you want to be able to call up the remote connection via the keyboard, use Hotkey to specify a hotkey. Use Show on to select the display option. Specify the minimum user role required for the manual set-up of the connection. If a user does not have the required authority to set up the connection, this connection is greyed out in the address book.   Click on  Apply  to set up the connection. The connection is shown in the address book.

The touchscreen is calibrated via defined calibration points (top left, centre left, bottom left, top centre, centre centre, bottom centre, top right, centre right, bottom right). These are shown one after the other during calibration.

If the calibration has not been performed correctly it cannot be confirmed. The calibration process will re-start automatically after 10 seconds.

If two touchscreens are connected, the button is split. You can calibrate each touchscreen separately.

Tapping on the touchscreen simulates a click with the left mouse key. If you want to open the context menu of applications you have to simulate a right mouse key click.

Right mouse key deactivated	Right mouse key activated

If no context menu pops up, no context menu is available for the position you clicked on.

If you remove your finger or pen before the circle has closed the right mouse key click is aborted.

You will need the IP address or the name of the server for the configuration. These are stored in the system properties of the server.

For RDP connections, remote access must be explicitly permitted in the server's system properties. The remote access must be configured for the user.

Open the Address Book register. Click on  + Add . A new address book entry is created. Click on  Edit . In Connection Settings, via the drop-down field Type, select "RDP". Under Name, enter the name of the connection. Under Server Address, enter the IP address or the name of the server. To ensure automatic access to the connected server you have to enter the correct logon data. Please note that a domain name may have to be used together with the user name.   Under User Name and Password, enter the logon data of the server. If you want to be able to call up the remote connection via the keyboard, use Hotkey to specify a hotkey. Click on Show on to select the display option. Specify the minimum user role required for the manual set-up of the connection. If a user does not have the required authority to set up the connection, this connection is greyed out in the address book.   Click on  Apply  to set up the connection. The connection is shown in the address book.

The VNC software must be installed on the Thin Client and the server, requiring Administrator authority on both.

To set up the connection you require the IP address of the VNC server and, depending on the configuration, the VNC password.

The process varies according to which VNC service is used. For more information, please refer to the documentation provided by the VNC service manufacturer.

This process requires Administrator authority.

The process varies according to which VNC service is used. For more information, please refer to the documentation provided by the VNC service manufacturer.

This process requires Administrator authority.

Enables you to perform system maintenance in the Administrator account and install applications on the Thin Client, for example.

Settings at system level may cause the device to malfunction. Only change to the system level if you are familiar with advanced settings. If not, ask your network administrator for help.

Certain changes to the firmware require a Thin Client restart.

You can reset the firmware settings to their factory state.

You can use the Export function to save the address book entries, the application list and network settings separately. Then use the Import function to restore the intact settings (see Import and Export).

Only carry out a reset if you are familiar with the configuration of the Thin Client.   Open the Maintenance menu. In the Main section, click on  Reset all Settings . A safety check will pop up. Confirm with  Yes . The system is reset to its factory state.

Use this dialogue to pair or add peripheral devices such as USB or Bluetooth devices.

The Windows 10 LTSB operating system is pre-installed on delivery. If Windows 10 LTSB is deactivated after a system reset for example, you can re-activate it via the telephone or internet access. A system dialogue will guide you through the re-activation via telephone.

Activating the operating system via telephone

Activation is carried out via Microsoft's telephone service.   Open the Maintenance menu. In the Windows Activation section, click on  Activate by phone . The Windows activation system dialogue will start. In the Select your country or region window, select your country or region. Click on  Next  to navigate to the Call and provide your installation ID window. Select the telephone number given and follow the instructions given in the telephone dialogue. Click on  Next  to navigate to the Enter your confirmation ID window. Enter your confirmation ID. Click on  Activate Windows  to activate the operating system.

	Activating the operating system via an internet access
	The Thin Client needs to have internet access.   Open the Maintenance menu. In the Windows Activation section, click on  Activate over Internet . This process may take up to one minute. Wait until the system issues a message. If the activation has been successful, the Windows Activation section will be hidden. The Information menu will list the activated operating system under System.

The Thin Client can be addressed via the IP address or the computer name in the network. The computer name can be used for remote access to the Thin Client via VNC, for example. The computer name should therefore be unique in the network.

Enter the computer name under Computer Name. It might make sense in large networks to enter a description too, in order to be able to identify the device faster.   Enter an informative description of the device under Description.

Use the proxy server to control and limit access to internet resources, for example. The client request is forwarded to the target server with the IP address of the proxy server.

You can save login data for access to the Windows Administrator account under Windows Admin Account Login Credentials. The login data is required to start applications via the firmware that require Administrator or other elevated rights.

We recommend you activate the Windows firewall and the virus protection, and permit all necessary security updates. In its factory state, these functions are activated.

The Unified Write Filter (UWF) is a write protection for the SSD and can be activated in the Protection menu. Use the UWF to protect the SSD from accidental writing. It transfers all write access to an overlay buffer in the RAM.

It thus prevents premature wear-out of the SSD and a corruption of system files after a sudden network failure. Also, viruses and Trojans are not permanently stored in the system, since all changes stored in the overlay buffer are deleted when the device is switched off.

Depending on your security concept, you can block the use of USB devices or permit the use of connected USB devices in the Protection menu. The use of other devices can be permitted via the Teach-In function

	Blocking the use of new USB devices
	Use this function to block all USB devices that are not or have never been connected to the Thin Client.   Open the Protection menu. Under USB Lockdown, activate the Block access to USB devices function. Activate Block new USB devices only. Confirm your selection with  Apply . The specifications of the connected USB devices will be saved. New USB devices are blocked.

The HORM function (Hibernate Once Resume Many) allows for a fast start of the Thin Client from a fixed system image (snapshot). After the start, the system is in exactly the same state as when the last HORM snapshot was taken. This means that running applications of the Pro version do not have to be restarted, but are available right away.

The Eagle and Manta series devices can use another Thin Client as an additional display. A virtual display is simulated at the main device, whose content can be displayed on the additional screen via a VNC connection.

You can adjust the resolution and orientation for each display. You can also specify the order (topology) and the main screen.

The factory setting for the keyboard layout is the US layout (QUERTY). This applies to the virtual and external keyboards (optional) The language layout is independent of the design, coding, position and number of keys on the physical keyboard.

The Thin Client system console is set to the US layout, and this can NOT be changed.

The firmware supports various language layouts for the virtual and external keyboards. The country codes for the language layouts are those listed in ISO 3166-1, subsection ALPHA-2.

You can specify how to open the firmware:

Use Ignore hotkeys if RemoteHMI menu is closed to specify whether the hotkeys for calling up remote connections and applications should be ignored when the dashboard is closed. The defined hotkeys are only effective if the dashboard is open. Use this function to use the same hotkeys for different purposes.

If you have defined a hotkey for opening the dashboard, this hotkey will always be active. It is not affected by this function.

An automatic logout can be specified for the Admin and Engineer user roles. A user is automatically logged off if he or she has been inactive for more than the pre-defined logout time.

Use the Allow Multiple simultaneous connections function to allow parallel use of multiple remote connections (multi-session connections). This enables you to:

Go to On connection loss, auto reconnect to specify an interval after which a reconnect is attempted after a connection has been lost.

This function must be activated separately for each remote connection in the address book entry.

The Connection Health Check function is used by the Thin Client to send cyclical pings (echo requests) to all servers configured in the address book. The result of these requests is shown as the connection status in the address book.

The connection health check only works properly if the servers' firewalls permit answering to an echo request.

You can switch off this function if you do not require an echo request. In this case the status of the connection is not shown in the address book