Home > OS >  [urgent] Windows Server 2003 local security policy secedit. SDB: a faulty extensibility
[urgent] Windows Server 2003 local security policy secedit. SDB: a faulty extensibility

Time:10-02


This problem, first from a client/server Shared clip cannot be accessed because start, then go to the server check related security policy configuration, found that, after the modification of one set is submitted to the errors,

In the online also baidu, then found the detected using the following command to repair, but to use
1, esentutl/k % windir % \ Security \ Database \ Secedit SDB and esentutl/g % windir % \ Security \ Database \ Secedit SDB to detect
But a run at the following error:

2, esentutl/p % windir % \ Security \ Database \ Secedit SDB repair
This is a mistake, at that time didn't come urgent screenshots, anyway, just can't according to the Internet to modify some of the methods, and the customer's system can't reshipment system, inside a lot of things, and their internal ERP data can't heavy

CodePudding user response:

To the top! ~ ~ ~ ~ ~ ~

CodePudding user response:

Found a new method of generating security database, consider, depends on you how many set

1. Open the % SystemRoot % \ Security folder, create a new folder, and then name it "OldSecurity".

2. Move all of the files ending in the log from the % SystemRoot % \ Security folder to the OldSecurity folder.

3. Find the Secedit. SDB file in the % SystemRoot % \ Security \ Database folder, and then rename this file to "Secedit. Old".

4. Click Start, Click Run, type MMC, and then Click OK.

5. Click the Console, Click the Add/Remove the Snap - in, and then Add the Security and the Configuration Snap - in.

6. Right - click the Security and the Configuration and Analysis, and then click the Open Database.

7. Browse to the % SystemRoot % \ Security \ Database folder, type Secedit. SDB in the File name box, and then click Open.

8. When you are prompted to import a template, click the Setup Security. Inf, and then click Open.
  • Related