Re: audio issues with Windows 2003 Remote Desktop?
- From: "TP" <tperson.knowspamn@xxxxxxxxxxxxxxx>
- Date: Wed, 16 Aug 2006 14:58:13 -0400
To connect to the console, use the /console command line switch. For example:
mstsc /console
-TP
Kremlar wrote:
I had an audio application I ran on a Windows XP box in my rack. I.
would login via Remote Desktop, it would login and control the
session currently running on that PC, and I could control that app.
I switched that machine out with a Windows 2003 Server box. I enabled
Remote Desktop through the System control panel. The problem I'm
having is that when I login via the Remote Desktop client it creates
a new session rather than taking control of the existing console
session, and this new session it creates doesn't seem to have audio
functionality so the application doesn't work correctly.
If I go into audio devices, I only see a RDP audio driver rather than
the sound cards installed on that PC. In the Remote Desktop client,
I have "Leave At Remote Computer" selected under the sound setting.
Is there any way to change this so it behaves more like my XP box, or
should I just control the box via different means (VNC or pcAnywhere,
etc...)???
Thanks!!
- References:
- audio issues with Windows 2003 Remote Desktop?
- From: Kremlar
- audio issues with Windows 2003 Remote Desktop?
- Prev by Date: Re: Local Drives in TS session
- Next by Date: Re: Terminal Server Configured as Per User is giving out Temporary Device Licenses
- Previous by thread: audio issues with Windows 2003 Remote Desktop?
- Next by thread: Re: Event ID 1004 No Terminal Server License
- Index(es):
Relevant Pages
|