Skip to main content
Version: 26.2

Configuration Requirements for Non-US Keyboards

Eggplant Test's Remote Desktop Protocol (RDP) connections are able to help perform keyboard layout synchronization between the Eggplant Test client machine (the machine running EPF, DAI, or Eggplant Gateway) and the system under test (SUT). For example, if a client machine is using a Japanese Keyboard, after the RDP connection is established, the SUT keyboard will also be set as a Japanese Keyboard.

Due to this behavior, some pre-configuration steps may be required to ensure proper keyboard mapping and functionality during remote sessions.

Support for RDP SUTs with Non-US keyboards​

The SUT will only reflect the correct keyboard layout if the previous RDP session has been disconnected and properly signed off.

Important

If the previous session is disconnected but not signed off, the keyboard layout may not update correctly in the new session.

Root Cause​

The issue arises because the keyboard layout synchronization depends on the state of the previous RDP session. If the session is disconnected without signing off, the SUT retains the previous keyboard layout settings.

Configuration Steps​

  1. Start the RDP session with your desired keyboard layout. (Or, using the RDP session that was previously started.)
  2. If you later need to switch to a different keyboard layout, you must first sign off from the current RDP session.
  3. Avoid only disconnecting the session, as this will retain the previous keyboard layout in the next session.
  4. After signing off, initiate a new Eggplant Test client RDP session/connection with the new keyboard layout.
  5. Verify that the new layout is correctly applied in the session.

Affected Scenarios​

This issue is commonly observed in environments using RDP or similar remote access technologies, where multiple sessions are initiated without proper sign-off. It affects users who rely on specific keyboard layouts for their work, leading to potential disruptions and inefficiencies.

Using RDP Connections with Non-US Keyboards on Linux​

note

This suggestion applies to Eggplant Functional (EPF) versions prior to 25.1.4, when creating Linux RDP connections to a Windows SUT.

If you are using an RDP (Remote Desktop Protocol) connection with a version of EPF prior to 25.1.4 on Linux, to prevent any issues with non-US keyboards, you can update the connection component Eggplant Gateway (which is built into EPF) to version 25.2 or higher. Eggplant Gateway versions 25.2 and above support all non-US keyboard layouts and all characters are typed as expected. This allows German customers, for example, to run EPF on Linux and run tests against a Windows SUT with the DE (German) Keyboard layout on the Linux machine as well as on the SUT.

When EPF establishes an RDP connection to the SUT, the keyboard layout of the EPF machine is applied to the Windows SUT machine.

Work with your Technical Success Manager or Eggplant Customer Support to sideload a version of Eggplant Gateway that supports all non-US keyboard layouts.

Last updated on