How to Change the Keyboard Layout Terminal

Written by dave wilson
  • Share
  • Tweet
  • Share
  • Pin
  • Email
How to Change the Keyboard Layout Terminal
Configure Terminal Servcies to deliver a consistant user experience. (computer keyboard image by forca from

Microsoft Windows Terminal Services enables remote users to use programs on a remote server as if the user is logged in locally to the server. If Terminal Services is configured to use a particular keyboard layout, then the Terminal Services administrator must modify the server registry so that the local default keyboard layout is used when a terminal session is established. Use the Registry Editor tool to enable Terminal Services to change the remote user terminal keyboard layout.

Skill level:

Things you need

  • Microsoft Windows 2008 computer with Terminal Services installed and configured
  • Credentials of an account with Administrator permissions on the Windows Server 2008 computer

Show MoreHide


  1. 1

    Log in to the username and password of an account that has Administrator permissions on the Windows Server 2008 computer.

  2. 2

    Click the "Start" button in the lower-left corner of the Windows Server 2008 desktop and click "Search," then type "cmd" in the "Search" box. Press the "Enter" key and the command line window will appear.

  3. 3

    Enter "reg add "HKLM\SYSTEM\CurrentControlSet\Control\Keyboard Layout" /v IgnoreRemoteKeyboardLayout /t REG_DWORD /d 0---00000001 /f" at the command prompt and press the "Enter" key.

  4. 4

    Click the red "X" in the upper-right corner of the "Registry Editor" window to close the Registry Editor. The Terminal Services default user profile keyboard layout will now be applied when establishing a Terminal Services remote terminal connection.

Don't Miss

  • All types
  • Articles
  • Slideshows
  • Videos
  • Most relevant
  • Most popular
  • Most recent

No articles available

No slideshows available

No videos available

By using the site, you consent to the use of cookies. For more information, please see our Cookie policy.