Dameware - iPad Keyboard Not Working Fully

I found an approximately two-year-old question that was posed which is similar to the issue I've encountered; however, it was never answered and has since been locked. Thus, the reason for this new question. With that said, let's get started.

Recently I've been using my iPad Air M2 with a Magic Keyboard that has to Remote Desktop (RDP) to my office workstation while I'm on-call after hours (aside from using it on-site for other troubleshooting tasks). After I successfully RDP to my office workstation and use Dameware from within that environment to connect onto an employee's workstation for further troubleshooting, I notice that the letters and numbers when pressed are not recognized whatsoever on the end user's workstation. Strangely enough, however, if I use a command sequence such as Ctrl + C, or use Backspace, or even the Tab key, they are recognized.

I'm unsure how come a small portion of the Magic Keyboard is recognized within Dameware when connected onto an end user's workstation, yet when I use RDP to one of our servers the keyboard is recognized without issue. Furthermore, the Magic Keyboard works in general so it doesn't appear to be anything specific with it that is causing it that I can tell, but rather an issue on the Dameware software end.

Thank you for your time and I hope a solution can be found for this issue without it ending with the same result as the previous individual who brought up a similar issue two years ago without any answer.

  • I'm running into the exact same problem with a similar setup (M4 iPad Pro + Magic Keyboard). Hoping for a solution because the iPad is so much more convenient for me to lug around when I'm on-call. I've had to resort to using the on-screen keyboard on the end user's workstation.

  • Tried replying to your (beaubp) comment using Google Chrome and Microsoft Edge but am unsure if this website is bugged in the sense that it doesn't provide a text box to do so when I click 'Reply'.

    Completely agree that it is much more convenient! I used to lug around our on-call laptop and it is cumbersome, so the iPad is much more preferable in comparison. The on-screen keyboard thankfully saves the day, but shouldn't have to. I've now begun to inform employees I'm assisting via Dameware on my iPad that I promise my typing isn't that slow and that I have to use the on-screen keyboard ;)

  • Posting another reply to ensure this issue stays current until someone from SolarWinds deems it worthy of any bit of attention ;)

  • New year but same issue!

    Really hoping that someone from SolarWinds sets aside some time to look into this issue further. Specifically in my instance, this is becoming much more problematic and forces me to use an alternative remote connection software (Ultra VNC in our team's instance - not my choice but is what was here before my time) as I cannot type whatsoever when connected onto an employee's workstation. Thus, negatively impacting the remote experience for all parties involved, especially as Dameware is being used for a non-profit hospital in my case.

    Furthermore, the lack of any response from SolarWinds is soon leading me to having a discussion with our management team to reassess our contract terms. No point in paying for a service and receive not even a single response to an issue with the servicer's software.

  • FormerMember
    0 FormerMember in reply to ianl33t

    Hi, I have the same problem, and it doesn't work both with bluetooth keyboard and touch keyboard on ipad. iPadOs18

  • Hello all! So, I have finally obtained an answer from SolarWinds support as thankfully we have an active contract with them, thus was able to push for an investigation into this issue. Please see below for their response:

    We have concluded our investigation into this issue. We have discovered the Windows App for iOS always sends keystrokes in Unicode to the remote device, which the DRE Viewer does not support. The workaround would be to use a different Remote Desktop client on iOS that supports sending keystrokes in scancodes to the remote workstation, such as Jump Desktop.  


    Not the answer we're all looking for nor do I believe it's a great one in the sense that it comes off as a "tough luck" situation, especially as there is no indication provided if they are even working on ever implementing such support.

    I sent the following response but seeing how things have played out I'll be surprised if I receive a substantive answer:

    Are there any future plans to support Unicode keystrokes via the Windows App for iOS / iPadOS?

    Furthermore, although iOS is used less commonly comparatively to Windows mobile-centric devices, it would be nice to know that SolarWinds supports even their Apple-device users as well.

    Especially as it seems non-user friendly to have to push use of remote services onto other apps (laughably, even an older program such as UltraVNC) to troubleshoot devices remotely from an iOS / iPadOS device instead of Dameware, which we actively pay for to use.




  • Hello all! I received advisement from Dameware support to try using the iPadOS Dameware app directly instead to see if as a workaround it would work; however, I found the same issue was present. I have sent this latest update to them and will update here with their response.