Bernard
Tue Oct 05 23:24:31 CDT 2004
a) I'm not sure what is 'debugging tools for windows', we are talking about
IISstate here.
you can read more info at www.iisfaq.com (find the iisstate) section
b) not much, it will just do a thread dump on the attached process
c) don't get you. whether you planning to use iisstate or not.
your server need to be patch up to date, virus free and etc.
--
Regards,
Bernard Cheah
http://www.tryiis.com/
http://support.microsoft.com/
http://www.msmvps.com/bernard/
"Manish" <mworli@yahoo.com> wrote in message
news:a879d5d.0410050518.5c7af68d@posting.google.com...
> mworli@yahoo.com (Manish) wrote in message
news:<a879d5d.0410041928.39ff398f@posting.google.com>...
> > Hi All,
> > I have read many posts on forums related to use of IISSTATE.
> > Recently we are faced with 100% CPU on our production web-servers IIS
> > 5.0 , win2k. I told my manager that we can install IISSTATE and
> > Debugging Tools for Windows on our production web servers to get the
> > root cause. But he is concerned about security issues (if any ) and
> > un-installing IISSTATE and Debugging tools cleanly after root cause
> > identification.
> > Can someone please tell me how do others handle this situation on
> > production web-servers or is some remote debugging possible.
> > If you can point me with some articles that would be great too.
> > Thanks in advance,
> > Manish
>
> How safe is to install "Debugging Tools for Windows" on production servers
?
> a) security wise b) performance wise c) later upgrade service-pack wise.