Re: Sound tansfered to Client after SP1 installed
- From: "Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 21 Feb 2008 12:38:49 -0800
You can disable the MessageBeep function. That's documented in the
article for hotfix 901115, under More Information.
901115 - A Terminal Services client computer may make
beep sounds after you connect to a Windows Server 2003
Service Pack 1-based computer
http://support.microsoft.com/?kbid=901115
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
=?Utf-8?B?Q2hyaXN0aW5hIENvbGVtYW4=?= <Christina
Coleman@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 21 feb 2008 in
microsoft.public.windows.terminal_services:
Vera: hopefully you can help on this as well. I have installed.
SP2, and now my beep is back. I experienced the system beeps
after SP1, obtained the hotifx and applied it, which resolved
the issue. now after SP2, the system beeps are back. I tried
running the hotifx again for grins, and a message appears "Setup
has detected that the Service Pak version of this system is
newer than the update you are applying. There is no need to
install this update". Any ideas??? Thanks in advance.
Christina
"Vera Noest [MVP]" wrote:
Check my very first reply in this thread for the KB article
that identifies the hotfix.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
=?Utf-8?B?RG9uYWxkIE0=?= <DonaldM@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote on 08 okt 2007 in
microsoft.public.windows.terminal_services:
Do you have the hotfix number? I noticed SP2 is out that
includes this fix but due to other reasons I can not apply
SP2.
thanks,
Don
"Vera Noest [MVP]" wrote:
You can disable audio redirection, but I'm not sure if that
applies to system beeps as well.
Anyway, I run the hotfix on a number of servers, without any
problems.
But of course, that's no guarantee that it will behave
identical on yours. Like anything else, you'll have to test
it.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
SQL troubleshooting: http://sql.veranoest.net
___ please respond in newsgroup, NOT by private email ___
"=?Utf-8?B?dGVlbnpidXRsZXI=?="
<teenzbutler@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 02 feb 2006
in microsoft.public.windows.terminal_services:
Thanks for getting back to me Vera. I was just
reiterating Patrick Rouse's recommendation in respone to
jeutix:
"This can be disabled via tscc.msc or group policy."
His response was some what vague. So, do you know if this
feature can be disabled through use of a group policy? If
not, do you know if there are any adverse affects as a
result of the hotfix?
"Vera Noest [MVP]" wrote:
That's hotfixes in a nut shell :-)
There isn't any setting in tscc or GPO about system
beeps. That's why a hotfix was needed. Or do I
misunderstand what you want to accomplish?
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
SQL troubleshooting: http://sql.veranoest.net
___ please respond in newsgroup, NOT by private email ___
"=?Utf-8?B?dGVlbnpidXRsZXI=?="
<teenzbutler@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 02 feb
2006 in microsoft.public.windows.terminal_services:
I am also experiencing the beeping. I contacted
Microsoft to retrieve the hot fix. However, they
informed me the hot fixed has not gone through
regression testing. So, it's basically at the users
own risk. I wanted to find out about the tscc.msc or
group policy methods. I accessed the tscc.msc but
couldn't find anything relating to this issue. I have
not worked with group policies before. Could someone
please advise as to what I need to look for in the
group policy.
Thanks.
"Vera Noest [MVP]" wrote:
Depends on what you mean with "sounds".
What has changed with SP1 is that system beeps are now
redirected to the clients. There is a hotfix to take
them away again.
This is fixed in SP1:
824952 - The Beep function does not generate a beep
sound in a Terminal Services session to a Windows
Server 2003-based computer
http://support.microsoft.com/?kbid=824952
Which made this post-SP1 hotfix necessary:
901115 - A Terminal Services client computer may make
beep sounds after you connect to a Windows Server 2003
Service Pack 1-based computer
http://support.microsoft.com/?kbid=901115
_______________________________________________________
__ Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email
___
=?Utf-8?B?amV1dGl4?=
<jeutix@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 18 nov
2005 in microsoft.public.windows.terminal_services:
Hi
I've installed the SP1 for server 2003 and after
that, users in TS-sessions get sound transfered to
their clients. This wasn't before SP1.
What has changed? I couldn't find anything :-(
Thanks for help in advance!
- Follow-Ups:
- Re: Sound tansfered to Client after SP1 installed
- From: Christina Coleman
- Re: Sound tansfered to Client after SP1 installed
- References:
- Re: Sound tansfered to Client after SP1 installed
- From: Christina Coleman
- Re: Sound tansfered to Client after SP1 installed
- Prev by Date: Remote desktop: Problems reconnecting to an existing session.
- Next by Date: Re: Remote desktop: Problems reconnecting to an existing session.
- Previous by thread: Re: Sound tansfered to Client after SP1 installed
- Next by thread: Re: Sound tansfered to Client after SP1 installed
- Index(es):
Relevant Pages
|
