Preconfiguration Requirements for Non-US Keyboards

Starting from version 4.25, Eggplant Gateway has introduced enhancements to better support Non-US keyboard layouts for RDP connection. With the latest enhancement, Eggplant Gateway's RDP connection are able to help to perform keyboard layout synchronization between the client machine with the SUT. Example: If client machine are using Japanese Keyboard, after RDP connection established the SUT keyboard will also set as Japanese Keyboard. Due to these improvements, some preconfiguration steps may be required to ensure proper keyboard mapping and functionality during remote sessions.

Supports for RDP SUTs with Non-US keyboards

The System Under Test (SUT) will only reflect the correct keyboard layout if the previous Remote Desktop Protocol (RDP) session has been properly signed off. If the previous session is disconnected (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.

Pre-configuration steps

1. Start the RDP session with your desired keyboard layout. (Or the RDP session has been started before.)
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 disconnect the session, as this will retain the previous keyboard layout in the next session.
4. After signing off, initiate a new Eggplant Gateway's RDP session 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.