There is a GPO
setting (never tried it) located here: \Computer Configuration\Administrative
Templates\System\Net Logon\Maximum Log File Size
explained by GPO setting:
maximum size in bytes of the log file netlogon.log in the directory
%windir%\debug when logging is enabled.
the maximum size of the log file is 20MB. If this policy is enabled, the
maximum size of the log file is set to the specified size. Once this size
is reached the log file is saved to netlogon.bak and netlogon.log is truncated.
A reasonable value based on available storage should be specified.
If this policy
is disabled or not configured, the default behavior occurs as indicated above.
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eric Fleischman
Turn logging down to 0.
I would note that there is no notion of
log generations, so your worst case here is 2* log size (where log size
defaults to 10MB), so worst case it should only be 20MB, and deleting the archive
is of course trivial.
More generally, we do reserve the right to
write to this log & recreate it as needed as sometimes there are things we
need to log so you can figure out what went wrong should something turn south.
So even a log level of 0 does not guarantee no logging, it just means
“not much logging” you could say.
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rimmerman, Russ
I just did a netlogon AD site cleanup
process and want to delete all netlogon.logs from all DCs in our domain.
I noticed you can't delete it while the netlogon service is running. Is
there a better way to keep these netlogon file sizes down, or delete them
regularly than to stop, delete, and restart services on each?