|
Posted by Steven L Umbach on July 9, 2006, 5:51 pm
Please log in for more thread options It sounds like some process using secedit in a batch file referencing a
security template may be making the change. I would check to see if any
Scheduled Task or AT command is configured to run at that time or possibly
a Group Policy startup script if the computer was started up at 8:00
. --- Steve
> Hello everybody,
>
> I've got a new Windows Server 2003 R2 set up. The Audit Policy is set to
> enable successful and failed logons. These settings are applied by me but
> after some time, i.e. 8 AM the next morning the server logs the following
> policy change.
>
> Event ID: 612
> User: NT AUTHORITY\SYSTEM
> Audit Policy Change:
> New Policy:
> Success Failure
> - - Logon/Logoff
> - - Object Access
> - - Privilege Use
> - - Account Management
> - - Policy Change
> - + System
> - - Detailed Tracking
> - - Directory Service Access
> - - Account Logon
> Changed By:
> User Name: ARWEN$
> Domain Name: WG
> Logon ID: (0x0,0x3E7)
>
> This basically means that my previously applied Logon/Logoff audit was
> turned off. I'm not sure which process triggered the update, it seems to
> come from a system process as the User Name ARWEN$ (the server name)
> suggests.
>
> The server is a standalone server, AD is not installed. Does anyone know
> why
> this happens and how I could fix the wrong policy update?
>
> Best regards,
>
> Alex
> --
> _______________________________________
>
> Alexander Groß
> Dipl.-Ing. (BA) für Informationstechnik
> PLEASEAlexanderGrossREMOVETHIS@gmx.de
> http://www.it99.org/axl/
> ICQ# 36765668
> _______________________________________
>
>
|