Peter Randziak
-
Posts
3,516 -
Joined
-
Last visited
-
Days Won
207
Posts posted by Peter Randziak
-
-
17 hours ago, RClegg said:
I think I figured it out; we are running "PROTECT", while you specified that this is for "Endpoint Security" and "Endpoint Antivirus". Is the Outlook Plugin the same for all three? What are the plans for deploying this to the PROTECT family?
The new Outlook plugin is present in both ESET Endpoint Security i.e. EES and ESET Endpoint Antivirus i.e. EEA.
The Endpoints 9.1 with the new Outlook plugin will be released later as standard products.
Peter
-
Hello @RClegg,
thank you for your positive feedback, hopefully it will resolve the sync issues for you.
If not, let us know for sure so we can check it.
Have you used a license with appropriate product tier?
I would try to activate it locally using the license key.
If that won't work, what error code have you received?
Peter
-
Hello @SalihGiray and @Christos Panagiotakis
I would recommend you to take part in https://forum.eset.com/topic/32193-eset-mail-security-for-linuxbsdsolaris-customer-research/ as the team responsible is looking forward to hear opinions of customers so you may directly influence the decision making...
Peter on behalf of the teams responsible
-
Hello @Luiz Coelho2
I would recommend you to take part in https://forum.eset.com/topic/32193-eset-mail-security-for-linuxbsdsolaris-customer-research/ as the team responsible is looking forward to hear opinions of customers so you may directly influence the decision making...
Peter on behalf of the teams responsible
-
Hello guys @Joshi, @ivoks, @Levi, @Mino
I would recommend you to take part in https://forum.eset.com/topic/32193-eset-mail-security-for-linuxbsdsolaris-customer-research/ as the team responsible is looking forward to hear opinions of customers so you may directly influence the decision making...
Peter on behalf of the teams responsible
-
Hello @eclipse79,
as the issue probably won't be easy to reproduce, I would recommend to enable the logging before the attempt for sure. So if you succeed (I hope you will 😉 ), we will have the logs for the dev team to check it.
On 3/21/2022 at 8:15 PM, Peter Randziak said:if any issues will arise, we will need the user to enable diagnostic logging of this component whenever needed (see screen below), run Outlook (or other email client), wait for the issue to demonstrate, quit Outlook and disable diagnostic logging to avoid extensive log-recording for a longer time. The resulting log will be stored under C:\ProgramData\ESET\ESET Security\Diagnostics\MailPlugins.etl
Peter
-
Hello @eclipse79
the EEA stands for ESET Endpoint Antivirus and EES for ESET Endpoint Security so I would recommend to install the product, you currently have.
If you have EEA and would like to try EES, let me know I can order you a business trial license for that.
Well I agree it might be not that easy to reproduce that... 😞
Peter
-
Hello @eclipse79,
can you please try and let us know how it behaves with the new ESET plugin for Outlook?
https://forum.eset.com/topic/31777-new-outlook-plugin-beta/
Peter
-
Hello @j-gray,
12 hours ago, j-gray said:Again, we do not see this with the latest connector and EEA V7.
I guess the V7 is a type and you meant V6, right? As based on the previous info it seems that the v.7 is causing the issues and v.6 is working without them, can you please confirm it?
Peter
-
Hello @j-gray,
one more thing
On 4/18/2022 at 5:32 PM, j-gray said:Failed to process a request to/from ESET Endpoint Security/Antivirus. RUN_LOOP_ERROR RUN_LOOP_TIMEOUT (2)"
This message is stemming probably from the network layer.
Is it persistent?
It might be also caused by the connector crashes...
Peter
-
The error "RUN_LOOP_ERROR RUN_LOOP_TIMEOUT " is known and should be fixed in the 1.9 release.
On 4/18/2022 at 5:39 PM, j-gray said:Error: License check failed.
When it comes to this error, it should be fixed in next hot fix release. (P_EEI-11289)
As you can see in the logs, the events are being sent successfully to EI server despite the error...
I apologize for the apologize for the inconvenience caused by those issues.
Peter
-
-
26 minutes ago, Nergenau said:
Can you tell me the solution ?
The issue should resolve automatically, if you have the LiveGrid enabled.
Can you confirm?
Peter
-
Hello @j-gray,
most of the reasons to see such should have been fixed in the 1.7 so maybe some of them slipped slipped through...
Can you send me the full log via a private message so I can have it checked for you?
Peter
P_EEI-8600
-
Hello @j-gray
when it comes co macs, as of now the licensing is not yet implemented for the EI connector, that is the reason for the "PERSEUS_UNKNOWN (5000)" log entries. It is not in v.6, but the license is required for v.7.
The logs show, that the events are being collected, send to server and it accepts it.
The error "RUN_LOOP_ERROR RUN_LOOP_TIMEOUT " is known and should be fixed in the 1.9 release.
Peter on behalf of the local EI guru 😉
-
Hello @GR8Metal,
thank you for your report.
This should work out of the box with the new plugin.
Can you please provide me with the log capturing the issue as I requested above (on March 31) to check with the dev team?
Peter
-
-
Hello @eclipse79,
I would also recommend to check this KB article covering the topic... https://support.eset.com/en/kb6567-you-receive-an-eset-uefi-detection
Peter
-
2 minutes ago, avielc said:
So glad to hear from you
Oh thank you
3 minutes ago, avielc said:I have 7 that have "can't connect to EEI Server" error.
What does the log say? Without it, we would be just shooting into the darkness...
Peter
-
-
Hello @avielc,
if the issue persists, collect the full set of logs from an affected machine and send them to me to check.
What exactly do you do with the endpoints?
Is it just an upgrade to the latest version, or any further actions are being performed?
Which version of EES/EEA do you have deployed?
Peter
-
Hello @Robert Smith,
the team responsible released a fix for the IDS yesterday, can you please confirm that the issue was resolved for you?
We apologize for the inconvenience caused by this,
Peter
P_EMA2-5176
-
Hello @Alexander Szewczyk,
are you able to reproduce the issue on demand i.e. does it happen after you remove them and start the Outlook again?
If yes, can you please:
- Delete the additional Junk email folders (to make the issue easier to spot)
- Quit Outlook
- Enable diagnostic logging for Email client protection as shown on the screenshot and confirm
- run Outlook and wait for the issue to demonstrate
- quit Outlook
- disable diagnostic logging to avoid extensive log-recording for a longer time.
- The resulting log will be stored under C:\ProgramData\ESET\ESET Security\Diagnostics\MailPlugins.etl
- Provide me with the log generated and info from which shared mailboxes the issue occurred to check it with our dev team.
Thank you, Peter
-
Hello Robert.
if the issue persists I would recommend to clear the browser cache, cookies and restart it to have a clear start and record a HAR from the attempt to check it with technical support.
Peter
New Outlook plugin BETA
in ESET Beta Products for Business Users
Posted
Hello @JonBastyan
the installation packages are available at https://forum.eset.com/files/category/8-outlook-plugin-beta/ for the BETA testing.
Peter