RDS, Remote App, and Window-Eyes
Hello all, A few questions. I know that some of this at least is addressed in the AISquared knowledge base, but it seems that either I or they are missing something. I'm attempting to run Window-Eyes 9.2 remotely on a server, for administration for one, and I've enabled virtual channel, and then when I go into the Window-Eyes settings to set up the Virtual Terminal services voice, it never actually activates and my settings always tend to revert back to the default. I hit activate on Virtual Terminal Services for Remote desktop, and at that moment, Window-Eyes stops speaking ... so there's sort of a caveat there isn't there? Anyway ... onto my second question. We're trying to set up remote app (my friend says he's got it working for his Active Directory site), and I'm wondering whether anyone has gotten Remote App working with Window-Eyes? (the KB article does not discuss it specifically when referring to Terminal Services, only to ZenWorks Presentation server ...) But I'd assume the procedures for configuration are the same whether referring to remote app or to VDI? Thanks for input and suggestions, guys!
I'm not sure why it's not working for you, but I use this successfully all day long. Make sure that on both the server and your local machine, you have gone to the Window-eyes advanced options in the start menu and enable Microsoft virtual channel. I also implemented a group policy which applies not only to the server but every domain computer forcing audio redirection. These 2 things should enable this to work. I don't remember the exact group policy procedure for the audio redirection, but could go back and figure out the way to configure it if you need it. -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Katherine Moss Sent: Friday, December 11, 2015 8:57 AM To: 'blind-sysadmins@lists.hodgsonfamily.org' Subject: [Blind-sysadmins] RDS, Remote App, and Window-Eyes Hello all, A few questions. I know that some of this at least is addressed in the AISquared knowledge base, but it seems that either I or they are missing something. I'm attempting to run Window-Eyes 9.2 remotely on a server, for administration for one, and I've enabled virtual channel, and then when I go into the Window-Eyes settings to set up the Virtual Terminal services voice, it never actually activates and my settings always tend to revert back to the default. I hit activate on Virtual Terminal Services for Remote desktop, and at that moment, Window-Eyes stops speaking ... so there's sort of a caveat there isn't there? Anyway ... onto my second question. We're trying to set up remote app (my friend says he's got it working for his Active Directory site), and I'm wondering whether anyone has gotten Remote App working with Window-Eyes? (the KB article does not discuss it specifically when referring to Terminal Services, only to ZenWorks Presentation server ...) But I'd assume the pr ocedures for configuration are the same whether referring to remote app or to VDI? Thanks for input and suggestions, guys! _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins
I'm not sure why it's not working for you, but I use this successfully all day long. Make sure that on both the server and your local machine, you have gone to the Window-eyes advanced options in the start menu and enable Microsoft virtual channel. I also implemented a group policy which applies not only to the server but every domain computer forcing audio redirection. These 2 things should enable this to work. I don't remember the exact group policy procedure for the audio redirection, but could go back and figure out the way to configure it if you need it. -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Katherine Moss Sent: Friday, December 11, 2015 8:57 AM To: 'blind-sysadmins@lists.hodgsonfamily.org' Subject: [Blind-sysadmins] RDS, Remote App, and Window-Eyes Hello all, A few questions. I know that some of this at least is addressed in the AISquared knowledge base, but it seems that either I or they are missing something. I'm attempting to run Window-Eyes 9.2 remotely on a server, for administration for one, and I've enabled virtual channel, and then when I go into the Window-Eyes settings to set up the Virtual Terminal services voice, it never actually activates and my settings always tend to revert back to the default. I hit activate on Virtual Terminal Services for Remote desktop, and at that moment, Window-Eyes stops speaking ... so there's sort of a caveat there isn't there? Anyway ... onto my second question. We're trying to set up remote app (my friend says he's got it working for his Active Directory site), and I'm wondering whether anyone has gotten Remote App working with Window-Eyes? (the KB article does not discuss it specifically when referring to Terminal Services, only to ZenWorks Presentation server ...) But I'd assume the pr ocedures for configuration are the same whether referring to remote app or to VDI? Thanks for input and suggestions, guys! _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins
What about remote app? In other words, when aplications are published from Terminal Services? Does that work via the same configuration? The knockedge base article says nothing about that. -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Troy Hergert Sent: Friday, December 11, 2015 10:27 AM To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Subject: Re: [Blind-sysadmins] RDS, Remote App, and Window-Eyes I'm not sure why it's not working for you, but I use this successfully all day long. Make sure that on both the server and your local machine, you have gone to the Window-eyes advanced options in the start menu and enable Microsoft virtual channel. I also implemented a group policy which applies not only to the server but every domain computer forcing audio redirection. These 2 things should enable this to work. I don't remember the exact group policy procedure for the audio redirection, but could go back and figure out the way to configure it if you need it. -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Katherine Moss Sent: Friday, December 11, 2015 8:57 AM To: 'blind-sysadmins@lists.hodgsonfamily.org' Subject: [Blind-sysadmins] RDS, Remote App, and Window-Eyes Hello all, A few questions. I know that some of this at least is addressed in the AISquared knowledge base, but it seems that either I or they are missing something. I'm attempting to run Window-Eyes 9.2 remotely on a server, for administration for one, and I've enabled virtual channel, and then when I go into the Window-Eyes settings to set up the Virtual Terminal services voice, it never actually activates and my settings always tend to revert back to the default. I hit activate on Virtual Terminal Services for Remote desktop, and at that moment, Window-Eyes stops speaking ... so there's sort of a caveat there isn't there? Anyway ... onto my second question. We're trying to set up remote app (my friend says he's got it working for his Active Directory site), and I'm wondering whether anyone has gotten Remote App working with Window-Eyes? (the KB article does not discuss it specifically when referring to Terminal Services, only to ZenWorks Presentation server ...) But I'd assume the pr ocedures for configuration are the same whether referring to remote app or to VDI? Thanks for input and suggestions, guys! _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins
What about remote app? In other words, when aplications are published from Terminal Services? Does that work via the same configuration? The knockedge base article says nothing about that. -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Troy Hergert Sent: Friday, December 11, 2015 10:27 AM To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Subject: Re: [Blind-sysadmins] RDS, Remote App, and Window-Eyes I'm not sure why it's not working for you, but I use this successfully all day long. Make sure that on both the server and your local machine, you have gone to the Window-eyes advanced options in the start menu and enable Microsoft virtual channel. I also implemented a group policy which applies not only to the server but every domain computer forcing audio redirection. These 2 things should enable this to work. I don't remember the exact group policy procedure for the audio redirection, but could go back and figure out the way to configure it if you need it. -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Katherine Moss Sent: Friday, December 11, 2015 8:57 AM To: 'blind-sysadmins@lists.hodgsonfamily.org' Subject: [Blind-sysadmins] RDS, Remote App, and Window-Eyes Hello all, A few questions. I know that some of this at least is addressed in the AISquared knowledge base, but it seems that either I or they are missing something. I'm attempting to run Window-Eyes 9.2 remotely on a server, for administration for one, and I've enabled virtual channel, and then when I go into the Window-Eyes settings to set up the Virtual Terminal services voice, it never actually activates and my settings always tend to revert back to the default. I hit activate on Virtual Terminal Services for Remote desktop, and at that moment, Window-Eyes stops speaking ... so there's sort of a caveat there isn't there? Anyway ... onto my second question. We're trying to set up remote app (my friend says he's got it working for his Active Directory site), and I'm wondering whether anyone has gotten Remote App working with Window-Eyes? (the KB article does not discuss it specifically when referring to Terminal Services, only to ZenWorks Presentation server ...) But I'd assume the pr ocedures for configuration are the same whether referring to remote app or to VDI? Thanks for input and suggestions, guys! _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins
Sorry, I'm only familiar with the Remote Desktop client. -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Katherine Moss Sent: Friday, December 11, 2015 12:23 PM To: Blind sysadmins list Subject: Re: [Blind-sysadmins] RDS, Remote App, and Window-Eyes What about remote app? In other words, when aplications are published from Terminal Services? Does that work via the same configuration? The knockedge base article says nothing about that. -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Troy Hergert Sent: Friday, December 11, 2015 10:27 AM To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Subject: Re: [Blind-sysadmins] RDS, Remote App, and Window-Eyes I'm not sure why it's not working for you, but I use this successfully all day long. Make sure that on both the server and your local machine, you have gone to the Window-eyes advanced options in the start menu and enable Microsoft virtual channel. I also implemented a group policy which applies not only to the server but every domain computer forcing audio redirection. These 2 things should enable this to work. I don't remember the exact group policy procedure for the audio redirection, but could go back and figure out the way to configure it if you need it. -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Katherine Moss Sent: Friday, December 11, 2015 8:57 AM To: 'blind-sysadmins@lists.hodgsonfamily.org' Subject: [Blind-sysadmins] RDS, Remote App, and Window-Eyes Hello all, A few questions. I know that some of this at least is addressed in the AISquared knowledge base, but it seems that either I or they are missing something. I'm attempting to run Window-Eyes 9.2 remotely on a server, for administration for one, and I've enabled virtual channel, and then when I go into the Window-Eyes settings to set up the Virtual Terminal services voice, it never actually activates and my settings always tend to revert back to the default. I hit activate on Virtual Terminal Services for Remote desktop, and at that moment, Window-Eyes stops speaking ... so there's sort of a caveat there isn't there? Anyway ... onto my second question. We're trying to set up remote app (my friend says he's got it working for his Active Directory site), and I'm wondering whether anyone has gotten Remote App working with Window-Eyes? (the KB article does not discuss it specifically when referring to Terminal Services, only to ZenWorks Presentation server ...) But I'd assume the pr ocedures for configuration are the same whether referring to remote app or to VDI? Thanks for input and suggestions, guys! _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins
I'll have to then mess with it. I'll tell you then what I find. -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Troy Hergert Sent: Friday, December 11, 2015 1:58 PM To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Subject: Re: [Blind-sysadmins] RDS, Remote App, and Window-Eyes Sorry, I'm only familiar with the Remote Desktop client. -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Katherine Moss Sent: Friday, December 11, 2015 12:23 PM To: Blind sysadmins list Subject: Re: [Blind-sysadmins] RDS, Remote App, and Window-Eyes What about remote app? In other words, when aplications are published from Terminal Services? Does that work via the same configuration? The knockedge base article says nothing about that. -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Troy Hergert Sent: Friday, December 11, 2015 10:27 AM To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Subject: Re: [Blind-sysadmins] RDS, Remote App, and Window-Eyes I'm not sure why it's not working for you, but I use this successfully all day long. Make sure that on both the server and your local machine, you have gone to the Window-eyes advanced options in the start menu and enable Microsoft virtual channel. I also implemented a group policy which applies not only to the server but every domain computer forcing audio redirection. These 2 things should enable this to work. I don't remember the exact group policy procedure for the audio redirection, but could go back and figure out the way to configure it if you need it. -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Katherine Moss Sent: Friday, December 11, 2015 8:57 AM To: 'blind-sysadmins@lists.hodgsonfamily.org' Subject: [Blind-sysadmins] RDS, Remote App, and Window-Eyes Hello all, A few questions. I know that some of this at least is addressed in the AISquared knowledge base, but it seems that either I or they are missing something. I'm attempting to run Window-Eyes 9.2 remotely on a server, for administration for one, and I've enabled virtual channel, and then when I go into the Window-Eyes settings to set up the Virtual Terminal services voice, it never actually activates and my settings always tend to revert back to the default. I hit activate on Virtual Terminal Services for Remote desktop, and at that moment, Window-Eyes stops speaking ... so there's sort of a caveat there isn't there? Anyway ... onto my second question. We're trying to set up remote app (my friend says he's got it working for his Active Directory site), and I'm wondering whether anyone has gotten Remote App working with Window-Eyes? (the KB article does not discuss it specifically when referring to Terminal Services, only to ZenWorks Presentation server ...) But I'd assume the pr ocedures for configuration are the same whether referring to remote app or to VDI? Thanks for input and suggestions, guys! _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins
I'll have to then mess with it. I'll tell you then what I find. -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Troy Hergert Sent: Friday, December 11, 2015 1:58 PM To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Subject: Re: [Blind-sysadmins] RDS, Remote App, and Window-Eyes Sorry, I'm only familiar with the Remote Desktop client. -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Katherine Moss Sent: Friday, December 11, 2015 12:23 PM To: Blind sysadmins list Subject: Re: [Blind-sysadmins] RDS, Remote App, and Window-Eyes What about remote app? In other words, when aplications are published from Terminal Services? Does that work via the same configuration? The knockedge base article says nothing about that. -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Troy Hergert Sent: Friday, December 11, 2015 10:27 AM To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Subject: Re: [Blind-sysadmins] RDS, Remote App, and Window-Eyes I'm not sure why it's not working for you, but I use this successfully all day long. Make sure that on both the server and your local machine, you have gone to the Window-eyes advanced options in the start menu and enable Microsoft virtual channel. I also implemented a group policy which applies not only to the server but every domain computer forcing audio redirection. These 2 things should enable this to work. I don't remember the exact group policy procedure for the audio redirection, but could go back and figure out the way to configure it if you need it. -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Katherine Moss Sent: Friday, December 11, 2015 8:57 AM To: 'blind-sysadmins@lists.hodgsonfamily.org' Subject: [Blind-sysadmins] RDS, Remote App, and Window-Eyes Hello all, A few questions. I know that some of this at least is addressed in the AISquared knowledge base, but it seems that either I or they are missing something. I'm attempting to run Window-Eyes 9.2 remotely on a server, for administration for one, and I've enabled virtual channel, and then when I go into the Window-Eyes settings to set up the Virtual Terminal services voice, it never actually activates and my settings always tend to revert back to the default. I hit activate on Virtual Terminal Services for Remote desktop, and at that moment, Window-Eyes stops speaking ... so there's sort of a caveat there isn't there? Anyway ... onto my second question. We're trying to set up remote app (my friend says he's got it working for his Active Directory site), and I'm wondering whether anyone has gotten Remote App working with Window-Eyes? (the KB article does not discuss it specifically when referring to Terminal Services, only to ZenWorks Presentation server ...) But I'd assume the pr ocedures for configuration are the same whether referring to remote app or to VDI? Thanks for input and suggestions, guys! _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins
Katherine: I played with remote app once a ton of years ago with an older version of Window-Eyes. I published both Window-Eyes and Calculator as a remote app and got it to work, kind of. The problem I ran into was that when I used a Window-Eyes hotkey sometimes it ran on my local copy and sometimes it ran on the remote copy. Also sometimes when I entered text both the local and remote copies would echo back my keystrokes. I mentioned these things to AISquared/GW-Micro at the time, and they didn’t seem that interested in addressing it. I’ve not looked at it lately though. We really just don’t use RDS for anything beyond administration where I work, we use Citrix Xenapp for app delivery. Ryan
Hello all: I would like to know what remote desktop solution do you use for helpdesk support? Do any of you use the remote assistance feature that comes with system center? I find system center clunky to use with a screen reader. In my experience, Window Eyes works the best with it so far. It looks like nvda remote is the most responsive right now. Is anyone using either nvda by itself or nvda remote in a corporate environment? I know there was a post on here about the nada remote relay server developed by techno-es.
JAWS Tandem, Remote Incident Manager, Respectfully, Guerra Access Technology Training LLC An Authorized state of Minnesota Vendor for Technology Training Call Guerra Access Technology Training LLC guerra Access Technology Training LLC Visit Guerra Access Technology Training on the Web -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Kathryn Jedynak Sent: Friday, December 11, 2015 7:15 PM To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Subject: [Blind-sysadmins] remote desktop solutions Hello all: I would like to know what remote desktop solution do you use for helpdesk support? Do any of you use the remote assistance feature that comes with system center? I find system center clunky to use with a screen reader. In my experience, Window Eyes works the best with it so far. It looks like nvda remote is the most responsive right now. Is anyone using either nvda by itself or nvda remote in a corporate environment? I know there was a post on here about the nada remote relay server developed by techno-es. _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins
All, The problem with all the remote control solutions is that you require screen reader to be installed. Thus if you support customer’s who do not like this or have a platform that your software doesn’t work on. Then you are out of luck. It is fine for internal customer’s as you can educate. Far more difficult for external customers. Sean
Actually, the solutions from Serotek do not. They will use one if its there but they do not require the remote machine to run a screen reader. I think they are the only ones in this category. Remote Access Manager and Remote Incident Manager. I looked at RAM for my office a few years ago when I was doing more enduser troubleshooting for just that reason, we got a demo of it, but ended up not going with it as I moved into more server facing job duties. Ryan
It looks like RIM and RAM require a service to be running on any computer that you plan to access. Also, an end user's keystrokes are echoed back to them when they are entering a keyword to access a session.
The host is the program which is installed on each end-user's machine. It is provided as a Windows Installer (MSI) package, so system builders and technicians have flexibility in deployment options. Once deployed, the host software sits quietly in the background except when remote access is required. It makes no permanent system configuration changes, except to install itself as a Windows service. If not for a small icon in the system tray (normally located at the bottom of the screen), users would not notice that the host software was present until they needed it. The host software plays a crucial role in RIM's accessibility. Because the host software communicates with System Access, it can provide speech output to visually impaired technicians when they access it remotely. However, the end-user does not hear this speech output unless he or she is already running a separately installed copy of System Access. If the end-user is running another known screen reader, the host software informs the technician. If the end-user is running JAWS for Windows or Window-Eyes, the host will even send the screen reader's speech output to the client so the technician will hear it. [...] 3. The end-user presses Control+Shift+Backspace from anywhere in his or her system to invoke the remote incident feature of the host software. 4. The host prompts the end-user for the incident keyword, both visually and through speech output, even if the end-user's screen reader or other assistive technology is not functioning. 5. The end-user enters the keyword provided by the technician. The host echoes the letters the end-user types both visibly and audibly. Chris On Mon, Dec 14, 2015 at 10:48:40AM +1100, Sean Murphy wrote:
My guess is that this is SA behind the scenes, unless it detects a different screen reader on the host, in which case it forwards the audio of that other screen reader. -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Sean Murphy Sent: Sunday, December 13, 2015 9:46 PM To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Subject: Re: [Blind-sysadmins] remote desktop solutions Chris, This doesn’t answer the most important question. How does it work with programs that SA doesn’t support. The last time I used SA, it didn’t work with any console applications. Sean
_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins
Hi, Or even if it's internal and you are expected at any one time to log into 1 of thousands of servers as I was and was turned down from a post for Allstate because of this. Hence why I'm now studying the Linux LPI Essentials in the hope I'll be able to get a job using SSH for remote access. Barry. -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Sean Murphy Sent: 13 December 2015 02:14 To: Blind sysadmins list Subject: Re: [Blind-sysadmins] remote desktop solutions All, The problem with all the remote control solutions is that you require screen reader to be installed. Thus if you support customer’s who do not like this or have a platform that your software doesn’t work on. Then you are out of luck. It is fine for internal customer’s as you can educate. Far more difficult for external customers. Sean
_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins
Hi, Or even if it's internal and you are expected at any one time to log into 1 of thousands of servers as I was and was turned down from a post for Allstate because of this. Hence why I'm now studying the Linux LPI Essentials in the hope I'll be able to get a job using SSH for remote access. Barry. -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Sean Murphy Sent: 13 December 2015 02:14 To: Blind sysadmins list Subject: Re: [Blind-sysadmins] remote desktop solutions All, The problem with all the remote control solutions is that you require screen reader to be installed. Thus if you support customer’s who do not like this or have a platform that your software doesn’t work on. Then you are out of luck. It is fine for internal customer’s as you can educate. Far more difficult for external customers. Sean
_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins
I have Window-Eyes installed on about 200 servers where I work, probably more now since we bake it into the base image so whenever a new server gets deployed its just ready to go. My biggest complaint is its a paine to keep all those copies up-to-date. Mostly I don’t worry about it, but that means I’ve got Window-Eyes all the way from 7.1 to 9.2 running on various servers. That can be a paine. I have an SCCM collection to tell me what’s where but I’d love a more automated way to update it across the environment. I know I’m in a unique situation, or relatively unique, but I think about the government agencies that employ tons of blind people, and wonder how they keep all those screen readers up-to-date. Ryan On 12/14/15, 12:44 PM, "Blind-sysadmins on behalf of Barry Toner" <blind-sysadmins-bounces@lists.hodgsonfamily.org on behalf of barry@tonermail.co.uk> wrote:
Can't you bake Window-Eyes updates into the SCCM/WSUS update process? (and that's the current issue at my company' Citrix is used for some applications, and the Mass Commission only supports JAWS, to getting Window-eyes to be recognized it sort of hard.) -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Ryan Shugart Sent: Tuesday, December 15, 2015 12:40 AM To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Subject: Re: [Blind-sysadmins] remote desktop solutions I have Window-Eyes installed on about 200 servers where I work, probably more now since we bake it into the base image so whenever a new server gets deployed its just ready to go. My biggest complaint is its a paine to keep all those copies up-to-date. Mostly I don’t worry about it, but that means I’ve got Window-Eyes all the way from 7.1 to 9.2 running on various servers. That can be a paine. I have an SCCM collection to tell me what’s where but I’d love a more automated way to update it across the environment. I know I’m in a unique situation, or relatively unique, but I think about the government agencies that employ tons of blind people, and wonder how they keep all those screen readers up-to-date. Ryan On 12/14/15, 12:44 PM, "Blind-sysadmins on behalf of Barry Toner" <blind-sysadmins-bounces@lists.hodgsonfamily.org on behalf of barry@tonermail.co.uk> wrote:
Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins
Unfortunately not. While I’ve gotten Window-Eyes to install through SCCM, the way that AISquared bundles their updates is not very conducive to delivering them through an automated process, at least that I’ve been able to figure out. While the main installer has a silent install flag the updates don’t, and you can’t use the main installer to do an update from a previous version, you have to use a specific update installer. With time I could probably rap the installer in a script and perhaps do something with it that way, I just don’t have the time. For what its worth, Citrix is heavily used where I work too, but I just install my own applications on my workstation and RDP whenever I need to get to a server. Longterm the idea is to move more toward a VDI infrastructure, which is where a lot of companies are going, but I don’t think anyone’s thought through the accessibility implications yet. Ryan On 12/15/15, 10:18 AM, "Blind-sysadmins on behalf of Katherine Moss" <blind-sysadmins-bounces@lists.hodgsonfamily.org on behalf of Katherine.Moss@gordon.edu> wrote:
It is my understanding that RAM and RIM only work on Windows. This is not great for me, as I support a product called Git Fusion (among others) which only runs on Linux. I have a 'tmate' server set up, but I am finding that a lot of the customer's we support expect WebEx, GoToMeeting or similar. Trying to get them to jump through any extra hoops so that I can support them is tricky ans usually results in "We will wait for the US to com eonline" or similar. Given that the customer has to install something for the Serotek solutions to work, I don't personally consider it much of a jump for them to install NVDA and NVDA remote, also they are free. However, I find that as soon as I say the word "screen reader" to a customer, who is not always very tech savy and usually stressed, they freak out. It would be nice to have a cross-platform solution. Tmate only works for terminals (Unix and Linux). Cheers, Jen. On 12/15/15, Ryan Shugart <rshugart@ryanshugart.com> wrote:
HI, Have you tried Team Viewer? I am not sure if this will help. Do you require full access to the linux environment? There must be a way so the client can see what you are doing at the time of your support call if you are supporting Linux platform product. This is why they like products like WebEx. Sean
It seems like neither nvda, or nvda remote are not very popular in the United States. not too many people know about the nvda remote plugin nor the fact you can have a relay server. I learned about the open source relay server for nvda from Michal Dziwisz Tyfol podcast which is based in Poland. Now I'm trying to convince the place where I work at to implement it. It seems that people here are stuck on Jaws. They aren't aware that there are a few other screen readers out there.For example, you can use window eyes for free as long as you have Office 2010 and up. Of course, you can download nvda for free. Sent from my iPad
I disagree, I think a lot of people in the US are familiar with NVDA. It is one of the two leading screen readers now, although JAWS does have a pretty big margin. I have tried the NVDA Remote plugin myself, and my thoughts are that its a good solution for providing things like remote support etc. but when used to manage hundreds of servers in an enterprise environment or run virtualized apps in an enterprise environment it just doesn’t scale too well. Honestly, I’d just like to see RDP/Citrix support added to NVDA and it’d make a lot of Windows admins happy. I’m really surprised this hasn’t been done, all someone would really need to do is put in a virtual synthesizer channel so you aren’t using remote audio and I think that’d cover things. In fact, since NVDA doesn’t use a video driver, it’d be perfect for these kinds of environments since it’d be relatively easy to centrally manage, and it could be streamed just like most Citrix presented apps are these days. As I said, I’m really surprised no one’s gone down that road but perhaps everyone else knows something I don’t. As to remote support, unfortunately, I just don’t see any way of getting around the need for a screen reader to run on the remote machine. Screen readers, any screen reader, need a lot more information than standard screen sharing software like GotoMeeting or Webex provide. Webex and the like simply send a picture of the screen across from the remote machine, they don’t send any control information or actual text of what’s displayed. That’s why even RDP/Citrix access need a screen reader running on the remote machine, and that’s why Serotek had to have a limited version of SA running on the remote machine. The screen reader needs to get information from Windows about the controls in use, the text displayed, etc. and there’s just no other way to do that than running software on the remote machine. Ryan -----Original Message----- From: Blind-sysadmins on behalf of Kathryn Jedynak Reply-To: Blind sysadmins list Date: Wednesday, December 16, 2015 at 5:43 PM To: Blind sysadmins list Subject: Re: [Blind-sysadmins] remote desktop solutions
Kathryn, I wrote you private message but no response, perhaps you didn't receive it. Here is my article unfortunately in polish describing creation of customized package with nvda remote plugin configuret for customer: http://tyfloswiat.pl/Budujemy_wlasne_narzedzie_pomocy_zdalnej_z_wykorzystani... W temacie "[Blind-sysadmins] remote desktop solutions" Kathryn Jedynak pisze:
-- Michał Dziwisz michal@dziwisz.net
Michal, I was looking for that article actually. I think I will create a executable like that myself. By the way, when I set up the server in Windows, I couldn't not get it to run as a service. Did you or anyone else experience this issue? As a work around, I am running it on a Windows 7 machine and I put the shortcut of the nvda remote server executable in the startup folder. However, I would prefer for it to run as a service if possible. Sent from my iPad
Kathryn, I have the server running in a console in debug mode. Its usefull when you wanna know who is connecting. So when somebody is asking for help he/she only should click an icon and ask me. No more giving ip addreses or simmilar thinks. Cheers, Michał Dnia 18.12.2015 o godz. 05:38 Kathryn Jedynak <ms98kasia@gmail.com> napisał(a):
Hi Sean, Last time I looked at Team viewer, it was my understanding that it would only work Windows to Windows, and that both parties had to have NVDA installed. That was my reason for not going further with it. Regarding the NVDA remote discussion: Is it not possible to easily set up a relay server in-house? I thought that if you had a box with NVDARemote and NVDA on it, that could be some how configured to be your relay, but again I may be wrong. Also I sm not sure why the devs would potentially have to pay for making the source of the Relay server components available to the public. Does it contain components that are not under a GPL type license? Cheers, Jen. On 12/18/15, Michał Dziwisz <michal@dziwisz.net> wrote:
Hi Sean, Last time I looked at Team viewer, it was my understanding that it would only work Windows to Windows, and that both parties had to have NVDA installed. That was my reason for not going further with it. Regarding the NVDA remote discussion: Is it not possible to easily set up a relay server in-house? I thought that if you had a box with NVDARemote and NVDA on it, that could be some how configured to be your relay, but again I may be wrong. Also I sm not sure why the devs would potentially have to pay for making the source of the Relay server components available to the public. Does it contain components that are not under a GPL type license? Cheers, Jen. On 12/18/15, Michał Dziwisz <michal@dziwisz.net> wrote:
Hi Jen. the server is available on git hub. i've installed it on my raspberry Pi and its working very well. the devs have been totally unresponsive and I trawled for ages on various lists before finding someone that had a copy of it. you can get it from: https://github.com/Technow-es/NVDARemoteServer/ cheers, Mo. On 20/01/2016 16:20, Jen Bottom wrote:
Hi Mo, Just found this thread after my last post, in case anyone is interested: http://nabble.nvda-project.org/FW-NVDA-NVDA-Remote-security-and-setting-up-o... It also has a link to the OpenSource remote server's location. The company I work for are not happy about having anyone directly connect to a Windows machine, so I have been using NVDARemote.com for VMs etc, but not with customer's. Also they are more Linux oriented, so having somehting they can run and manage on a linux box is potentially good, though that doesn't mean they will implement it for me. I personally don't get a lot of call to assist people on Windows machines, so this is mainly a solution to enable me to work with Windows VMs, when trying to repro issues with our installer's etc. I will have a bash at setting this up for personal use when I get a chance. Cheers, Jen. On 1/20/16, Mobeen Iqbal <mobeeniqbal@gmail.com> wrote:
Hi Mo, Just found this thread after my last post, in case anyone is interested: http://nabble.nvda-project.org/FW-NVDA-NVDA-Remote-security-and-setting-up-o... It also has a link to the OpenSource remote server's location. The company I work for are not happy about having anyone directly connect to a Windows machine, so I have been using NVDARemote.com for VMs etc, but not with customer's. Also they are more Linux oriented, so having somehting they can run and manage on a linux box is potentially good, though that doesn't mean they will implement it for me. I personally don't get a lot of call to assist people on Windows machines, so this is mainly a solution to enable me to work with Windows VMs, when trying to repro issues with our installer's etc. I will have a bash at setting this up for personal use when I get a chance. Cheers, Jen. On 1/20/16, Mobeen Iqbal <mobeeniqbal@gmail.com> wrote:
Hi, The NVDA plugin is good, but I was very disappointed that they decided not to release the relay server themselves (in my view for reasons which didn't stack up), and since the release, they have closed the beta list and there hasn't been any further discussion on the addin. Further to this I don't believe it scales well to allow admin of several servers, and could potentially be seen as a backdoor by some IT departments. This is why I like the RDP so much: it uses existing interfaces to provide the remote desktop capabilities, which is known and loved by everyone. Andrew. ________________________________________ From: Blind-sysadmins [blind-sysadmins-bounces@lists.hodgsonfamily.org] on behalf of Kathryn Jedynak [ms98kasia@gmail.com] Sent: 17 December 2015 00:43 To: Blind sysadmins list Subject: Re: [Blind-sysadmins] remote desktop solutions It seems like neither nvda, or nvda remote are not very popular in the United States. not too many people know about the nvda remote plugin nor the fact you can have a relay server. I learned about the open source relay server for nvda from Michal Dziwisz Tyfol podcast which is based in Poland. Now I'm trying to convince the place where I work at to implement it. It seems that people here are stuck on Jaws. They aren't aware that there are a few other screen readers out there.For example, you can use window eyes for free as long as you have Office 2010 and up. Of course, you can download nvda for free. Sent from my iPad
_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins
Figures ... I'm not even going to go into my thoughts about that guy ... just suffice it to say, he's not my favorite developer in the world That's putting it nicely. But on the issue of RDP ... I'm just curious for the devs on this side, what API would that even use? I figured it was some proprietary thingo that AISquared and FS had with Microsoft, so that's why it doesn't work with NVDA, but maybe I'm wrong? -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Kathryn Jedynak Sent: Thursday, December 17, 2015 9:32 AM To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Subject: Re: [Blind-sysadmins] remote desktop solutions I aggree. The developers should have provided the relay server themselves even if it ment paying for it. I tryed contacting Christopher Toff but he never responded. Sent from my iPhone
_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins
There appears to be an NVDA ticket for this issue. #3564 (add support for sending speech over remote desktop protocol channels) http://trac.nvda-project.org/ticket/3564 Chris On Thu, Dec 17, 2015 at 05:39:09PM +0000, Katherine Moss wrote:
Katherine: I’m not a dev, but. There’s documentation for RDP here: https://msdn.microsoft.com/en-us/library/windows/desktop/aa383015(v=vs.85).a... Based on this, my guess, and its only a guess, is that all that the RDP support in JAWS or Window-Eyes does is use one of these extensible channels that the docs talk about. Text that would normally go to the synthesizer is sent through the extent channel just like it’d normally be sent to the synthesizer, the screen reader on the other end gets it and it continues on its way just as normal. I’m sure I’m really over simplifying things as again I’m not a dev, but it doesn’t look like making it work would be a really big deal, the foundations for it are already in the RDP spec. Ryan -----Original Message----- From: Blind-sysadmins on behalf of Katherine Moss Reply-To: Blind sysadmins list Date: Thursday, December 17, 2015 at 10:39 AM To: Blind sysadmins list Subject: Re: [Blind-sysadmins] remote desktop solutions
Figures ... I'm not even going to go into my thoughts about that guy ... just suffice it to say, he's not my favorite developer in the world That's putting it nicely. But on the issue of RDP ... I'm just curious for the devs on this side, what API would that even use? I figured it was some proprietary thingo that AISquared and FS had with Microsoft, so that's why it doesn't work with NVDA, but maybe I'm wrong? -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Kathryn Jedynak Sent: Thursday, December 17, 2015 9:32 AM To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Subject: Re: [Blind-sysadmins] remote desktop solutions I aggree. The developers should have provided the relay server themselves even if it ment paying for it. I tryed contacting Christopher Toff but he never responded. Sent from my iPhone
_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins
Hi, He doesn't seem to reply to anyone that I know of, including myself on any of his products. Barry -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Kathryn Jedynak Sent: 17 December 2015 14:32 To: Blind sysadmins list Subject: Re: [Blind-sysadmins] remote desktop solutions I aggree. The developers should have provided the relay server themselves even if it ment paying for it. I tryed contacting Christopher Toff but he never responded. Sent from my iPhone
_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins
He'll talk to you, but not about Q-continuum, or Accessable apps, or what ever the hell it's called now. -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Barry Toner Sent: Thursday, December 17, 2015 4:06 PM To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Subject: Re: [Blind-sysadmins] remote desktop solutions Hi, He doesn't seem to reply to anyone that I know of, including myself on any of his products. Barry -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Kathryn Jedynak Sent: 17 December 2015 14:32 To: Blind sysadmins list Subject: Re: [Blind-sysadmins] remote desktop solutions I aggree. The developers should have provided the relay server themselves even if it ment paying for it. I tryed contacting Christopher Toff but he never responded. Sent from my iPhone
_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins
He'll talk to you, but not about Q-continuum, or Accessable apps, or what ever the hell it's called now. -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Barry Toner Sent: Thursday, December 17, 2015 4:06 PM To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Subject: Re: [Blind-sysadmins] remote desktop solutions Hi, He doesn't seem to reply to anyone that I know of, including myself on any of his products. Barry -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Kathryn Jedynak Sent: 17 December 2015 14:32 To: Blind sysadmins list Subject: Re: [Blind-sysadmins] remote desktop solutions I aggree. The developers should have provided the relay server themselves even if it ment paying for it. I tryed contacting Christopher Toff but he never responded. Sent from my iPhone
_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins
Hi, He doesn't seem to reply to anyone that I know of, including myself on any of his products. Barry -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Kathryn Jedynak Sent: 17 December 2015 14:32 To: Blind sysadmins list Subject: Re: [Blind-sysadmins] remote desktop solutions I aggree. The developers should have provided the relay server themselves even if it ment paying for it. I tryed contacting Christopher Toff but he never responded. Sent from my iPhone
_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins
Hi, The NVDA plugin is good, but I was very disappointed that they decided not to release the relay server themselves (in my view for reasons which didn't stack up), and since the release, they have closed the beta list and there hasn't been any further discussion on the addin. Further to this I don't believe it scales well to allow admin of several servers, and could potentially be seen as a backdoor by some IT departments. This is why I like the RDP so much: it uses existing interfaces to provide the remote desktop capabilities, which is known and loved by everyone. Andrew. ________________________________________ From: Blind-sysadmins [blind-sysadmins-bounces@lists.hodgsonfamily.org] on behalf of Kathryn Jedynak [ms98kasia@gmail.com] Sent: 17 December 2015 00:43 To: Blind sysadmins list Subject: Re: [Blind-sysadmins] remote desktop solutions It seems like neither nvda, or nvda remote are not very popular in the United States. not too many people know about the nvda remote plugin nor the fact you can have a relay server. I learned about the open source relay server for nvda from Michal Dziwisz Tyfol podcast which is based in Poland. Now I'm trying to convince the place where I work at to implement it. It seems that people here are stuck on Jaws. They aren't aware that there are a few other screen readers out there.For example, you can use window eyes for free as long as you have Office 2010 and up. Of course, you can download nvda for free. Sent from my iPad
_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins
It is my understanding that RAM and RIM only work on Windows. This is not great for me, as I support a product called Git Fusion (among others) which only runs on Linux. I have a 'tmate' server set up, but I am finding that a lot of the customer's we support expect WebEx, GoToMeeting or similar. Trying to get them to jump through any extra hoops so that I can support them is tricky ans usually results in "We will wait for the US to com eonline" or similar. Given that the customer has to install something for the Serotek solutions to work, I don't personally consider it much of a jump for them to install NVDA and NVDA remote, also they are free. However, I find that as soon as I say the word "screen reader" to a customer, who is not always very tech savy and usually stressed, they freak out. It would be nice to have a cross-platform solution. Tmate only works for terminals (Unix and Linux). Cheers, Jen. On 12/15/15, Ryan Shugart <rshugart@ryanshugart.com> wrote:
Can't you bake Window-Eyes updates into the SCCM/WSUS update process? (and that's the current issue at my company' Citrix is used for some applications, and the Mass Commission only supports JAWS, to getting Window-eyes to be recognized it sort of hard.) -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Ryan Shugart Sent: Tuesday, December 15, 2015 12:40 AM To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Subject: Re: [Blind-sysadmins] remote desktop solutions I have Window-Eyes installed on about 200 servers where I work, probably more now since we bake it into the base image so whenever a new server gets deployed its just ready to go. My biggest complaint is its a paine to keep all those copies up-to-date. Mostly I don’t worry about it, but that means I’ve got Window-Eyes all the way from 7.1 to 9.2 running on various servers. That can be a paine. I have an SCCM collection to tell me what’s where but I’d love a more automated way to update it across the environment. I know I’m in a unique situation, or relatively unique, but I think about the government agencies that employ tons of blind people, and wonder how they keep all those screen readers up-to-date. Ryan On 12/14/15, 12:44 PM, "Blind-sysadmins on behalf of Barry Toner" <blind-sysadmins-bounces@lists.hodgsonfamily.org on behalf of barry@tonermail.co.uk> wrote:
Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins
Thanks ... I'll mess with it ... unfortunately the article in the knowledge base only addresses up to Windows Server 2008 R2, so I'm wondering whether I'm missing something in the configuration in 2012 R2 ... I mean, when activating the terminal services voice, how does one get it to stay active long enough to get it toggleable in the voice roder? (the way the KB article is written, is downright confusing, even for the most powerful of technologists, if you ask me). -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Ryan Shugart Sent: Friday, December 11, 2015 6:00 PM To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Subject: Re: [Blind-sysadmins] RDS, Remote App, and Window-Eyes Katherine: I played with remote app once a ton of years ago with an older version of Window-Eyes. I published both Window-Eyes and Calculator as a remote app and got it to work, kind of. The problem I ran into was that when I used a Window-Eyes hotkey sometimes it ran on my local copy and sometimes it ran on the remote copy. Also sometimes when I entered text both the local and remote copies would echo back my keystrokes. I mentioned these things to AISquared/GW-Micro at the time, and they didn’t seem that interested in addressing it. I’ve not looked at it lately though. We really just don’t use RDS for anything beyond administration where I work, we use Citrix Xenapp for app delivery. Ryan
_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins
Thanks ... I'll mess with it ... unfortunately the article in the knowledge base only addresses up to Windows Server 2008 R2, so I'm wondering whether I'm missing something in the configuration in 2012 R2 ... I mean, when activating the terminal services voice, how does one get it to stay active long enough to get it toggleable in the voice roder? (the way the KB article is written, is downright confusing, even for the most powerful of technologists, if you ask me). -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Ryan Shugart Sent: Friday, December 11, 2015 6:00 PM To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Subject: Re: [Blind-sysadmins] RDS, Remote App, and Window-Eyes Katherine: I played with remote app once a ton of years ago with an older version of Window-Eyes. I published both Window-Eyes and Calculator as a remote app and got it to work, kind of. The problem I ran into was that when I used a Window-Eyes hotkey sometimes it ran on my local copy and sometimes it ran on the remote copy. Also sometimes when I entered text both the local and remote copies would echo back my keystrokes. I mentioned these things to AISquared/GW-Micro at the time, and they didn’t seem that interested in addressing it. I’ve not looked at it lately though. We really just don’t use RDS for anything beyond administration where I work, we use Citrix Xenapp for app delivery. Ryan
_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins
Sorry, I'm only familiar with the Remote Desktop client. -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Katherine Moss Sent: Friday, December 11, 2015 12:23 PM To: Blind sysadmins list Subject: Re: [Blind-sysadmins] RDS, Remote App, and Window-Eyes What about remote app? In other words, when aplications are published from Terminal Services? Does that work via the same configuration? The knockedge base article says nothing about that. -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Troy Hergert Sent: Friday, December 11, 2015 10:27 AM To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Subject: Re: [Blind-sysadmins] RDS, Remote App, and Window-Eyes I'm not sure why it's not working for you, but I use this successfully all day long. Make sure that on both the server and your local machine, you have gone to the Window-eyes advanced options in the start menu and enable Microsoft virtual channel. I also implemented a group policy which applies not only to the server but every domain computer forcing audio redirection. These 2 things should enable this to work. I don't remember the exact group policy procedure for the audio redirection, but could go back and figure out the way to configure it if you need it. -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Katherine Moss Sent: Friday, December 11, 2015 8:57 AM To: 'blind-sysadmins@lists.hodgsonfamily.org' Subject: [Blind-sysadmins] RDS, Remote App, and Window-Eyes Hello all, A few questions. I know that some of this at least is addressed in the AISquared knowledge base, but it seems that either I or they are missing something. I'm attempting to run Window-Eyes 9.2 remotely on a server, for administration for one, and I've enabled virtual channel, and then when I go into the Window-Eyes settings to set up the Virtual Terminal services voice, it never actually activates and my settings always tend to revert back to the default. I hit activate on Virtual Terminal Services for Remote desktop, and at that moment, Window-Eyes stops speaking ... so there's sort of a caveat there isn't there? Anyway ... onto my second question. We're trying to set up remote app (my friend says he's got it working for his Active Directory site), and I'm wondering whether anyone has gotten Remote App working with Window-Eyes? (the KB article does not discuss it specifically when referring to Terminal Services, only to ZenWorks Presentation server ...) But I'd assume the pr ocedures for configuration are the same whether referring to remote app or to VDI? Thanks for input and suggestions, guys! _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins
participants (12)
-
Andrew Hodgson
-
Barry Toner
-
Chris Nestrud
-
Guerra Access Technology Training LLC
-
Jen Bottom
-
Katherine Moss
-
Kathryn Jedynak
-
Michał Dziwisz
-
Mobeen Iqbal
-
Ryan Shugart
-
Sean Murphy
-
Troy Hergert