How to make the physical keyboard on a Chromebook Plus send accented characters well in a Windows remote desktop session

Jaime Domínguez 0 Reputation points
2024-05-13T05:52:17.9233333+00:00

I use a brand new Chromebook plus updated to the latest version. I occasionally use it to remotely log into Windows computers for support purposes. I use Microsoft's remote desktop client for Android, which can be downloaded from the Play Store.

My default keyboard is international Spanish. Two things happen to me when I start remote session with any Windows computer: it changes the default keyboard to English and then, once I change the keyboard in the remote session to Spanish, when I type a word with an accented letter, it sends like two commands, first the accent and then the well accented letter. For example, if I type the word "café" in the remote session it appears "caf'é" (with the accent the same, not as I put it now).

What could this be due to?

Windows 10
Windows 10
A Microsoft operating system that runs on personal computers and tablets.
10,818 questions
Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,297 questions
Remote Desktop
Remote Desktop
A Microsoft app that connects remotely to computers and to virtual apps and desktops.
4,298 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Claudia Dos Santos Haz (CONCENTRIX CORPORATION) 775 Reputation points Microsoft Vendor
    2024-05-14T10:28:55.5233333+00:00

    Hi @Jaime Domínguez,

    Thank you for sharing your experience! It seems like you’re encountering keyboard layout issues during remote sessions. Let’s address this step by step:

    Keyboard Layout Change to English:

    • When you connect via Remote Desktop Connection (RDC) to a Windows computer, the session defaults to an English keyboard layout, even if your local keyboard is set to Spanish.
      • To resolve this, you can set the IgnoreRemoteKeyboardLayout registry value to 1 on the Terminal Server. This will make the session use the default keyboard layout stored in the user profile instead of the layout provided by the RDC client.
        • Here are the steps:
          1. On the terminal server, click **Start**, then **Run**, type **`regedit`**, and click **OK**.
          
                1. Navigate to **`HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Keyboard Layout`**.
          
                      1. On the **Edit** menu, click **Add Value**, and add the following registry information:
          
                               - Value name: **`IgnoreRemoteKeyboardLayout`**
          
                                        - Data type: **`REG_DWORD`**
          
                                                 - Value data: **`1`**
          
                                                       1. Quit Registry Editor.
          
                                                          - After doing this, configure the default keyboard layout and input language you want, then log off. [All later user logons will use the default keyboard layout from the profile](https://answers.microsoft.com/en-us/msoffice/forum/all/remote-desktop-connection-keyboard-language/e1796a5b-4d34-4977-80eb-42b5192f19d5)[1](https://answers.microsoft.com/en-us/msoffice/forum/all/remote-desktop-connection-keyboard-language/e1796a5b-4d34-4977-80eb-42b5192f19d5).
          
                                                          **Accented Letters Issue:**
          
                                                             - The behavior you described (sending two commands for accented letters) might be related to the keyboard layout mismatch.
          
                                                                - Ensure that both your local keyboard and the remote session are set to the same Spanish layout.
          
                                                                   - Additionally, check if any third-party keyboard utilities or language settings are interfering with the input.
          

    Remember to apply these changes on both your local machine and the remote server

    Best regards,