What is correct way to create secedit.sdb file?

[Guest]

A couple weeks ago I re-created my secedit.sdb file on Windows 2000
Pro workstation by exporting the security policy to a .inf file from
the secpol.msc console, editing the .inf file to suit my needs,
deleting the secedit.sdb file, and then importing the .inf file from
the secpol.msc console (which re-created the secedit.sdb file).

But there seems to be a lot of varying information out there about how
to re-create secedit.sdb, and I want to make sure that I didn't miss
something that might cause subtle problems.

Some sources say that before re-creating secedit.sdb, you need to
delete all of the files directly under c:\winnt\security in addition
to deleting the c:\winnt\security\database\secedit.sdb file.

Other sources say that you need to delete all of the files in c:\winnt
\security\logs in addition to deleting secedit.sdb.

Some sources also say that you should reboot the computer after
deleting secedit.sdb.

So do I need to delete any files (besides secedit.sdb) and/or reboot
the computer before re-creating secedit.sdb?

 

[Hayman Ezzeldin]

Dear NoSpam
According to the Microsoft Article
1- Don't delete the file, just rename it to "secedit.old" instead of
"secedit.sdb"
2- Start - Run - CMD
3- At the command prompt type "secedit /refreshpolicy machine_policy
/enforce" because you have Windows 2000, but without the Quotation Marks.
This should recreate the secedit.sdb file.

Best regards

 

[Guest]

Dear NoSpam
According to the Microsoft Article
1- Don't delete the file, just rename it to "secedit.old" instead of
"secedit.sdb"
2- Start - Run - CMD
3- At the command prompt type "secedit /refreshpolicy machine_policy
/enforce" because you have Windows 2000, but without the Quotation Marks.
This should recreate the secedit.sdb file.

That method actually didn't work for me.