(paraphrasing :vlad) On a Windows 64 AWS test slave, there was an issue where the autologin'd user wasn't getting a proper gfx environment. The solution described at https://bugzilla.mozilla.org/show_bug.cgi?id=886640#c23 works and is an easy path forward. We need to implement this in the tester AMI setup -- it is blocking getting most of the tests greened up, since the majority of the ones that are failing are graphics-related.

To verify that things are successful, have the "real" cltbld user also start firefox.exe as part of its login/startup script. When you connect to it via RDP after startup (to check), Firefox should be running, and all the HW accel bits in about:support should show as enabled (D2D/DWrite should be true, GPU Accel Windows should be D3D10 1/1, WebGL should have a renderer; the Adapter should be RDPUDD Chained DD or something like that).

I've set up tst-w64-ec2-001 with the following steps: https://etherpad.mozilla.org/tst-w64-ec2-rdp-setup I'm running test builds against my staging buildbot master: http://dev-master01.build.scl1.mozilla.com:8901/buildslaves/tst-w64-ec2-001 Two settings that need to be undone on tst-w64-ec2-001: * in AWS console, set mozstate back to 'ready' * in slavealloc, set tst-w64-ec2-001 properties to match other tst-w64-ec2-00X hosts and reboot

(In reply to John Hopkins (:jhopkins) from comment #2) > I've set up tst-w64-ec2-001 with the following steps: > > https://etherpad.mozilla.org/tst-w64-ec2-rdp-setup Hmm, VNC really shouldn't be involved at all here. I'm not sure if it hurts any, but it definitely doesn't help -- and having it installed at all might screw up some of the sessions if it tries to hook into them. Instead of installing VNC and connecting via VNC to log in as cltbld-starter, you can just RDP in as cltbld-starter.

I think VNC was required here to be able to log in and verify everything is working properly. with both cltbld and cltbld-starter having active sessions, you're not allowed to login as Adminstrator via RDP since there's a max of 2 active sessions. In any case, I've automated the creation of this user and its on-logon scripts in our AMI creation tools.