bthebaudeau
commented
4 years ago The mapping above was for Ubuntu as the host OS with an en-us mapping.
With Windows Server 2019 Standard and an fr-fr mapping, I get:
azertyuiop→qwertyuiopqsdfghjklmM→asdfghjkl,?wxcvbn→zxcvbn²→ùShift+²→%&é"'(-è_çà→&é"'(-è_çà(no issues)1234567890→1234567890(no issues)~#{[|`\^@→~#{[|`\^@(no issues))°=+}^¨$£ù*µ,?;.:/→^"=+}$£mM²*µ;.:/!§]¤%!§<>→ not mapped at all0.123456789/*-+(numpad) →à:&é"'(-è_ç!8)+
Horgster
trondkk
Monsurd
rgl
ensingerphilipp
Using an fr-fr keyboard with MeshCommander v0.8.2, some keys are correctly mapped, some other keys are mapped as en-us, some other keys are mapped otherwise, and some keys are not mapped at all. I get the same behavior whether the AMT host is running the BIOS UI, Windows 10 Pro with an fr-fr keyboard or Ubuntu with an en-us mapping.
I don't know if this can help, but with MDTK, in order to get an acceptable keyboard mapping, I had to select "Japanese keyboard" in the connection options of UltraVNC and to switch my Windows keyboard mapping to en-us for the KVM window.
Here is the exact mapping that I get with MeshCommander v0.8.2:
a-z→a-z(no issues)²→'Shift+²→"&é"'(-è_çà→1234567890(as if en-us)1234567890→!@#$%^&*()(as if en-us))°=+^¨$£ù%*µ,?;.:/→[{=+]};:`~\|,<.>/?!§<>and AltGr combinations → not mapped at allAMT host: Lenovo ThinkServer TS140, BIOS version: FBKTD9AUS, Intel ME v9.1.45 activated in Admin Control Mode (ACM). Client: Windows 10 Pro 1909, 64-bit, fully updated, RLE8.
MeshCommander was installed using the MSI installer.
Tell me if you need more information.