If the keyboard at the console and the keyboard at the remote platform do not share the same keyboard layout, some keystrokes might be incorrectly interpreted during a KVM session. There is only a small range of differences between international keyboards in terms of the number of keys, but the expected generated characters can vary widely from keyboard to keyboard.
KVM in Intel AMT Release 6.0 assumes that it is emulating a US English keyboard – that it has the same number of keys and keyboard layout as a US English keyboard.
To demonstrate the problem, consider the following flow:
Note that a keyboard is defined by the key codes sent by the keyboard (basically the location of the key) and by the operating system, which interprets the key, by determining the character that key position represents. If the console keyboard is not a US English keyboard, then the remote platform may display characters different from the keys pressed on the console keyboard. Keys on an extended keyboard that have no equivalent key on a US English keyboard will not be displayed.
The straightforward solution for Intel AMT Release 6.0 is to use a physical or virtual keyboard at the management console with the same layout as the keyboard on the managed platform. The console operating system should be set to a US English keyboard even when other languages or layouts are actually used. This allows the IT operator to use any language or layout on the managed platform.
The RealVNC viewer and Intel AMT Release 7.0 use a different character encoding that supports extended keyboards. The RFB 4.0 protocol has a protocol extension mechanism that sends USB Scancode directly. Any viewer taking advantage of this feature would have to implement the USB Scancode protocol extension.
Copyright © 2006-2022, Intel Corporation. All rights reserved.