katbert 3 Posted February 21, 2019 Share Posted February 21, 2019 We have trial 1-month license for EDTD: ESET Dynamic Threat Defense for Endpoint Security + File Security ESET Dynamic Threat Defense for Mail Security We add license to EBA Account, activete some servers. I see EDTD license in ESMC Console (Computer - show details), and see EDTD settings in local GUI of File Security. If I manually submit files - I see message about successfully sended files. But I don't see submitted files in local GUI or ESMC console, as described here: https://help.eset.com/edtd/en-US/?manual_upload.html Local Sent files log is empty. Agent version is 7.0.577 and File Secuirity version is 7.0.12018 Link to comment Share on other sites More sharing options...
Administrators Marcos 5,085 Posted February 21, 2019 Administrators Share Posted February 21, 2019 Never heard about such issue and also manually submitted files are logged: I'd suggest temporarily enabling diagnostic logging verbosity, submitting a file manually and then checking the ESET event log for possible errors. Link to comment Share on other sites More sharing options...
ESET Staff MartinK 378 Posted February 21, 2019 ESET Staff Share Posted February 21, 2019 26 minutes ago, katbert said: If I manually submit files - I see message about successfully sended files. But I don't see submitted files in local GUI or ESMC console, as described here: Not sure, but maybe file is not actually submitted because it is already known, i.e. it was submitted previously - are you testing with some custom made file? Link to comment Share on other sites More sharing options...
katbert 3 Posted February 21, 2019 Author Share Posted February 21, 2019 Just now, MartinK said: Not sure, but maybe file is not actually submitted because it is already known, i.e. it was submitted previously - are you testing with some custom made file? Yes, with custom files. Link to comment Share on other sites More sharing options...
katbert 3 Posted February 21, 2019 Author Share Posted February 21, 2019 23 minutes ago, Marcos said: I'd suggest temporarily enabling diagnostic logging verbosity, submitting a file manually and then checking the ESET event log for possible errors. How to enable diagnostic logging? Link to comment Share on other sites More sharing options...
Administrators Marcos 5,085 Posted February 21, 2019 Administrators Share Posted February 21, 2019 Don't forget to change the verbosity back to informative then: Link to comment Share on other sites More sharing options...
katbert 3 Posted February 21, 2019 Author Share Posted February 21, 2019 This screen for Endpoint Security. How to enable diagnostics logging in File Security? Link to comment Share on other sites More sharing options...
Administrators Marcos 5,085 Posted February 21, 2019 Administrators Share Posted February 21, 2019 The advanced setup looks almost same, ie advanced setup -> Tools -> Log files as shown in the screen shot. Link to comment Share on other sites More sharing options...
katbert 3 Posted February 21, 2019 Author Share Posted February 21, 2019 File Security 7.0.12018 don't have log verbosity settings Link to comment Share on other sites More sharing options...
katbert 3 Posted February 21, 2019 Author Share Posted February 21, 2019 we found solution if Windows Server don't trust certificate of ts.eset.com - send files log is empty and no error logged after import Digicert and thatwe root certs - Eset can send files successfuly, and show all previuosly sent files this is a bug, I think Peter Randziak 1 Link to comment Share on other sites More sharing options...
Administrators Marcos 5,085 Posted February 21, 2019 Administrators Share Posted February 21, 2019 You are right. In EFSW, diagnostic logging can be enabled here: Link to comment Share on other sites More sharing options...
katbert 3 Posted February 21, 2019 Author Share Posted February 21, 2019 1 hour ago, Marcos said: You are right. In EFSW, diagnostic logging can be enabled here: Thanks for the explanation! And how about certificate issue from my previous post? Quote we found solution if Windows Server don't trust certificate of ts.eset.com - send files log is empty and no error logged after import Digicert and thatwe root certs - Eset can send files successfuly, and show all previuosly sent files this is a bug, I think Link to comment Share on other sites More sharing options...
Recommended Posts