Troubleshooting
Problem
The issue might happen when a new WinCollect agent is installed without creating a log source. If a Microsoft® Windows® Security Event Log log source was created manually, and deployed, the events from the Windows server might not be associated with the newly manually created log source.
Symptom
If you manually create an MS Windows Security Event Log log source and deploy the log source, you might not see events being associated with this log source.
When examined, the events are going to an auto-detected log source, and you can see that there are two MS Windows Security Event Log log sources with the same Log Source Identifier.
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSBQAC","label":"IBM Security QRadar SIEM"},"ARM Category":[{"code":"a8m0z000000cwtwAAA","label":"WinCollect"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Was this topic helpful?
Document Information
Modified date:
10 November 2023
UID
ibm17070591