Audio Mapping

Post a reply

Smilies
:D :) :( :o :shock: :? 8) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :wink: :!: :?: :idea: :arrow: :| :mrgreen:

BBCode is OFF
Smilies are ON

Topic review
   

Expand view Topic review: Audio Mapping

Re: Audio Mapping

by aka » Mon Sep 20, 2010 1:22 pm

Please, try 4.6.7.

Re: Audio Mapping

by HGRIM » Fri Sep 17, 2010 5:46 pm

For those of you that have this same problem, I created a new config file with the exact same lines as my old config and this fixed my issue. I'm not sure what changed but sound does map to the thin client now.

Audio Mapping

by HGRIM » Thu Sep 16, 2010 11:31 pm

We have a thin client booting with a flash drive using WTWare Pro 4.6.4 . The config file is pointing to a Terminal Server and all is working except the audio. I have a Group Policy applied to the Terminal Server that has audio mapping enabled. This is enabled with the 'Allow Audio Redirection' in Computer Configuration->Administrative Templates->Windows Components->Terminal Services->Terminal Server->Device and Resource Redirection. If I login to the Terminal Server from the thin client, no sound is mapped but if I use a Windows RDP session, the audio is mapped. I am using the same account to login to the Terminal Server and Windows RDP. In my config file, I have the following lines:

sound=on
sound_level=100

I have also verified audio is being mapped by using a non-WTware thin client. Is there something I am missing in the config that is not allowing sound to be mapped? I have also tried adding the line sound=remote. Any help would be appreciated. Thanks.

Top