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.
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.