Many ThinManager Ready thin clients have the capability to play sound. The following conditions need to be met to get sound to work properly:
- Windows 2003 or greater must be used. Sound is not supported on Windows 2000 terminal servers.
- Make sure that Audio Mapping is allowed on the Client Settings tab of the RDP-tcp Properties in the Terminal Server Configuration Console as sound redirection to terminals is turned off by default.
- Open the Terminal Services Configuration (Start> Program Files> Administrative Tools> Terminal Services Configuration), highlight Connections on the left and double-click on RDP-tcp on the right to launch the RDP-tcp Properties page.
- Select the Client Settings tab and unselect Audio Mapping to allow sound to be redirected to the terminal.
- Any users will need to log out and login to apply the change.
- Make sure that you are using a model of ThinManager Ready thin client that has sound capability.
- Use the Sound Module for that specific thin client. Sound modules are added on the Modules page of the Terminal Configuration Wizard. The sound modules have Sound in Session and Terminal Effects set to Enabled by default.
- Connect a powered speaker to the "Line Out" plug. Line Out isn't amplified so it requires a powered speaker, like the once normally used with PCs.
- The ThinManager Ready thin client will play a “ta da” sound when it boots to show that sound from the thin client is working. The thin client will normally play the standard Microsoft Sounds when it first starts a session on the terminal server unless it has been turned off in a group policy. It will not play the sound when it reconnects to an existing session.
If the terminal plays the “ta da” sound during the boot process then sound is enabled and working. If a sound doesn’t play in an application, check the settings in the application or for the session.