Re: Disabling CTFMON.EXE on WIN2K3 Terminal Server Cluster.

From: Guy Leech (_at_))
Date: 08/19/04 

Date: Thu, 19 Aug 2004 08:45:24 +0100

I took permissions off it for all but system and administrators to achieve
the same effect and using this method you won't potentially hit Windows File
Protection putting the file back in an effort to "help" you.

Regards,

Guy

"Cláudio Rodrigues" <Claudio.Rodrigues@NOSPAM-Terminal-Services.NET> wrote
in message news:#XXY2ObhEHA.2908@TK2MSFTNGP10.phx.gbl...
> I simply rename CTFMON.EXE to CTFMON.OLD. That works and I do not need to
go
> through all the crap listed on the KB. :-)
>
> --
> Cláudio Rodrigues
>
> Microsoft MVP
> Windows Technologies - Terminal Services
> http://www.terminal-services.net
> "Geoffc" <Geoffc@discussions.microsoft.com> wrote in message
> news:F70F17C5-566B-4B4A-9337-625A839583F0@microsoft.com...
> > Thanks Alex
> >
> > As per the KB 313176, I have already ticked the 'Turn off advanced text
> > services' check box. No Luck!
> >
> > The last reply didnt have a link to the CTFMON.exe kill app.
> >
> > Could you please post the link again.
> > I would still prefer to identify why the original 'fix' worked on one
> > server, but not on it's identical partner.
> >
> >
> > Geoff Craig
> >
> >
> > "Alex K. Angelopoulos [MVP]" wrote:
> >
> >> Geoffc wrote:
> >> > As noted in the MS KB Article below, I have attempted to disable an
> >> > instance of CTFMON.EXE from running for every client that connects to
> >> > our TS Cluster.
> >> >
> >> > http://support.microsoft.com/default.aspx?scid=kb;EN-US;q282599
> >> >
> >> > This has worked for 1 of the servers, but not the other.
> >> >
> >> > Any suggestions on what MAY be wrong would be appreciated.
> >>
> >> You may also want to check the information here:
> >> http://support.microsoft.com/?kbid=313176
> >> for additional steps to take.
> >>
> >> An alternative hack I have used for checking on ctfmon instances and
> >> killing
> >> them is to run an application that requests notification via WMI of
> >> ctfmon.exe creation events and then kills the instances. Attached is an
> >> HTML
> >> Application that does precisely this; rename ctfmonkill.hta.txt to
> >> ctfmonkill.hta, then run it in a session that has administrative
> >> privileges
> >> on the Terminal Server. It will automatically see and kill all ctfmon
> >> instances within 10 seconds of their launch, and will log the event to
> >> its
> >> display window
>
>