No sound card is needed for RDP, nor for Enhanced Session mode; both use RDP at their cores, though it's enabling RDP that I'm having issues with through VMConnect which is the virtual equivalent of connecting a monitor to the VM, essentially. -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Troy Hergert Sent: Monday, November 20, 2017 2:47 PM To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Subject: Re: [Blind-sysadmins] Virtualization MS Hyper-V Thank you this is helpful information. I'm not really clear as if you are having the same problem Katherine is? I have not yet seen the Hyper V console but I assume at the server, if it has a sound card there could be audio when starting the virtual server with rdp enabled? Sorry if my question is off, but I'm inexperienced with Hyper V up to this point. Just trying to pre plan properly. Thanks. -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Timothy Spaulding Sent: Monday, November 20, 2017 1:06 PM To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Subject: Re: [Blind-sysadmins] Virtualization MS Hyper-V Good point, I did forget this part as the RDP capabilities are turned off by default. -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Katherine Moss Sent: Monday, November 20, 2017 12:53 PM To: 'Blind sysadmins list' <blind-sysadmins@lists.hodgsonfamily.org> Subject: Re: [Blind-sysadmins] Virtualization MS Hyper-V While on this subject, I have a Windows Server 2016 image and since it does not have RDP enabled by default, I always have to (or rather someone else does for me), go into the Hyper-V VMConnect application and then enable it, though even with enhanced session mode turned on, I don't get audio by default, seemingly, and I get stuck in the application with no easy way out other than to kill it. Am I missing something? -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Timothy Spaulding Sent: Monday, November 20, 2017 12:34 PM To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Subject: Re: [Blind-sysadmins] Virtualization MS Hyper-V Here is what I know/have personally used: - The Hyper-V console is accessible for creating and configuring a Virtual Machine - the is no audio access for installing the OS on a Virtual Machine via Hyper-V (I have no knowledge/experience with the different flavors of VMWare) - Once the OS is installed and configured in the Virtual Machine, you can install JAWS as a remote client - As long as your local copy of JAWS has the remote option set on the authorization key you are using, then you can use the remote desktop app to connect to the remote machine and use it normally. If you attempt to connect within the Hyper-V console to the remote machine, this connects at the console level and JAWS will not use the remote authorization to activate the copy of JAWS on the remote machine. Tim -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Troy Hergert Sent: Monday, November 20, 2017 11:58 AM To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Subject: [Blind-sysadmins] Virtualization MS Hyber V Hello everyone, I know there has already been discussions on this list about server virtualization. My small nonprofit has finally come to a point where my LAN support team is recommending that we consider virtualizing our server. I am being advised to run Microsoft hyper V , so that I can virtual eyes a 2012 server, along with a linux server. Would someone kindly remind me what the current level of accessibility is regarding speech with jaws or NVDA in those environments? Thanks. Troy Hergert Information Technology Manager Email: thergert@vision-forward.org Tel: 414-615-0122 The information transmitted, including attachments, is intended only for the person(s) or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and destroy any copies of this information. _______________________________________________ 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 _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins