Jose
"Logging of Security Events in disabled by default in XP"
I do not think you are right here. I have never made any changes when
reinstalling and the Security log has always been populated. I only use
Home Edition. The situation could be different with Professional, where
the Administrator can set Policy options.
--
Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
Poor choice of words based on assumption. I am not using Home, and
the OP didn't specify, so we have to guess.
The default installation of XP Pro has the Security Auditing Policies
set to No auditing. I thought I read once that it was just XP in
general now I read Pro and Home are different in this area.
XP Home has some default security policies enabled that "cannot be
administered". That is good to know.
In Pro, the mechanism is there and "enabled", but there is probably
nothing set up to audit to cause something to be written to the
Security log. In Pro this is through the secpol.msc snapin. The
closest equivalent in Home might be lusrmgr.msc which is not on a Pro
system.
If you are using Home and have stuff in your Security log, it would be
interesting to see what your security policies setting are for what
events to log. You can open the events and figure out what is being
audited and then check your policies. I can't do that here.
I can easily get way too much information in the log by choosing to
audit certain events, but just being us chickens here, I don't care.
Even running the Event Viewer to look a the log creates entries in the
Security log since it is an administrative tool!
Back to No auditing for me.
Jose