JSI Tip 7140. After applying SP4 to Windows 2000, values in your Local Security Policy revert to the values that are stored in the Secedit.sdb file?

The subject behavior occurs when SP4 applies the Local Security Policy Database (%SystemRoot%\Security\Database\Secedit.sdb) as it adds the Impersonate a client after authentication and Create global objects user rights.

To resolve this problem:

1. Control Panel / Administrative Tools / Local Security Policy.

2. Expand Local Policies in the left-hand pane.

3. Expand Security Options in the left-hand pane.

4. Double-click any one policy in the right-hand pane.

5. Immediately press OK. This action causes the values stored in the registry to update the %SystemRoot%\Security\Database\Secedit.sdb file.

6. Close the Local Security Settings Window.



Hide comments

Comments

  • Allowed HTML tags: <em> <strong> <blockquote> <br> <p>

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.
Publish