You're right, it's a big bummer we can't get that kind of information. My own personal example is with password expirations. We have several template base images where the local administrator password you're supposed to use to log onto the machine to do the setup before joining it to the domain has expired. It's a real pain, and sometimes the easiest approach is to just get a friendly pair of eyes to walk me through the process. Still very annoying though. One thing that might be worth trying, although this will totally depend on your network connectivity and how your machines are set up, is to try running Narrator. It gives me horrible performance over RDP, but I have gotten it to work from time to time. By default, sound is turned off on server versions of Windows, I turn the audio services on when I build templates for things like this, and they can also be enabled through GPOs. Ryan -----Original Message----- From: blind-sysadmins-bounces@lists.hodgsonfamily.org [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Darragh OHeiligh Sent: Tuesday, July 12, 2011 7:30 AM To: Blind sysadmins list Cc: blind-sysadmins-bounces@lists.hodgsonfamily.org Subject: Re: [Blind-sysadmins] Access using remote desktop. Your definitly right, You can fource the log information to be provided before the remote desktop session starts however for reading remote errors it would be great to have a screen running. I know that's not possible at the moment though. Specifically, I was trying to access a test desktop with a newly created temporary test account in a specific OU. I had forgotten to give the user remote desktop access permissions so I was getting an error on the remote end. If jaws had read that error it would have saved me a lot of time. Regards Darragh Ó Héiligh Fujitsu Offices of the Houses of the Oireachtas, Fredrick Building, South Fredrick Street, Dublin2 Telephone: +353 (1) 618 3559 Email: darragh.oheiligh@oireachtas.ie Internet: http://www.oireachtas.ie From: Ryan Shugart <rshugart@pcisys.net> To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Date: 12/07/2011 14:25 Subject: Re: [Blind-sysadmins] Access using remote desktop. Sent by: blind-sysadmins-bounces@lists.hodgsonfamily.org Hi Darragh: On the first problem, there are a few ways I've worked around this. With a Windows 7 RDP client RDPing to a Windows Server 2008R2 machine, all the login information is asked for on the client end before the connection is even made. You can force this on earlier connections by checking the show more box, and then entering a username and password. I also have just memorized the steps, for example, on Windows Server 2003, once the connection is made, alt+u username, alt+p password, enter works. Sometimes you need to do enter, alt+u username, alt+p password, enter if you have a login banner like we do on some of our machines. Windows Server 2008, not 2008R2, can be more difficult because the usernames appearing on the login screen can vary, but in that case you can force the client to ask for credentials, and most of the time if it's a server you and only you log into, your name will be the default. On the second problem, I use Window-Eyes, not JAWS, so can't comment accept to say I've not seen this abnormally, AKA no more in an RDP session than I'd see it on a standard console session, so I'd guess it's a JAWS issue. Ryan -----Original Message----- From: blind-sysadmins-bounces@lists.hodgsonfamily.org [ mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Darragh OHeiligh Sent: Tuesday, July 12, 2011 6:47 AM To: Blind sysadmins list Subject: [Blind-sysadmins] Access using remote desktop. Greetings, I have 2 problems when using remote desktop. I'm assuming most if not all of you have these problems as well however in case you have a work-around I thought I'd post here. The first problem is I am unable to read the log in screen for any version of Windows when accessing it using remote desktop. This means that If trying to switch users in Windows 2008 or I get a log in error in Windows 2003 I am unable to read it. I'm using the Jaws screen reader. I don't expect that there's a work-around for this. Do any of you have a way of reading log in errors when accessing a system using remote desktop? The next problem is something I've been reporting for years. It was fixed for a while around Jaws 9 or 10 however it's back again. In fairness, I'm not totally convinced it's an issue caused by Jaws any more. The alt or control keys seem to stick when using a remote desktop. For example, after pressing alt tab a few times then pressing alt F4 you might find that if you press the letter e, alt is still pressed even though on the physical keyboard it's not pressed at all. I have spoken to people in FS right from Eric to the tech support people. They seem unable to reproduce the problem or unable to resolve it. I however can reproduce it in seconds on any system I use. I have also experienced this problem when using tandem. Any ideas? Thanks Regards Darragh Ó Héiligh Fujitsu Offices of the Houses of the Oireachtas, Fredrick Building, South Fredrick Street, Dublin2 Telephone: +353 (1) 618 3559 Email: darragh.oheiligh@oireachtas.ie Internet: http://www.oireachtas.ie _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins