-
733 items
13 item
9 item
235 item
211 item
169 item
11 item
88 item
1 item - For developers
This Connector allows you to connect to Microsoft Windows event sources using the WMI protocol and collect generated events.
Suggested for you are based on app category, product compatibility, popularity, rating and newness. Some apps may not show based on entitlements. Learn more about entitlements.
Consider this as the latest release
updated with OT rebranding
2020.1r1
Mar 2020:
Oct 2018:
2018.1r1
New Certified Platform
Software Fixes
Sentinel Does Not Receive Events After Windows Update on an Event Source
Issue: After the Windows update on an Event Source, WECS stops sending events to Sentinel until you restart the Event Source in Sentinel Control Centre. After the Windows update, sometimes the Event Source may not be responsive and WECS keeps trying to communicate with the event source. (Bug 1035423)
Fix: WECS now attempts to connect to the event source for the specified number of times. If the event source is still not responsive, WECS disconnects the existing connection to the event source and creates a new connection. You can specify the number of times WECS should attempt to connect to the event source by configuring the noOfRetry parameter in the eventManagement.config file. For more information, see “Configuration Options” on page 52.
The WECS Agent Does Not Communicate if TLSv1.0 is Disabled
In non-FIPS mode, the WECS Agent now communicates seamlessly if TLSv1.0 is disabled. Therefore, it works with TLSv1.1 and TLSv1.2. (Bug 937554)
To ensure communication in FIPS mode, follow the workaround mentioned in section Communication Issues Between the Connector and WECS When Sentinel in FIPS Mode in the Known Issues section.
Please upgrade to one of the following broswers: Internet Explorer 11 (or greater) or the latest version of Chrome or Firefox
