Re: How to apply local auditing through secedit

From: Nick Finco [MS] (nfinco@online.microsoft.com)
Date: 03/28/03 

From: "Nick Finco [MS]" <nfinco@online.microsoft.com>
Date: Thu, 27 Mar 2003 17:58:21 -0800

On Win2k, the Local Security Policy snapin is a local policy store for those
settings. It does not reflect the current system state. Your configuration
of those settings via secedit is working properly because the analysis
feature isn't showing mismatches. As long as the domain policy and the
local policy (viewed in the snapin) isn't forcing those settings to a
particular value, your script will configure the values properly.

N 

-- 
This posting is provided "AS IS" with no warranties, and confers no rights.
"Paul" <plangton@start.com.au> wrote in message
news:b37306f8.0303271738.3f620ed4@posting.google.com...
> Hi All,
>
> I am trying to create a script that will apply local auditing on
> events on our PC's as part of a build process. I am attempting to use
> the secedit command, which I must say, has to be the most confusingly
> documented command I have come across yet. I have created an SDB file
> where I have set two local auditing options. I then went into the
> local security snap in, turned it off, then attempted to set it back
> via secedit - it says it completed successfully but no luck, when I go
> back into the local security settings it isn't applied. WHen I do an
> analysis of the computer against this sdb however, it says it is. I am
> doing something wrong along the way obviously, does anyone have any
> idea what? I am at the point of writing a script that manually creates
> these setting by opening windows and clicking on buttons - any secedit
> experts out there???
>
> The secedit command line I am running is as follows:
>
> secedit /configure /db secedit.sdb
>
> and I am running it from the directory that contains my customised sdb
> file.
Quantcast