Export
Secedit can be used to export a configuration from a security database to a security template. This allows the security template to be used on other computers. The command to do this is
secedit /export [/MergedPolicy] [/DB filename] [/CFG filename]
[/areas area1 area2...] [/log filename] [/verbose] [/quiet]
The following parameters may be provided:
- /MergedPolicy This specifies that secedit should export both the domain and local policies.
- /DB filename This specifies the path to the database file that contains the stored configuration to be exported.
- /CFG filename This specifies the path where the security template is to be saved.
- /areas This specifies the security areas of the template to be exported. The areas may be: Securitypolicy, Group_mgmt, User_rights, Regkeys, Filestore, Services. If no areas are specified, the default is all areas.
- /log filename This specifies the path to the log file for the command.
- /verbose This tells secedit to provide details while running.
- /quiet This tells secedit not to provide output to the screen while running.
The output of this command could be used with other commands to make sure the same policy is in place across an entire domain.
In this tutorial:
- Windows 2000 Security Issues
- Setting up the System
- Local Security Policy Settings
- Logon Message
- LAN Manager Authentication Level
- System Configuration
- File Systems
- Network
- Account Settings
- USER MANAGEMENT
- Setting File Permissions
- System Management
- Analysis
- Configuration
- Validation
- Export
- Auditing a System
- Log Files
- Looking for Suspicious Signs
- Missing Log Files or Gaps in the Log Files
- Unknown Processes