Forum / Remote Desktop Manager Mac - Support

Nummeric keyboard gives 'q'

  • Create an Issue
  • Cancel

Hi


I have a Macbook Pro with Devolutions (4.6.2.0) connecting to a Windows 2016 terminal server.
Using an AZERTY Keyboard.
When I type on the keyboard I get for every number on the numeric keyboard a 'q'.
Using the number on the top of the keyboard I get no numbers at all.
The keyboard layout in the 'Local Resources' is set to Dutch(Belgium).
Using Qwerty settings, everthings works.
The Mac is using MacOS High Sierra 10.32.2.


Does anyone has a solution for this problem?

Clock2 yrs

Hello,
Jonathan is currently on vacation but I know that he was working on a fix for that in ARD. I will assign this to our devs and they will get back to you as soon as they get back to the office next week.

Regards

David Hervieux

signaturesignature

Clock2 yrs

Lossing hours on this issue.
I changed the keyboard layout in 'Local Resources' to French(Belgium) and the problem was solved.
But after login of and reconnecting, the issue comes back.
This is very unstable.


In version 4.6.1.0, same issue.
It must be a bug.

Clock2 yrs

Hi Danny,

I would like clarify a couple things to make sure I have all the information I need to successfully reproduce your issue.
You mentioned using an azerty keyboard layout. I assume the actual layout is Dutch(Belgium)?
Is the server 2016 also using a Dutch(Belgium) keyboard layout?
Have you experienced this problem on a machine other than a Server 2016?

Regards,

Jonathan Lafontaine

signaturesignature

Clock2 yrs

Is there some progress on this issue?
Some of the clients use Qwerty.
We have a terminal server 2012r2 and this causes no problem. Although the Windows 2016 server works with a gateway/loadbalancer and the 2012R2 server does not.

Clock2 yrs

I wasn't able to reproduce this particular issue which leads me to believe i'm missing some information.

I asked a couple of questions in my last post.
It could help me pinpoint the problem.

Regards,

Jonathan Lafontaine

signaturesignature

Clock2 yrs

As you only seem to have problem with this server, could you try connecting with the official Microsoft RDP client to see if you have the same issues?
Also, the RDP log could help pin point the problem. You can activate logging for this particular session by specifying a path in the properties' advanced tab.

Regards,

Jonathan Lafontaine

signaturesignature

Clock2 yrs

We just did a test and with Microsoft Desktop no problem with the keyboard.

Clock2 yrs

Would it be possible to have restricted access to your server?
I haven't been able to reproduce this issue locally, unfortunately.

Jonathan Lafontaine

signaturesignature

Clock2 yrs