Phew J From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Eric Fleischman Oh, so basically, my read on levels
confirms what Kevin posted. J ~Eric From: Eric Fleischman I’d answer this question two ways: 1) Our general answer to this for all of the ntds diagnostics logging
values is “none”, “a bit”, “a good amt”,
“a lot”, “a whole lot”, “yowsers” J 2) Field engineering is a bit easier, just because it is not weaved in
so many places in the code. So basically, use sev_internal for field
engineering. J ~Eric From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Sullivan I saw an article showing what you would
get if set to 4 or 5 but not specifically 3. I always look at those levels as superfluous.
If I need to get info I crank it up get what I need and crank it back down. I
guess if you have to leave it running for a while 3 would be an option. ·
DS_EVENT_SEV_VERBOSE ·
DS_EVENT_SEV_INTERNAL From http://msdn.microsoft.com/library/default.asp?url="">.
Kevin From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Isenhour, Joseph Hello,
Has
anyone out there found a book or a web site that contains a comprehensive list
of what each of the NTDS debug levels will show you. I'd like to know
what information will be revealed if Field Engineering is set to 3 for example. |
Title: NTDS Diagnostics