Has anyone successfully configured Microsoft Exchange Message Tracking as a data source as shown here: https://community.mcafee.com/thread/52745
After I configure the data source, I try to test the connection, and receive the following error:
I currently collect Message Tracking logs via CIFS without issues. I would double check that you have the proper permissions where the logs are located. The account will need write access even if you don't plan to delete the logs after processing. I believe the Remote Registry service also needs to be running.
I would tail the messages file on the receiver when running the test connect. It could provide more details about where the issue is. Also I know there was a reported issue that was fixed in mr7 "1015740 - Connection test failing when connection test tries to use /ss1/usr/local/elm/tmp for tmp directory on receiver".
Hope this helps.
Thanks Wizard. I did everything you suggested, but I'm still receiving the NotOk \n error. Below is the result of the tailing the messages:
BTW, I'm on 9.5.0 MR2.
The account has full access, and I'm still receiving the error. Support says based on the logs I sent them, the account is locked out, but I have verified that it's not, and the issue does not happen on other data sources that are associated with the account. I have also verified that my personal account has full access to the share, and when I use it as the username, I receive the same error.
Could you pls try below command and inform us:
First login of your ERC via ssh
#perl /usr/local/bin/wmitest.pl -i '10.10.10.10' -H 'Server_Name' -u 'domain\user' -p 'password'
if everything's ok then output:
NotOk Access denied. The user may not have permissions to access the DCOM interface or the provided credentials are incorrect.
Also note, that I can gather Widows security logs from the server via WMI using that same account without issue. I only have the problem trying to connect and pull the Exchange Messaging logs.
As you know ESM is a Linux based system and sometimes it can be such this file sharing problem especially with NTFS on Windows. Therefore McAfee released a windows base application called McAfee SIEM Collector Utility. I recommned that you use this application for these types of windows files for log collect.
I do use this tool for dome other Windows data sources, but the tool is installed on a "jump server" and the data sources send the files to the jump server, then Nitro picks them up from there. Can I use this tool without using a jump server?
Download the new ePolicy Orchestrator (ePO) Support Center Extension which simplifies ePO management and provides support resources directly in the console. Learn more about ePO Support Center