I’ve been developing some tutorials for our users on local network and posting them on our Sharepoint Intranet. Most of our users use Windows Terminal Server 2003 to connect to the Intranet though, and by default sound on Windows Terminal Server is disabled.
By the way, if you are trying to do this enable sound on Windows Terminal Server 2000 it is not possible as the Remote Desktop Protocol used in Windows Server 2000 does not support it.
There are two ways that you can enable sound on Windows Terminal Server 2003. One is through Terminal Services Configuration on the Terminal Server, and the other is through the Group Policies. Depending on how you have Group Policies configured you may need to do both. In this tutorial we will look at the first option:
Enable the Sound on the Windows Terminal Server
Enabling the sound on the Windows Terminal Server is a simple, four step process.
- In Terminal Services Configuration, click on “Connections”
- Double-click RDP-Tcp
- Click on the “Silent Settings” tab
- Clear the check-mark from the Audio mapping box
Below is a screen shot of the configuration window:
This setting will now apply to all new Windows Terminal Server sessions, but the individual clients will also need to enable the feature on their local computer.
Enable the Sound in Remote Desktop Client
- Open your Remote Desktop Client
- Click on the “Options” button
- Click on the “Local Resources” tab
- Change the “Remote Computer Sounds” dropdown to “Bring to this Computer”
- Then apply the changes.
Here is a screen shot of that configuration window:
Then after connecting you should be able to hear audio.
5 responses so far ↓
1 Richard // Aug 19, 2008 at 9:08 pm
Doesn’t there have to be a sound card in the server though?
2 Bill Hutchison // Aug 20, 2008 at 12:15 am
As far as I know you don’t need a sound card on the server, as long as under “Remote Computer Sound” you choose to “Bring to This Computer”. Then it depends on your local computer having a sound card.
All the servers that I have used actually have built in sound cards, so although I think that it should work on all servers, I don’t currently have a way to test it.
3 Peter Draganov // Oct 3, 2008 at 11:45 am
You definitely need a sound card on the server. Our terminal server is on an IBM blade which doesn’t have sound card and it cannot be added. Windows Media Player gives:
“Windows Media Player cannot play the file because there is a problem with your sound device. There might not be a sound device installed on your computer, it might be in use by another program, or it might not be functioning properly.”
I selected in Tools/Options/Devices/Speakers DirectSound: Microsoft RDP Audio Driver (emulated)
4 Bill Hutchison // Oct 6, 2008 at 1:33 pm
Hi Peter.
Thanks for clarifying that the server needs a sound card for the sound to work over a terminal session. It’s good to know.
Bill
5 John R // Oct 21, 2008 at 7:42 am
Weird,
I have terminal services set up on servers that do not have a soundcard, and sound can still be redirected to the clients.
In Device Manager, I have the following devices listed under Sound, video and game controllers:
Audio Codecs
Legacy Audio Drivers
Legacy Video Capture Devices
Media Control Devices
Video Codecs
Leave a Comment