Security Compliance
Import archived Windows event logs into SEM
Learn how to import Windows event logs into Security Event Manager (SEM). You may want to complete this process on an unused/new system or blank VM as importing can affect the Security log.
First published date
Last published date
Product section
Resolution
Note:
It is recommended that you perform the following steps on an unused system or a blank VM as these could affect the Security log on the system where they are taken from.
To import archived Windows event logs:
- On a blank system or VM, set the Windows Event Log service to start manually.
- Click Start, Open CMD, and then run services.msc.
- From the Services pane, scroll to and right-click Windows Event Log > Properties.
- In the Startup type drop down box, select Manual, and then click OK.
- Reboot the system to allow your changes to be applied.
- Stop the SEM Agent.
- Click Start, open CMD, and then run services.msc.
- From the Services pane, scroll to and right-click SolarWinds Security Event Manager Agent > Stop.
- Stop the Windows Event Log service
- Click Start, open CMD, and then run services.msc.
- From the Services pane, scroll to and right-click Windows Event Log > Stop.
- Copy the .evtx file and paste it to C:\Windows\System32\winevt\Logs.
- Rename the .evtx file to
Note: Rename first any existing
- In Windows Explorer, go to C:\Windows\System32\winevt\Logs.
- Select the archived file, and rename it to Security.evtx.
- Adjust readerState.xml.
Note: 0 means to start at the beginning of the Event log.
- Go to C:\Windows\SysWOW64\ContegoSPOP\tools.
- Change readerState.xml to logStartPoint=”0”.
- Change description to .
- Restart the Windows Event Log service.
- Click Start, open CMD, and then run services.msc.
- From the Services pane, scroll to and right-click Windows Event Log > Start the Service.
- Restart the LEM Agent.
- Click Start, open CMD, and then run services.msc.
- From the Services pane, scroll to and right-click SolarWinds Security Event Manager Agent > Start the Service.
The SEM Agent, if it has a connector that can read the Windows Security log, should be able to parse through the copied Event logs. These parsed logs have the DetectionTime in SEM matching the time the logs were initially generated.