Finally got this working, there are two ways to centralise logs with the two subscription types:
- Collector Initiated - The collector computer contacts the selected source computers
- Source computer initiated - source computers in the selected groups are configured via a GPO to send data to the collector.
I agree if you opt for option 2 then only future event IDs will be forwarded and event ID 111 is acceptable, however if you want historic event logs forwarding then you need to configure option 1. In my case i only wanted SMBAudit logs and for this to work I have to give specific permissions to the audit log by running the following command on the source servers. This grants the Event log Readers group Network services access.
wevtutil set-log Microsoft-Windows-SMBServer/Audit /ca:O:BAG:SYD:(A;;0x5;;;BA)(A;;0x1;;;S-1-5-32-573)(A;;0x1;;;S-1-5-20)
You must run the command on the source servers before configuring the subscription, otherwise you will need to deselect the event log in the subscription and then reselect.
I then wanted to export specific information from the event log into a CSV file, i created the following script:
Add-Content -Value “computername,server,TimeCreated” -Path c:SMBv1.csv
$Events = Get-WinEvent -LogName ForwardedEvents
# Parse out the event message data
ForEach ($Event in $Events) {
# Convert the event to XML
[xml]$xmlEvent = $event.ToXml()
$computername = $xmlevent.Event.EventData.Data.'#text'
$server = $Event.MachineName
$TimeCreated = $Event.TimeCreated
Add-Content -Value “$computername,$server,$TimeCreated” -Path c:SMBv1.csv
}
Hope this helps others trying to achieve this.