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.

Parents
  • 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.

Reply
  • 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.

Children