I have an RDS deployment where users connect to a remote PC through the RD Web HTML5 client. The browser-based resource launch works normally until an application on the remote PC accesses the microphone, such as the Windows Recording settings.
At that point, the browser indicates that microphone access is active, but the remote session freezes for several minutes. It eventually becomes responsive again. CAP, RAP, collection, browser, and Group Policy settings have all been reviewed and configured correctly.
Audio and microphone redirection work without problems when connecting through standard RDP directly to the remote PC, through a session host, and even across additional RDP hops. The issue only occurs with the HTML5 client, using a recent 2.1.65.0 build. Has anyone encountered this behavior, or is microphone passthrough unreliable through the HTML5 client and multiple connection layers?
1 Answer
A useful first comparison is whether the same redirection works through a regular RDP client. If it does there but the HTML5 session freezes when the browser starts capturing the microphone, that points more toward a limitation or defect in the HTML5 client than a CAP, RAP, collection, or policy problem.
Standard RDP works normally, including direct connections, connections through a session host, and even additional RDP hops. The freezing only happens when the microphone is accessed through the HTML5 client, which is running version 2.1.65.0.