Faizan Siddiuqi 1 Posted August 29, 2022 Posted August 29, 2022 Hi, why its showing USB drive letter in logged user instead of user name?
Administrators Marcos 5,741 Posted August 29, 2022 Administrators Posted August 29, 2022 What kind of report did you generate?
Faizan Siddiuqi 1 Posted August 29, 2022 Author Posted August 29, 2022 Its not a report. Its email notification.
Administrators Marcos 5,741 Posted August 29, 2022 Administrators Posted August 29, 2022 Do you mean the notification "Malicious file detected (trojan / worm / virus / application)" ? If so, what version of ESET PROTECT do you use? On your system the term "threat" is used, however, this changed to "detection" quite a long time ago and the current template looks like as follows: Detection type: ${detection_type} Detection name: ${detection_name} Computer name: ${computer_name} Computer static group hierarchy: ${computer_sg_hierarchy} Logged user: ${user} Time of occurrence: ${timestamp} Scanner: ${scanner} Action performed: ${action_performed} Please copy and paste your template.
Faizan Siddiuqi 1 Posted August 29, 2022 Author Posted August 29, 2022 ESET PROTECT VERSION 9.0 Eset endpoint version is 9.0.2046.0 problem is only with incorrect logged user, please see in photo i pasted above Logged user: D:\ its USB drive. And my question is why its showing USB drive in logged user instead of user name who logged in on the system.
Administrators Marcos 5,741 Posted August 29, 2022 Administrators Posted August 29, 2022 Please copy and paste the notification template as shown above.
Faizan Siddiuqi 1 Posted August 29, 2022 Author Posted August 29, 2022 Ok. I wil. Please confirm if this is belong to below point marked in red
Administrators Marcos 5,741 Posted August 30, 2022 Administrators Posted August 30, 2022 Has upgrading to the latest Endpoint 9.1.2057 resolved the issue?
Faizan Siddiqui 0 Posted August 30, 2022 Posted August 30, 2022 We haven't done an upgrade yet, I'm asking you if it has anything to do with that.
Administrators Marcos 5,741 Posted August 30, 2022 Administrators Posted August 30, 2022 I don't know for sure if it would resolve the issue, hence I've asked you to try to upgrade Endpoint to the latest v9.1.2057 and see.
Recommended Posts