My experience with RDP is that setting jaws to run at login from the
toggle quoted messageShow quoted text
target computer (as if you were sitting down at that machine and
logging in normally) doesn't work very well. Instead I tell the RDP
client to run jaws after connecting and that does work.
And as Michael says, for RDP to be useful at all you have to have
purchased the remote access option for your jaws license. (At the time
I did that it was only available for jaws pro, but am not sure if that
changed with FS' change in license structure).
On 3/15/17, Michael Mote <firstname.lastname@example.org> wrote:
Hi Jonathan! I’m wondering if the remote access for JAWS is working
correctly. It sounds like you may be getting the speech through the PC
you’re connecting to, and not your own PC. The other thing that you
mentioned in your email that raises a red flag is the fact that you have to
have your authorization installed on the computer that you’re connecting to.
If remote access is working properly, that shouldn’t be the case. Have you
paid for the remote access to be enabled on your version of JAWS?
From: email@example.com [mailto:firstname.lastname@example.org] On Behalf Of Jonathan
Sent: Tuesday, March 14, 2017 3:15 PM
Subject: JAWS 18 and RDP Sessions
I am having difficulty using JAWS in RDP sessions. Since the computers to
which I am connecting must be logged on 24/7, I use Disconnect instead of
Logoff to terminate the session. The problem I am having is that quite
often when I connect via an RDP session, speech is not available with JAWS.
I usually have to end the JAWS process through Task Manager and then restart
it again to have speech. However, this doesn’t always work, and I have to
restart the entire computer to resolve it. Other times it connects without
difficulty and speech is immediately available. I have checked to run JAWS
and logon and after all users using Always, but this hasn’t helped. The
only consistent connection I can get is with a computer on which JAWS is
registered with my auth code. I was under the impression that the auth code
wasn’t needed for computer running JAWS remotely, however, and so this
doesn’t explain the inconsistency I’m seeing. The problem is happening on
several different desktops with 2 running WIN7 and 1 running WIN10. Does
anyone have ideas on this?