How can I configure MS Windows 2000 (Or XP; I would upgrade for this
feature) so that when acting as a remote terminal server it outputs
audio to the server's sound output instead of trying to map the audio
to the client?  I have the server connected to my stereo system and
I'm trying to use the client as a remote control.  The terminal server
always tries to map the audio to the client.  **Answer must state how
to do it, not that it is impossible.**

---

Request for Question Clarification by poormattie-ga on 06 Feb 2003 18:42 PST

I just want to be sure-- you are running Windows 2000 Server (or
Advanced Server), correct?

Can you mention what you've tried thus far? The documentation I've
read just now seems to indicate it's quite easy to get the server to
play sounds-- but very difficult (with Win2k server) to get the client
to. (Unfortunately, I just removed my sound card from my Win2k Server
box a couple weeks ago, so I can't immediately try it myself. I know I
used my sound card a great deal on the serevr machine itself, I'm just
unsure if I ever invoked it through a client connecton.)

Are you certain the sound card itself is working properly? What kind
of messages do you receive when it 'tries to map the audio to the
client'?

Thanks very much for your clarification.

---

Request for Question Clarification by mrbuzz-ga on 06 Feb 2003 22:09 PST

Hi minermbel-ga,

Windows XP/Server 2003's RDP allows 3 different options for audio
mapping: Leave at server, bring to client and mute.  Let me know if
this is what you were looking for.

Regards,
mrbuzz-ga

---

Clarification of Question by minermbel-ga on 06 Feb 2003 23:15 PST

MRBUZZ-GA, yes, that will cover what I need to do.  I am leaving this
question open so that you can close it out and get paid.  I can see
how I need to configure this in Server 2003.  **I AM ASKING OTHER
RESEARCHERS TO CONSIDER THIS QUESTION PERMANENTLY LOCKED BY
MRBUZZ-GA**  He has already given the secret.  I am afraid that if I
close the question before he submits the "OFFICIAL ANSWER" I won't be
able to pay him.

Hi minermbel-ga,

Windows XP and Server 2003’s Terminal Services (aka Remote Desktop)
have advanced quite a bit since the days of Windows 2000.

I’ve used audio redirection using “Leave at remote computer” mode in
two instances.  One was a LAN party where the ‘server’ computer
(running WinXP Pro, no monitor) was hooked up to a few nice speakers
and I’ve used it from my computer, like you’ve mentioned to act as
“remote control”, for Winamp.  The other is to startle people who
might be in the computer room at my house by playing music loudly
while I was at school or work. :)

This solution is very simple if you’re using Window XP Professional
(not sure if this will work with XP Home since I don’t have any
licenses for it, though I don’t see why it wouldn’t).  With Windows
Server 2003, I believe audio redirection is disabled by default in RDP
for administration mode so you’ll need to change a few settings if you
plan to use Windows Server 2003.  My solution below will assume that
you will be using Windows XP Professional.  Let me know if you will be
using Server 2003 RC2 or a later beta build and I will post the
necessary settings that you will need to change for that OS.

First, make sure you’ve patched up to Service Pack 1 for Windows XP. 
This will at least protect your computer from a few nasty bugs.  If
your client computer is not running Windows XP, you will need to
download a copy of the Remote Desktop Connection Client at
(http://www.microsoft.com/windowsxp/pro/downloads/rdclientdl.asp ).

Once you’ve installed all necessary sound drivers for your new Windows
XP install on the ‘server’ machine, you will need to enable Remote
Desktop.  This can be done through the System Control Panel, Remote
tab and check the box that says “Allow users to connect remotely to
this computer”.

Now, on your client machine, in the Remote Desktop Connection Client
(Start, Programs, Accessories, Communications) that you’ve downloaded,
click on the Local Resources tab, and under Remote Computer Sound,
choose “Leave at remote computer”.

Feel free to modify other settings in the client.  Once done, I would
strongly recommend you save a copy of connection settings by going to
the General tab and click Save As at bottom.

Now when you connect to your Windows XP machine and use Winamp or any
other media player software, the sound should be left at the server.

I’ve just now gone to confirm that this works.  I’ve tested it so far
on 3 of my home machines (all running Windows XP Pro) and verified
that it works as described above.

Please let me know if you encounter problems through the “request
clarification” button and I will do my best to help you until you are
satisfied with the answer.

Thanks,
mrbuzz-ga

Thank you this is going to do the trick.  I will upgrade to XP and do this.

I have successfully set this system up as follows:
Server: pII-466  / 256 / 10/100 / SB128PCI  / XP_Pro_SP1
Client: pIII-1.0 / 384 / 10/100 / SBLivePCI / XP_Pro_SP1

Initially I could use the Client to get the Server to play through its
own speakers (as a remotecontrol setup). One time however I wanted to
play the sound locally so I set that "Bring to this computer" option
in the Client's RDC options. Once in the Server, the Sound control
panel showed "Microsoft RDP Audio Driver" as the selected audio
device.

On subsequent connections I reverted to sound "Leave at remote
computer" yet audio programs complain there is no sound device
installed. Sound control panel still lists "Microsoft RDP Audio
Driver" as the only audio device. But Device Manager shows the SB128
and its game port both present and correct. I told DevMan to uninstall
the device, scan for harware changes, and it found it again and set it
up again. Going back to the Sound control panel it still isn't listed.
Rebooted, no different. That's quite a pain if you can't disable audio
retreival if you have once enabled it.