Hello, I am hoping that someone has had some degree of success with
logging Microsoft Exchange 2016. Our messaging team is upgrading to 2016
and I need to ensure the system logs to the SIEM. I have not seen any
(good) or read anything that highlights...
I would like to know the best way to configure windows servers and add
them to NetWitness. The process I have right now (Windows Event
Forwarding) has its own set of issues and would like something more
native to NetWitness. However, manually running...
Yes, that is ok. Sorry for the delay. I was supposed to receive email
updates on this but apparently did not get this one. I can say WEF add
its own complexities too, in that when it forwards logs busier log
aggregating servers will cause the collect...
With your great help! I could not figure this out and had resorted to
Windows event collection which is a valid option, but not optimal. This
appears to be a fully automated process and leverages NW policy tooling
so we can receive alerts when/if a c...
Upon looking closer, I found the issue. The variable for $WinRMPort =
'5986' had a transposed value of $WinRMPort = '5896' This script works
like a charm. Thank you very much for the help!
Hello, Yes, I passed the parameters that are relevant to our
environment. I have the event sources configured for HTTPS and they do
work when I manually create in the NW GUI. The machine does have the
required cert from our CA. See previous images fo...
Hello Miha, I was able to get the scripts run and the event sources
added; however, when I use the API to add the machines I get the error
stating the event source is not configured for https and to validate
server. Then if I delete the test machine ...
