Re: Sound tansfered to Client after SP1 installed

  • Thread starter Thread starter Donald M
  • Start date Start date
D

Donald M

Guest
Re: Sound tansfered to Client after SP1 installed

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@discussions.microsoft.com> 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@discussions.microsoft.com> 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@discussions.microsoft.com>
> >> >> 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!

>
 
Re: Sound tansfered to Client after SP1 installed

Re: Sound tansfered to Client after SP1 installed

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@discussions.microsoft.com> 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@discussions.microsoft.com> 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@discussions.microsoft.com> 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@discussions.microsoft.com>
>> >> >> 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!
 
Re: Sound tansfered to Client after SP1 installed

Re: Sound tansfered to Client after SP1 installed

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@discussions.microsoft.com> 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@discussions.microsoft.com> 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@discussions.microsoft.com> 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@discussions.microsoft.com>
> >> >> >> 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!

>
 
Re: Sound tansfered to Client after SP1 installed

Re: Sound tansfered to Client after SP1 installed

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@discussions.microsoft.com> 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@discussions.microsoft.com>
>> 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@discussions.microsoft.com> 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@discussions.microsoft.com> 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@discussions.microsoft.com> 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!
 
Re: Sound tansfered to Client after SP1 installed

Re: Sound tansfered to Client after SP1 installed

Thank you; however I have tried that and it too did not work. What's
interesting is it references this problem being corrected in SP2, which is
what I have installed. Curiouser and curiouser.
--
Thank you, Christina


"Vera Noest [MVP]" wrote:

> 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@discussions.microsoft.com> 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@discussions.microsoft.com>
> >> 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@discussions.microsoft.com> 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@discussions.microsoft.com> 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@discussions.microsoft.com> 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!

>
 
Re: Sound tansfered to Client after SP1 installed

Re: Sound tansfered to Client after SP1 installed

Yes, that's really strange. I have no idea how to solve it, I'd call
Microsoft support.

_________________________________________________________
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=?=
<ChristinaColeman@discussions.microsoft.com> wrote on 22 feb 2008
in microsoft.public.windows.terminal_services:

> Thank you; however I have tried that and it too did not work.
> What's interesting is it references this problem being corrected
> in SP2, which is what I have installed. Curiouser and
> curiouser.
 
Re: Sound tansfered to Client after SP1 installed

Re: Sound tansfered to Client after SP1 installed

HAving same beep problem in a windows 2008 TS server. anyone found the real
fix yet? the reg settings have not worked. Hotfix wont apply as it is a 2008
server. HELP!

"Vera Noest [MVP]" wrote:

> Yes, that's really strange. I have no idea how to solve it, I'd call
> Microsoft support.
>
> _________________________________________________________
> 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=?=
> <ChristinaColeman@discussions.microsoft.com> wrote on 22 feb 2008
> in microsoft.public.windows.terminal_services:
>
> > Thank you; however I have tried that and it too did not work.
> > What's interesting is it references this problem being corrected
> > in SP2, which is what I have installed. Curiouser and
> > curiouser.

>
 
Re: Sound tansfered to Client after SP1 installed

Re: Sound tansfered to Client after SP1 installed

I never did find anything and ended up having all users disable on their base
workstations as follows:

Click on Start
Right click my computer
Properties
Hardware
Device manager
View
Show hidden devices
Expand non plug and play drivers
Double click on ‘BEEP’
On General Tab click ‘device usage’ drop down arrow and change to ‘disable’
Click on Driver Tab
Click STOP
Click ok

Reboot if prompted

-That's all I got!
Thank you, Christina


"Chris" wrote:

> HAving same beep problem in a windows 2008 TS server. anyone found the real
> fix yet? the reg settings have not worked. Hotfix wont apply as it is a 2008
> server. HELP!
>
> "Vera Noest [MVP]" wrote:
>
> > Yes, that's really strange. I have no idea how to solve it, I'd call
> > Microsoft support.
> >
> > _________________________________________________________
> > 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=?=
> > <ChristinaColeman@discussions.microsoft.com> wrote on 22 feb 2008
> > in microsoft.public.windows.terminal_services:
> >
> > > Thank you; however I have tried that and it too did not work.
> > > What's interesting is it references this problem being corrected
> > > in SP2, which is what I have installed. Curiouser and
> > > curiouser.

> >
 

Similar threads

Back
Top