Hi Andrew: I've never had a need to do an automated JFW install, I've always been able to use the interactive installs, but I've only needed it on one or two machines. Back in the day when Window-Eyes was a concern I got an automated install working using SCCM but we ended up not using it because we wanted it on all of the servers in the company at the time, and had been advised on several fronts it would be best to just incorporate it into the server build template image. I've ran both Window-Eyes and JAWS in Azure using RDP and have never had a problem due to not enough VRAM, I didn't think JAWS used a lot of VRAM in the main video driver. My own recommendation, if you have access to a template against which all servers are built to incorporate the screen reader in there, that way it will be there and ready to go whenever a new server is built, and you can test it in the template and be 99% sure it will work when you build out a server using that template. When you do this, I'd make sure JAWS is not set to start automatically at all, either at the logon screen or post logging into the server, in theory that way it will have a very small footprint on normal server operations. You'll either have to assign it to a hotkey or get good at typing windows+r and jaws2021 and enter. I also went ahead and enabled the Windows audio service in the templates I built and made sure audio redirection was working over RDP. I know there are those whould disagree with that approach, but I didn't see it as introducing that much of an overhead, and when I did this I ran it past other IT people at the company including our security people, and they agree there was a legit reason to do this so that I'd have something to use as a backup in case a screen reader failed to launch. Ryan -----Original Message----- From: Andrew Hodgson <andrew@hodgson.io> Reply-To: Mailing list for blind system administrators <blind-sysadmins@lists.hodgsonfamily.org> Date: Sunday, January 31, 2021 at 5:01 AM To: Mailing list for blind system administrators <blind-sysadmins@lists.hodgsonfamily.org> Subject: [Blind-sysadmins] Re: What is the best way to access Windows server 2012 and 2016 instances in the cloud? Hi, I have to say I've had difficulties getting cloud installations working on an automated fashion. I think it had something to do with the way I was running the installation. I tried running it via some login scripts and also via a CLI VM task in Azure. I did get to a point where I had a running JFW but it kept complaining about video drivers, when talking to S&S (UK distributor) they said it was because there wasn't enough VRAM available. My recent work in Windows is now a bit limited, but anything I did remotely I did via scripts which I could run easily and get output in particular files, or use remote MMCs like Server Manager and other remote admin tools which meant I didn't have to RDP to the server. This may potentially change as security are always going on about us accessing servers (even Linux boxes or Kubernetes) via Windows bastion boxes using RDP which is going to be a significant game changer for me. If I was forced down the route of using a bastion I was potentially looking at building a VM image with JFW pre-loaded, building the image using Packer and DSC. I have some jobs that do this already with Linux and Ansible, but not Windows. Whether you would want to use that as a generalised server build for mainline workloads is another matter. Andrew. -----Original Message----- From: Jared Stofflett <stofflet@gmail.com> Sent: 29 January 2021 19:47 To: Mailing list for blind system administrators <blind-sysadmins@lists.hodgsonfamily.org> Subject: [Blind-sysadmins] Re: What is the best way to access Windows server 2012 and 2016 instances in the cloud? Do you have any examples of group policy to automatically install Jaws? I won't be doing the builds but it sounds like we will have enough servers that we will be building them with automation instead of manually. On Tue, Jan 26, 2021 at 8:01 PM Ryan Shugart <rshugart@ryanshugart.com> wrote: > Hi Jared: > I've never used Oracle Cloud before, but have done this with > Azure quite a bit and have had good success. If you can get RDP to > work then you should be able to get a copy of JAWS installed and use > remote access just as normal. In fact, if you can get remote audio > enabled, you can use Narrator to navigate to and then run the talking install and be all good. > Hope this helps. > Ryan > > -----Original Message----- > From: Jared Stofflett <stofflet@gmail.com> > Reply-To: Mailing list for blind system administrators < > blind-sysadmins@lists.hodgsonfamily.org> > Date: Tuesday, January 26, 2021 at 5:31 AM > To: blind-sysadmins <blind-sysadmins@lists.hodgsonfamily.org> > Subject: [Blind-sysadmins] What is the best way to access Windows > server > 2012 and 2016 instances in the cloud? > > I've started a new job and may need to access Windows server 2012 > and > 2016 > instances in Oracle cloud. What is the best way to do this? My > thought is > to have group policy install Jaws with remote access. Although I'm > an NVDA > user I don't want to be installing the remote access add-on into > servers. > I'm also not sold on the Unicorn remote access solution since I > have not > heard much about it good or bad. In my limited experience remote > desktop > with Jaws was pretty reliable. > Thanks for any advice. > _______________________________________________ > Blind-sysadmins mailing list -- > blind-sysadmins@lists.hodgsonfamily.org > To unsubscribe send an email to > blind-sysadmins-leave@lists.hodgsonfamily.org > > _______________________________________________ > Blind-sysadmins mailing list -- > blind-sysadmins@lists.hodgsonfamily.org > To unsubscribe send an email to > blind-sysadmins-leave@lists.hodgsonfamily.org > _______________________________________________ Blind-sysadmins mailing list -- blind-sysadmins@lists.hodgsonfamily.org To unsubscribe send an email to blind-sysadmins-leave@lists.hodgsonfamily.org _______________________________________________ Blind-sysadmins mailing list -- blind-sysadmins@lists.hodgsonfamily.org To unsubscribe send an email to blind-sysadmins-leave@lists.hodgsonfamily.org