Well, here's a reason not to install ISA2K4/SP2: It will create a new 400mb
file, Windir\Debug\ISALOG.BIN, and a second, new 400mb file, ISALOG.BAK, on
the C: drive. According to my admittedly superficial reading of the technote
(google ISALOG.BIN), this file's purpose is for troubleshooting by MSSupport
in the event of problems with ISA 2004.
You can get rid of this by going to HKLM/Software/Microsoft/ISATracing and
setting the BootTracing parameter to 0. Then reboot and delete both
ISALOG.BIN and ISALOG.BAK.
The technote further says that you can prevent the creation of these files
by adding the reg key and value before installing SP2.
Below is the relevant info from the technote:
Nearly one gig of space taken up on crowded C: drives JUST IN CASE
MSSupport wants to look at the log file. Someone at MSSupport has lost his
mind.
GaryK
http://www.microsoft.com/technet/prodtechnol/isa/2004/plan/sp2.mspx
(search page for ISALOG.BIN)
Tracing
Service Pack 2 includes an error-level tracing mechanism that operates
continually in the background. If necessary, the tracing information is
available for Microsoft Product Support Services. The tracing mechanism does
not collect personally identifiable information.
Tracing takes place in the background, and has a negligible affect on ISA
Server performance. A 400 megabyte (MB) file (%windir%\debug\isalog.bin) is
created by Service Pack 2 on each computer running ISA Server services, to
contain the tracing information.
We recommend that you use the default settings for this feature. However, if
you want to modify the tracing mechanism, you can do so through the registry
key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ISATrace. To change the size of
the file used by tracing, change the value of CircularlLogSizeMB. To disable
tracing, change the BootTracing value to 0. This does not delete the file,
which has to be deleted manually. After registry changes, restart the
computer so that the changes take effect. If you create the registry key
before installing Service Pack 2, and set the BootTracing value to 0, the
tracing file will not be added during the installation, and tracing will not
be enabled.
GaryK
"Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]" <sbra...@pacbell.net>
wrote in message news:O4ZtsknK...@TK2MSFTNGP15.phx.gbl...
HKLM/Software/Microsoft/ISATracing
Value name == AlternateTracingFile
Value type == String Value
Value data == FullPathToTracingFile.bin
1.a. Add the following registry value under
HKLM/Software/Microsoft/ISATracing
Value name == UseAlternateTracingFile
Value type == DWORD Value
Value data == FFFFFFFF (hex)
2. From a cmd window, type:
logman stop isa -etw & logman start isa –etw
Apparently there's a way to redirect it?
Missed that. Thanks. Can't see why you'd want to redirect it. That's a lot
of space to waste on the very slim chance that some day MSSupport might want
to look at it.
GaryK
"Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]" <sbra...@pacbell.net>
wrote in message news:%23yfP%23FoKG...@TK2MSFTNGP15.phx.gbl...
--
Russ Grover
Small Business IT Support
SBS Rocks!
Portland/Beaverton OR
Email: Sales at SBITS.Biz
Website: http://www.SBITS.Biz
"Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]" <sbra...@pacbell.net>
wrote in message news:e7X8fBpK...@TK2MSFTNGP11.phx.gbl...
"Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]" <sbra...@pacbell.net>
wrote in message news:%23yfP%23FoKG...@TK2MSFTNGP15.phx.gbl...
"Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]" <sbra...@pacbell.net>
wrote in message news:%23yfP%23FoKG...@TK2MSFTNGP15.phx.gbl...