The default bug view has changed. See this FAQ.

Configure AWS Windows Server 2012 instances for audio support

RESOLVED FIXED

Status

Release Engineering
Platform Support
RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: aklotz, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

(Reporter)

Description

3 years ago
Windows Server 2012 is by default set up with its audio services disabled. Unfortunately this breaks our media tests that expect a working audio device.

Please configure these instances so that the "Windows Audio" and "Windows Audio Endpoint Builder" services have their startup mode set from "Manual" to "Automatic."

We also need to make a modification to start-rdp.bat:
audiomode:i:1 needs to be changed to audiomode:i:0

Comment 1

3 years ago
Chris,
Can you set this up?
Flags: needinfo?(catlee)
Sure

Aaron, do you know how to enable audio services programmatically?
Flags: needinfo?(catlee)
(Reporter)

Comment 3

3 years ago
Created attachment 8470182 [details]
Enable audio services batch file
(Reporter)

Comment 4

3 years ago
When run as Administrator, the above batch file will reconfigure the audio services to run automatically at startup.
(Reporter)

Comment 5

3 years ago
Created attachment 8470190 [details]
Start audio services batch file

Alternatively, here is a batch file that will forcibly start the services when run as Administrator.
Great, thanks.
Ok, I created ami-bb87fd8b that has the appropriate changes in it. I'm trying to re-create the instances with the new AMI, but a ton of code has changed since we last used this so it's not working out of the box. Will try again soon.
Ok, I had to regenerate the AMI again.

New AMI in us-west-2 is ami-03ff8533. I've re-created tst-w64-ec2-001 with the new AMI. The old instance is still available, but stopped (named tst-w64-ec2-001-old).

If tst-w64-ec2-001's results look good, I'll do the same for -002.
tst-w64-ec2-001 looks ok, so I'm going to re-create -002 as well.

Updated

3 years ago
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.