Forum Discussion
Remote Desktop Web Audio Not Passing (Correctly)
Hello!
I manage an RDS farm (WEB/GW, CB, DB, HST etc) at work, and it's been working great aside from Audio Passthrough.
Clients will connect to the RD Website and then launch a remote app of their choosing. However, when the client is on the remote app PC and uses their audio (via an app or just using mmsys.cpl) the remote session will just freeze and be unusable. All RDS Infra is on at least Win. Server 2019+. All GPO Settings have been properly configured, as well as collection, CAP/RAP, and browser settings.
I have confirmed launching RDP (mstsc.exe) session from my local laptop to the remote app PC (through the HST) does work without any issue, so I am led to believe there is something wrong with RD Web. RD Web Client Pkg is on the latest version. Any advice is greatly appreciated as I am banging my head against the wall trying to get it to work with RD Web.
Cheers
1 Reply
Because the same RemoteApp audio works through mstsc, the Session Host audio service and collection policy are probably functional; the failure is isolated to the browser client path. First sign out of the frozen remote session rather than disconnecting, then test the identical RemoteApp in Edge and Chrome with extensions disabled. Confirm the browser is allowed to play audio and compare a full desktop launched through RD Web client. On RD Web Access, reinstall the latest web-client package and publish it first as Test, then reproduce against the test URL before promoting it with Publish-RDWebClientPackage -Type Production -Latest. Reimport the Broker certificate if it was renewed. At the failure timestamp, collect browser console/network errors plus RD Gateway, RD Web Access, Connection Broker, and Session Host event logs. If only web RemoteApp sessions freeze, provide those correlated logs to Microsoft support; changing CAP/RAP rules is unlikely to fix an established session
