To enable audio on Windows Server 2012, configure playback in the Remote Desktop client and start the server’s Windows Audio services. The complete setup usually takes about five minutes and sends sound from the RDP session to your local computer.
Prerequisites
- A VPS running Windows Server 2012 with an active RDP connection.
- Local administrator access on the server, plus a Windows PC with working speakers or headphones.
- Permission to change the local Group Policy if an existing policy blocks audio redirection.
- A Windows RDP server from VPSLake if you still need a suitable Windows VPS.
Step 1: Allow playback in the RDP client
The RDP client decides whether the remote session’s sound is played on your computer, so enable this before opening a new session.
On your local Windows computer, open the Run dialog with Windows key + R, enter mstsc.exe, and select OK. Then follow this path:
- Select Show Options.
- Open the Local Resources tab.
- Under Remote audio, select Settings.
- In Remote Audio Playback, choose Play on this computer.
- Leave Remote Audio Recording set to Do not record unless you also need to send microphone audio to the server.
- Select OK, then connect to the Windows Server 2012 VPS.
If the RDP window is already open, disconnect and reconnect after saving this option. Audio redirection settings are negotiated when the session starts, so changing the setting while connected may not affect the current session.
Microsoft documents the same client-side choice in its Remote Desktop connections FAQ.
Step 2: Start the Windows audio services
Windows Server 2012 needs its audio services running before an RDP session can create a remote playback device.
Inside the server session, press Windows key + R, enter the following, and select OK:
services.mscIn the Services console, find Windows Audio, open its properties, and set Startup type to Automatic. Select Start, choose Apply, and then select OK.
Also check Windows Audio Endpoint Builder. It should show Running; if it is stopped, open its properties, set Startup type to Automatic, start it, and apply the change. This service supplies the audio endpoint that Windows exposes to the RDP session.
You can check both services from an elevated PowerShell window:
Get-WmiObject Win32_Service -Filter "Name='Audiosrv' OR Name='AudioEndpointBuilder'" | Select-Object Name,State,StartModeExpected output is similar to this:
Name State StartMode
---- ----- ---------
AudioEndpointBuilder Running Auto
Audiosrv Running AutoStep 3: Permit RDP audio redirection in local policy
The client option cannot override a server policy that explicitly blocks audio and video playback redirection.
On the server, open the local Group Policy Editor:
gpedit.mscGo to Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Device and Resource Redirection. Open Allow audio and video playback redirection, select Enabled, and choose Apply → OK.
Apply the policy, then reconnect the RDP session:
gpupdate /forceExpected output includes:
Updating policy...
User Policy update has completed successfully.
Computer Policy update has completed successfully.If the VPS belongs to a domain, a domain Group Policy can override this local setting. Microsoft lists the policy name and its location in the TerminalServer policy reference.
Confirm audio playback
Reconnect with the RDP client after completing the settings above. On the server, open the sound control panel:
mmsys.cplOn the Playback tab, look for Remote Audio or Speakers (Remote Audio). Select it, choose Properties, and use the Test control. You should hear the test tone through the speakers or headphones attached to your local computer.
The service check should still show both services running:
Get-Service -Name Audiosrv,AudioEndpointBuilder | Select-Object Name,StatusExpected output:
Name Status
---- ------
AudioEndpointBuilder Running
Audiosrv RunningTroubleshooting
No Remote Audio device appears
The RDP client was probably opened before playback redirection was enabled, or the server policy is blocking it. Close the RDP session completely, set Local Resources → Remote audio → Settings → Play on this computer, confirm the playback policy is enabled, and reconnect.
Windows Audio will not start
Windows Audio depends on Windows Audio Endpoint Builder. In services.msc, start Endpoint Builder first, then start Windows Audio. If a service immediately stops, check Event Viewer → Windows Logs → System for the related service error and restart the server after saving any pending Windows updates.
The test tone is audible on the server but not on the local PC
The server is producing audio, but the local endpoint is muted or the RDP session is sending playback to the wrong place. In the RDP client’s Remote Audio Settings, select Play on this computer, then check the local Windows volume mixer and selected output device. A disconnected session cannot deliver audio even when the services remain healthy.
Group Policy keeps changing back to Disabled
A domain policy or managed security baseline is taking precedence over the local setting. Review the applied policies with an administrator, or ask the domain administrator to allow audio and video playback redirection for this session host; repeatedly changing the local policy will not override a domain rule.
FAQ
Does enabling Windows Audio open a new firewall port?
No. RDP audio playback is carried inside the existing RDP session, so this change does not require a new inbound firewall rule or an additional exposed port.
Can I use this setup for microphone input too?
Yes, but microphone input is a separate redirection choice. In the local RDP client, open Local Resources → Remote audio → Settings and select an option under Remote Audio Recording; a server policy may also restrict recording redirection.
Why do I need to reconnect after changing the RDP option?
The RDP client negotiates device redirection while it creates the session. A session that was already connected may keep its original audio configuration until you disconnect and sign in again.
Will audio continue after I close the RDP window?
No. Closing or disconnecting the RDP session ends the path that carries playback to your local device. Keep the session connected while the application needs to play sound.
