Article ID: 889532
Article Last Modified on 7/20/2005
APPLIES TO
- Microsoft Windows XP Professional
- Microsoft Windows XP Service Pack 1a
- Microsoft Windows XP Professional
- Microsoft Windows XP Professional
- Microsoft Windows XP Home Edition
- Microsoft Windows XP Service Pack 1a
- Microsoft Windows XP Home Edition
- Microsoft Windows XP Home Edition
SYMPTOMS
When you try to export local security policy settings in Microsoft Windows XP by using the Secedit.exe command-line utility, the security policy settings do not export. For example, if you type SecEdit /export /cfg c:\cfg.txt, the Cfg.txt file does not contain the information that you want to export.
CAUSE
This problem occurs because of a design change in the Windows XP architecture. In Microsoft Windows 2000, the security policy settings are stored in the Secedit.sdb database before the settings are applied. Windows XP does not store the security policy settings in the Secedit.sdb database. Therefore, when you run the SecEdit.exe utility in Windows XP, the utility does not find security policy settings in the Secedit.sdb database.
RESOLUTION
To resolve this problem, install the hotfix that is available in the following MIcrosoft Knowledge Base article:
897327 You cannot use the Secedit.exe command-line tool to export the local security policy settings on a stand-alone workstation that is running Microsoft Windows XP
This hotfix contains an updated version of the Secedit.exe utility that can export the local security policy settings on a Windows XP-based computer.
WORKAROUND
To work around this problem, manually export and then save the Security Options list from the Local Security Settings snap-in. To do this, follow these steps:
- In Control Panel, double-click Administrative Tools, and then double-click Local Security Policy.
- In the left pane, expand Local Policies, and then click Security Options.
- On the Action menu, click Export List.
- In the Save in box, specify the location where you want to save the text file.
- In the File name box, type a name for the text file, and then click Save.
- On the File menu, click Exit to close Local Security Settings.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
For more information about how to use Secedit.sdb database to perform security analysis of your computer, click the following article numbers to view the articles in the Microsoft Knowledge Base:
816119 How to use the Secedit.sdb database to perform a security analysis in Windows Server 2003
318711 How to use the Secedit.sdb database to perform a security analysis in Windows 2000
Keywords: kbtshoot KB889532
